|From:||"William J. Earl" <firstname.lastname@example.org>|
|Date:||Sun, 27 Dec 1998 18:32:31 -0800|
|Cc:||Greg Chesson <email@example.com>, Alex deVries <firstname.lastname@example.org>, Ariel Faigon <email@example.com>, Fredrik Rovik <firstname.lastname@example.org>, email@example.com|
|References:||<Pine.LNX.3.96.981222224859.1946Cfirstname.lastname@example.org> <email@example.com> <9812230951.ZM5336@xtp.engr.sgi.com> <19981224190545.A648@uni-koblenz.de>|
firstname.lastname@example.org writes: ... > > What we need to do is make it easy for Linux to determine what > > chipsets are attached to the cpu. Bill Earl might have some > > straightforward > > answers. I'm in favor of simply publishing the relevant sections > > of Irix bootstrap code. Perhaps Santa Claus can make a code drop this > > year. > > Isn't that ``Full House'' vs. ``Guiness''? Linux knows that difference since > it is running on the Indy. The basic difference is between "FullHouse" (Indigo2) and "Guinness" (Indy). Beyond that, there are smaller differences between Indy and Challenge S. Challenge S does have an extra SCSI channel, but the configuration is not identical to Indigo2. (I will look into that later.) I am still working on an agreement to release more technical information about a variety of our systems.
|<Prev in Thread]||Current Thread||[Next in Thread>|