Re: 2.2.0pre1 OOPS on boot.
root (root@ohwig03.houston.cwomnes.net)
Fri, 1 Jan 1999 14:35:05 -0600 (CST)
> 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.
what about something like this:
for each chip that we already have a profile for, allow something like:
Cyrix processor [Y/n/?]
6x86 [N/y/?]
MI [N/y/?]
MII [Y/n/?]
where each profile has the correct settings for a given cpu.
in addation, have a fallthrough configuration where new/unknown cpus
can select the options by hand:
Configure processor attributes by hand [Y/n/?]
working WP bit in supervisor mode [n/Y/?]
working time stamp counter [n/Y/?]
-
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/