From: Clem Cole <email@example.com>
To: segaloco <firstname.lastname@example.org>
Cc: The Eunuchs Hysterical Society <email@example.com>
Subject: [TUHS] Re: Current Ownership of 3B/WECo Computer IPs
Date: Sun, 10 Sep 2023 23:37:39 -0400 [thread overview]
Message-ID: <CAC20D2P8jdgU-+_NwGCKAgAvDxHcfU79OujH2tGx=ryVbh6hEg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3278 bytes --]
My point was it was not clear at all other than then NCR deal would have
added to the confusion. For instance I know that one of my brothers who was
doing communications chips at ATT Allentown PA that we originally for the
3B but later licensed to Apple (became FireWire I think) stayed with ATT
but one or more of his buddies ended up moving to Ohio to become part of
NCR because that was were more SCSI and FC chips were being done.
So like lots of big firms things were added and subtracted as different
deals were made. So I’m not sure there is an easy linear progression and
while Nokia at this point clearly owns some of this but don’t be surprised
that like Unix - there are multiple firms with IP claims and unless
something happens where it takes a court to sort it out, I’m not so sure
any of here is going to be able to give you a definitive answer.
Sent from a handheld expect more typos than usual
On Sun, Sep 10, 2023 at 10:58 PM segaloco via TUHS <firstname.lastname@example.org> wrote:
> Whoops, my bad, hadn't considered NCR in this train of thought.
> And it sounds like the Nokia stream is a compelling direction, what with
> the 3B20 emulation and all that, it was a telecom processor after all. Glad
> to see I'm not just stumped, that it can be a little unclear.
> - Matt G.
> P.S. I realize my last P.S. may be more opinion oriented and/or
> controversial..just wanna recognize that oversight, no harm intended,
> different discussion for a different time
> ------- Original Message -------
> On Sunday, September 10th, 2023 at 6:43 PM, Clem Cole <email@example.com>
> On Sun, Sep 10, 2023 at 9:11 PM segaloco via TUHS <firstname.lastname@example.org> wrote:
>> Is there a clear, current owner of these WECo hardware IPs, or have those
>> waters grown even murkier than those of UNIX in the times after AT&T proper?
> I have never seen an unofficial, much less an official, reckoning, but if
> you discover/unearth something, it will be interesting to read.
> That said, you left out one piece of history. Please remember that AT&T
> bought NCR in the mid-1980s (and eventually spun it off a few years later).
> The UNIX HW development was moved into the new division of the old NCR,
> including the 3B series work, the WE32000, and some other semiconductor IPs.
> FWIW: That occurred when I consulted for NCR's Chief Architect (Lee Hovel)
> in the mid-late 80s (I did some of the analysis for Lee on what IP was
> there). But that all settled out after my contract expired, so I don't know
> how it finally settled - other than I'm reasonably sure that most of the 3B
> and chip development reported up through an ex-NCR exec after purchase.
> Those teams and their associated IP were folded into things like the old
> NCR semi-conductor, NCR Computer, *etc*.. IIRC Also, a few NCR
> communications products were moved out of the old NCR team and into the old
> WE folks.
> So .... I would not be surprised if when NCR was later spun back out, some
> of the old AT&T IP (such as the computer HW and chip IP) went with them,
> just as when Novell was sold the UNIX SW IP. Of course, later, Lucent, ney
> Alcatel, ney Nokia - got the communications IP.
[-- Attachment #2: Type: text/html, Size: 6038 bytes --]
next prev parent reply other threads:[~2023-09-11 3:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 1:11 [TUHS] " segaloco via TUHS
2023-09-11 1:35 ` [TUHS] " alan
2023-09-11 2:02 ` alan
2023-09-11 3:17 ` Kevin Bowling
2023-09-11 1:43 ` Clem Cole
2023-09-11 2:57 ` segaloco via TUHS
2023-09-11 3:37 ` Clem Cole [this message]
2023-09-11 15:34 ` Paul Winalski
2023-09-11 17:46 ` [TUHS] nassau smelting was " Mark Seiden
2023-09-11 19:58 ` [TUHS] " Douglas McIlroy
[not found] ` <F227DB6D-F1D5-45CD-9F7Aemail@example.com>
2023-09-11 21:06 ` Douglas McIlroy
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).