From: rminnich@gmail.com (ron minnich)
Subject: [TUHS] lost ports
Date: Thu, 05 Jan 2017 17:23:07 +0000 [thread overview]
Message-ID: <CAP6exYLonR_0Qrvwkg2OA+KwzbMX1TiYd4q0QZv+kW4uK0dLxA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2P6qxW24Hv_cU-ctpzehEWZhNWHQ7O6uTvgbup+fiViSA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]
On Thu, Jan 5, 2017 at 8:02 AM Clem Cole <clemc at ccc.com> wrote:
>
>
> Cute story but not true [and I was @ DEC working Alpha at that time].
> Some facts:
>
Clem, thanks for the correction. This leaves me wondering why I was so
naive as to believe that fable from those guys we visited ...
I suspect they did not know or were just lying to me, since the question
came up in the context of LInuxBIOS for the 4-socket system (2048 of them
were used in ASCI Q) and I doubt they wanted to hear about non-DEC firmware
on that system.
The SRM was a huge pain point on that machine and we hoped to replace it
with something we could live with, but it was not to be.
We did get LinuxBIOS on the 1-socket pizza box thanks to Eric Biederman and
Linux NetworX, which we used to build a 128-node LinuxBIOS cluster.
LinuxBIOS included a PALcode implementation.
Which leads to a question ... Jon Hall used to tell me that DEC used SRM in
general and PALcode in particular as competitive leverage with customers
(i.e. DEC-based Alpha systems always had the latest SRM and PALcode, and
non-DEC-based Alpha systems were always a few revs behind).
Note this implies DEC as a systems vendor was competing with DEC Alpha chip
customers who were systems vendors, which was a situation we've seen in
practice with many vendors that sold chips and motherboards.
Anyway, the question: with LinuxBIOS, we shipped a GPL-ed PALcode
implementation. It was pretty dumb, it just did 1:1 virt to phys mapping
for example, but it worked. I've always believed that was the only open
source or at least GPL'ed PALcode out there -- can you tell me if I got
this right?
Thanks, it's always good to read your histories ...
sorry this is not strictly a Unix history question but I've always wondered.
ron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170105/22a4cc5e/attachment.html>
next prev parent reply other threads:[~2017-01-05 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 21:24 ron minnich
2017-01-04 21:41 ` Ron Natalie
2017-01-04 21:58 ` Larry McVoy
2017-01-05 1:52 ` Larry McVoy
2017-01-04 22:01 ` Robert Swierczek
2017-01-04 22:01 ` Dan Cross
2017-01-05 16:01 ` Clem Cole
2017-01-05 16:20 ` Clem Cole
2017-01-05 17:23 ` ron minnich [this message]
2017-01-05 19:08 ` Clem Cole
2017-01-05 19:16 ` ron minnich
2017-01-05 20:08 ` Clem Cole
[not found] ` <E3DA30C5-7227-4143-8DA1-401A161C74C6@gmail.com>
[not found] ` <CAP6exYLvXvtGEWSg_t5bqjJwunGKC1xiiaoLj7yb5QxkHsMvuA@mail.gmail.com>
2017-01-05 23:40 ` Lawrence Stewart
2017-01-05 16:15 ` Derek Fawcus
2017-01-05 18:34 ` Pierre DAVID
2017-01-05 12:28 Rudi Blom
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=CAP6exYLonR_0Qrvwkg2OA+KwzbMX1TiYd4q0QZv+kW4uK0dLxA@mail.gmail.com \
--to=rminnich@gmail.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).