The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Current Ownership of 3B/WECo Computer IPs
Date: Mon, 11 Sep 2023 02:57:50 +0000	[thread overview]
Message-ID: <8cLEEhdmkOHtKBxAfMVu6TQNyw3XQ6paWadcOywtb43zx--LshnfV0tYzcIqZGf_IBODnckLjTG-TETOHBWq8sOABYbJBXlzaYDahigXpm4=@protonmail.com> (raw)
In-Reply-To: <CAC20D2MQjsObV-Wt4Qp3k3VydaG0AbzcxLzsB0dLiMnN980r2w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]

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 <clemc@ccc.com> wrote:

> On Sun, Sep 10, 2023 at 9:11 PM segaloco via TUHS <tuhs@tuhs.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: 4478 bytes --]

  reply	other threads:[~2023-09-11  2:58 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 [this message]
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-9F7A-906732892105@seiden.com>
2023-09-11 21:06               ` Douglas McIlroy

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='8cLEEhdmkOHtKBxAfMVu6TQNyw3XQ6paWadcOywtb43zx--LshnfV0tYzcIqZGf_IBODnckLjTG-TETOHBWq8sOABYbJBXlzaYDahigXpm4=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).