> What's this card?
> 
> > sio0 at pci0 dev 8 function 0: Intel 82378ZB System I/O (SIO) (rev. 0x43)
> 
> Yep, definitely a PC164.  Wonder why the SRM isn't reporting the
> right thing? 
> 
> Would you annotate get_cpuinfo() to report the numeric sys_variation?
> Perhaps my ident data is off by one.

Booting on EB164 variation EB164 using machine vector EB164 (typ 1a var 4)

This is wrong then- the var field only has EMBEDDED CONSOLE set. Looks
like we'll need another console command line override for subtype too!



Y'know- I can't remember where the HWRPB systype/field comes from- is this
ultimately determined by the PAL code, or by the CONSOLE code loaded
inside EV5 at powerup?

I'll send along my patches too that will print out the system/variant
names that the PAL has set up (dsr_sysname). Later today I'll get around
to booting with NetBSD again which uses different PAL code and check to
see what the typ/subtype is...

I believe I must have ancient PAL code- I'm using the aboot that came with
LINUX RH5.2, which about-0.5 with whatever (2.0.35?) bootlx that comes
with. This boot block exits right away (halts) when I boot on a rawhide-
and isn't this the fella responsible for loading PAL code? So is this
bustedness possibly due to old PAL code being used? BTW- I can't build
rawboot in 2.2.1 (build fails)- is working in another version?

-matt




Reply via email to