From: Clem Cole <firstname.lastname@example.org>
To: segaloco <email@example.com>
Cc: The Eunuchs Hysterical Society <firstname.lastname@example.org>
Subject: [TUHS] Re: Current Ownership of 3B/WECo Computer IPs
Date: Sun, 10 Sep 2023 21:43:27 -0400 [thread overview]
Message-ID: <CAC20D2MQjsObV-Wt4Qp3k3VydaG0AbzcxLzsB0dLiMnN980r2w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
On Sun, Sep 10, 2023 at 9:11 PM segaloco via TUHS <email@example.com> 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
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: 3171 bytes --]
next prev parent reply other threads:[~2023-09-11 1:44 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 [this message]
2023-09-11 2:57 ` segaloco via TUHS
2023-09-11 3:37 ` Clem Cole
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-9F7Afirstname.lastname@example.org>
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).