Re: 64bit clean drivers was Re: Linux 2.4.20-pre1

From: Thunder from the hill (thunder@ngforever.de)
Date: Wed Aug 07 2002 - 12:31:29 EST

Next message: Alan Cox: "Re: Oopses on dual Athlon with 2.4.19-ac4 and 2.4.20-pre1-ac1"
Previous message: Heinz Diehl: "Re: Why 'mrproper'?"
In reply to: Andi Kleen: "64bit clean drivers was Re: Linux 2.4.20-pre1"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

On Wed, 7 Aug 2002, Andi Kleen wrote:
> Alternatively CONFIG_NO_64BIT to work around this issue.

Please don't do this. This way leads to madness when 96/128 bit or
whatever !64 bit comes. (And I can confirm it's cool.) Don't you say
"well" here, I remember being f*cked up when we doubled the bit rate once
on another system. (It was from 4 to 8 bits, actually. Nice time.)

Hardly ANYTHING will be !CONFIG_NO_64BIT.

Thunder

-- .-../../-./..-/-..- .-./..-/.-.././.../.-.-.-

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Alan Cox: "Re: Oopses on dual Athlon with 2.4.19-ac4 and 2.4.20-pre1-ac1"
Previous message: Heinz Diehl: "Re: Why 'mrproper'?"
In reply to: Andi Kleen: "64bit clean drivers was Re: Linux 2.4.20-pre1"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:36 EST