Return to BSD News archive
Xref: sserve comp.arch:35918 comp.os.386bsd.questions:5198 Newsgroups: comp.arch,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Subject: Re: PALcode Message-ID: <hastyCDKLtq.MLy@netcom.com> Organization: Netcom Online Communications Services (408-241-9760 login: guest) References: <id.H4M21.B7J@nmti.com> <CDI2pr.2Du@dragon.dsh.org> <GLASS.93Sep17192920@sun-lamp.postgres.Berkeley.EDU> Date: Sat, 18 Sep 1993 22:15:26 GMT Lines: 32 In article <GLASS.93Sep17192920@sun-lamp.postgres.Berkeley.EDU> glass@postgres.Berkeley.EDU (Adam Glass) writes: > > 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. > Why don't you call up DEC and persuade them to loan you a couple of Alpha workstations? Amancio -- This message brought to you by the letters X and S and the number 3 Amancio Hasty | Home: (415) 495-3046 | ftp-site depository of all my work: e-mail hasty@netcom.com | sunvis.rtpnc.epa.gov:/pub/386bsd/incoming