Linux-kernel mailing list archive 2000-15,: RE: NexGen detection

# RE: NexGen detection

Thomas S. Iversen (zensonic@diku.dk)
Sat, 15 Apr 2000 09:42:10 +0200 (METDST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: G. Allen Morris III: "Re: Suggested dual human/binary interface for proc/devfs"
- Previous message: Richard Gooch: "Re: devfs - why not ?"

On Fri, 14 Apr 2000, Maciej W. Rozycki wrote:

> If you compile for an 486 or better the kernel assumes WP works right --
> no check is performed other than the following one (this is taken from
> include/asm-i386/bugs.h):

I know for sure that a kernel compiled for a 586 won't work caused by:

if (boot_cpu_data.wp_works_ok < 0) {
boot_cpu_data.wp_works_ok = 0;
printk("No.\n");
#ifdef CONFIG_X86_WP_WORKS_OK
panic("This kernel doesn't support CPU's with broken
WP. Recompile it for a 386!");
#endif

in arch/i386/mm/init.c. Haven't tried as a 486. Will it work? If not, we
need to update the Configure.help file saying that nexgens must be
compiled as 386. Currently it says:

- "486" for the AMD/Cyrix/IBM/Intel DX4 or 486DX/DX2/SL/SX/SX2,
AMD/Cyrix 5x86, NexGen Nx586 and UMC U5D or U5S.

Question is still wether you should leave the cosmetics (use
cpuid if supported to populate /proc/cpuinfo) out of the story. The kernel
works just fine anyhow.

Yours Thomas

Thomas S. Iversen
zensonic@diku.dk
Dept. of computer science - copenhagen, denmark.

-
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/

- Next message: G. Allen Morris III: "Re: Suggested dual human/binary interface for proc/devfs"
- Previous message: Richard Gooch: "Re: devfs - why not ?"