#Granted, this would detect the case of BX on a CPU w/o cpuid correctly.
#But there is no such abomination out there (yet). In any case, I'm
#curious, how do you go about detecting BX at such an early stage (no PCI
#or anything yet)?
THAT, I am not sure how I will do gracefully. I'm beginning to think it
might be easier to be a compile-time option. It's not like joe-user isn't
going to know he's got BX in his PC. All the OEMs are hyping it like it's
the coolest thing since sliced white bread. }:P
#I agree. My point is that we don't want to start adding detection code
#for every single possible thing that may exist out there, unless it is
#absolutely necessary. This low-level stuff has a really strong tendecy to
#interact and break things (as the BX-Cyrix case proved). If we can work
#on the BX chipset in C somewhere else the better.
Definitely. That's why I'm beginning to seriously consider it being a
compile time option. MUCH easier. Then it becomes THIS easy:
if compiled BX
don't touch 0x22,0x23
else
play with 0x22,0x23
Wow. That was hard. :)
#I'd rather wait and see, and also put it in big red letters in the code.
#"This code assumes that anything running on BX will have cpuid available".
#Either way would be correct (for now). :)
Maybe. Remember, AMD may blow it. We'll have to see.
#True, but how do you know it does 0x22,0x23 *without* using 0x22,0x23?
#That why the current code uses the flags across division test.
If there's one thing Cyrix has, it's consistency with stuff like that. And
fixing stuff in later revisions. Always. That's why I usually wait on
newer Cyrix processors. Find somebody who has one, find out what bugs and
issues may or will need to be worked around, and wait till they fix them.
;)
-Phil R. Jaenke (kernel@nls.net / prj@nls.net)
TheGuyInCharge(tm), Ketyra Designs - We get paid to break stuff :)
Linux pkrea.ketyra.INT 2.0.33 #15 Sat Apr 18 00:40:21 EDT 1998 i586
Linux eiterra.nls.net 2.1.98 #15 Fri May 1 18:21:00 EDT 1998 i586
- Linus says for 'brave people only.' I say 'keep a backup.' - :)
! I reserve the right to bill spammers for my time and disk space !
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu