On Mon, 1 Feb 1999, Matthew Jacob wrote:

> 
> An interesting FYI about CIA. Jay works at Digital....
> 
> 
> 
> ---------- Forwarded message ----------
> Date: Mon, 1 Feb 1999 19:22:39 -0800
> From: Richard Henderson <rth@cygnus.com>
> To: mjacob@feral.com
> Cc: linux-alpha@vger.rutgers.edu
> Subject: Re: (PROBLEM SOLVED) Re: restore to srm that doesn't....
> 
> On Mon, Feb 01, 1999 at 05:15:40PM -0800, Matthew Jacob wrote:
> > cia0: using BWX for PCI config access
> 
> Beware.  Jay Estabrook told me the CIA-2 on the PC164 is buggy
> with BWX I/O.  The first core chipset to get it right was PYXIS.
> 
> I don't know in what form the bugs appear -- I just took his word for it.
> 
> > isp1 at pci0 dev 6 function 0
> > isp1: Board Revision 2100, loaded F/W Revision 1.15
> > isp1: Adapter WWN 0x200000e08b003c1f
> > isp1: Firmware State Config Wait -> Waiting for AL/PA
> > isp1: Firmware State Waiting for AL/PA -> Wait Login
> > isp1: Firmware State Wait Login -> Ready
> > isp1: Loop ID 113, ALPA 0x23
> 
> 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.

We only use BWX for machines with PYXIS.  As far as I know, all EB164 type
machines with a subtype >= SV_ST_ALPHAPC164LX_400 should have PYXIS (this
is the way NetBSD detected them and we do the same).

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037