Date: Thu, 15 May 97 17:18:12 -0700 From: "Chris G. Demetriou" <cgd@pa.dec.com> To: Andrew Gallatin <gallatin@CS.Duke.EDU> Cc: Warner Losh <imp@village.org>, freebsd-alpha@FreeBSD.ORG Subject: Re: Alpha questions.. Message-ID: <717.863741892@dnaunix.pa.dec.com> In-Reply-To: Your message of "Thu, 15 May 97 18:32:19 EDT." <199705152232.SAA28646@hurricane.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > : Also, I understand that the PALcode in MILO is not idential to the > > : PALcode in the SRM console firmware. > > Download milo & have a look. The palcode claims to be the OSF > PAL code. It is, but it is _not_ identical to the OSF PALcode in the SRM console firmware in several ways. At minimum: (1) there are some interfaces provided by the SRM console's OSF PALcode on some platforms which are not provided by the MILO OSF PALcode, and (2) machine-checking handling/logout frames are different. > Also, since Linux can boot from either SRM or Milo, it would seem that > the OSF PAL code in Milo & in the SRM console are "close enough." They are not. There are operations provided by the OSF PALcode on (at least) EB64+ and EB164 machines which are not provided by MILO's OSF PALcode. If you're using EB64+ or EB164 systems with 'native' OSF PALcode and try to use the hardware directly rather than using the PALcode ops provided by the firmware (for the appropriate operations), you will not be receiving many interrupts... cgd
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?717.863741892>