From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] lost ports
Date: Thu, 5 Jan 2017 14:08:43 -0500 [thread overview]
Message-ID: <CAC20D2MzcXUk2n-pQg_jLLacT-grxtNPuKcrZh9JB51jaiWa9w@mail.gmail.com> (raw)
In-Reply-To: <CAP6exYLonR_0Qrvwkg2OA+KwzbMX1TiYd4q0QZv+kW4uK0dLxA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
On Thu, Jan 5, 2017 at 12:23 PM, ron minnich <rminnich at gmail.com> wrote:
> 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?
I have no reason to believe it is otherwise - i.e. I have no knowledge of
anything else. Your comment about PALcode being used as leverage, I never
saw that in practice and I worked with a lot of external folks. I think
it was more of a delta-T between the time DEC engineering released the code
and DEC-Semi got it to the field and the integrators into their systems.
I don't think DEC systems sales tried to compete with the DEC-Semi
customers, although in practice I'm sure they were not very good at being
to have it both ways and certainly made mistakes. Maurice Marks was the
lead techie @ DEC Semi in those days, and a colleague I used to see fairly
often then. I know Maurice would have screamed pretty loud if he saw the
system side of DEC mucking up his business and I think G2-Bob would have
swatted folks if they had - he wanted revenue anyway he could get it. As
I think you know my last DEC projects was the 1K Alpha were we spliced an
EV6 into a $799 AMD based system. The DEC guys were the ones that hated
it (Compaq actually liked it because Dell could not do it). Anyway,
Maurice and I were shaking our heads on that one.
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170105/18422479/attachment.html>
next prev parent reply other threads:[~2017-01-05 19:08 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
2017-01-05 19:08 ` Clem Cole [this message]
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=CAC20D2MzcXUk2n-pQg_jLLacT-grxtNPuKcrZh9JB51jaiWa9w@mail.gmail.com \
--to=clemc@ccc.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).