Return to BSD News archive
Xref: sserve comp.arch:35909 comp.os.386bsd.questions:5187
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!koriel!cs.utexas.edu!math.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!agate!glass
From: glass@postgres.Berkeley.EDU (Adam Glass)
Newsgroups: comp.arch,comp.os.386bsd.questions
Subject: Re: PALcode
Date: 17 Sep 93 19:29:20
Organization: Organization is evil.
Lines: 29
Message-ID: <GLASS.93Sep17192920@sun-lamp.postgres.Berkeley.EDU>
References: <2700niINN8fr@jhunix.hcf.jhu.edu> <CD9HsC.EIH.1@cs.cmu.edu>
<id.H4M21.B7J@nmti.com> <CDI2pr.2Du@dragon.dsh.org>
NNTP-Posting-Host: sun-lamp.cs.berkeley.edu
In-reply-to: gary@dragon.dsh.org's message of Fri, 17 Sep 1993 13:27:25 GMT
It has been a bit since I have looked at my Alpha Architecture
Reference Manual, but I believe there should be enough information
between it and the chip-specific manual to write a new set of PALcode
routines. I saw a PostScript document on the 21064 when I was on
axposf.pa.dec.com, and from what I managed to get from it, I think it
would be enough. The new 20166 and 20168 chips should be quite similar,
if not the same, as far as PALcode is concerned. Other incarnations of
the Alpha architecture may be quite different, though. If I had NetBSD
for the AlphaPC, I would probably buy one tomorrow.
Gary D. Duzan
Network Administrator
Delaware State Hospital
If we had a few alpha boxes, and some people with time, we would be
doing an Alpha port right now. From our point of view, the Alpha is
in the same class as the sparc in terms of porting difficulty, though
DEC seems to do a better (and more accessible) job of documenting
their boxes than Sun does.
later,
Adam Glass
NetBSD project
--
Adam Glass |E-mail home: glass@sun-lamp.cs.berkeley.edu
|Physical : Seattle
"reality is for dead birds"