how about defining the CPU in terms of features internaly and let the
config program do the work of picking which features, something along the
lines of 386, 486, pentium, ppro, k6, other where other then allowes
individual features to be picked.
David Lang
"If users are made to understand that the system administrator's job is to
make computers run, and not to make them happy, they can, in fact, be made
happy most of the time. If users are allowed to believe that the system
administrator's job is to make them happy, they can, in fact, never be made
happy."
- -Paul Evans (as quoted by Barb Dijker in "Managing Support Staff", LISA '97)
On Thu, 31 Dec 1998, Linus Torvalds wrote:
> Date: Thu, 31 Dec 1998 12:31:37 -0800 (PST)
> From: Linus Torvalds <torvalds@transmeta.com>
> To: Andrea Arcangeli <andrea@e-mind.com>
> Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
MOLNAR Ingo <mingo@chiara.csoma.elte.hu>, linux-kernel@vger.rutgers.edu
> Subject: Re: 2.2.0pre1 OOPS on boot.
>
>
>
> On Thu, 31 Dec 1998, Andrea Arcangeli wrote:
> >
> > I agree with removing completly the i386 i486 i586 i686 and add instead
> > the "has RDTSC", "has not buggy IOAPIC", "has working wp in supervisor
> > mode MMU" etc... config option. I think it's more generic, will not cause
> > documentation mistakes anymore and will produce more readable code. The
> > mtrr stuff just follow this good way.
>
> Note that I have rewritten the config.in file to essentially do this, and
> now the i386/etc choices are really just shorthands for various
> combinations of options.
>
> I agree that the most flexible thing is to make each option an option in
> itself, but quite frankly, it's way too confusing to people that don't
> intimately know their machine. Think of somebody that knows he has a
> Celeron chip, but doesn't know much else. At least there is a chance in
> hell that he would select "Pentium Pro", but there is just _no_ way that
> he can sanely answer a few questions like
>
> - do you hav a working WP bit in supervisor mode?
> - do you have a time stamp counter that works?
> - does you machine have a local APIC that doesn't need the
> read-before-write workaround?
>
> And that's basically why there is the choice according to machine type
> rather than according to each possible feature.
>
> Linus
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQEVAwUBNo1BMT7msCGEppcbAQHFiwf7BDv2IxKg98ASkjrSE5U2ihc6Q8R3LqUe
hF3hUe98peupQVU/2v72F/M+92pgDrHarfQXaA28kPeBUuR+Um6k+Q9Yo4jRoq8F
vCvbG6Ri9kJJ+QnF002gqDDGXYzGPHQaII6K3KrZ+r3PClFjDHZ8dOjhB2z1dNyI
htGWkjGPC8V1I0osmUXbM9DmBJE+3wI5AjNZ3KnfT3E7meunawnqpayGTB8Wbyb1
UQoWtD6R/Uqo9WEFGz+0SO6lRmpPRKy5bSXlR79Pbmn0iiOMXJ9YMgYP1VDPKs7X
tq+PzyOC82sGxLJqN0TQ2bwCPN1Yyi0glTpB+Ya7SY3OcHusLRUSLQ==
=voUG
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/