Date: Fri, 6 Sep 1996 19:04:38 +0200 (MET DST) From: Stefan Esser <se@zpr.uni-koeln.de> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: se@freefall.freebsd.org (Stefan Esser), CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c Message-ID: <199609061704.TAA16627@x14.mi.uni-koeln.de> In-Reply-To: <199609060323.MAA15217@genesis.atrad.adelaide.edu.au> References: <199609052134.OAA21522@freefall.freebsd.org> <199609060323.MAA15217@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Smith writes: > Stefan Esser stands accused of saying: > > > > Include only register specifications for those chip sets that apply to > > a cpu that might boot this a particular kernel (ie. make the Saturn code > > depend on I486_CPU being defined, the Pentium chip sets on I586_CPU ...) > > Please note that the PODP chips mean that it's possible to have a Pentium > on a 486 board; I would be cross for example to discover that the SiS > 496/497 code disappeared from my kernel just because I'm running one 8) The PODP ??? You mean there are actually people who use them ? You got one yourself ? Well, that's a difference :) Honestly, I totally forgot about that chip, and it makes my idea look even worse ... I had already come to the conclusion that it wasn't worth the complexity, and had been thinking about backing out that change. (I wondered about the Cyrix 6x86 cpu, for example, which isn't detected as an I586_CPU, AFAIK, but goes into the same motherboards as a Pentium. This would be a CPU that claimed to be a 486, but needs the P5 chip set names. The opposite of your situation with the PODP ...) You'll get your chip set message back. I promise! Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609061704.TAA16627>