[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45455F21.6010908@tmr.com>
Date: Sun, 29 Oct 2006 21:10:41 -0500
From: Bill Davidsen <davidsen@....com>
To: linux-kernel@...r.kernel.org
Cc: Andi Kleen <ak@...e.de>
Subject: Re: Frustrated with Linux, Asus, and nVidia, and AMD
Robert Hancock wrote:
> Bill Davidsen wrote:
>> 2.6.18 is the latest released kernel, I don't think calling one
>> release back "ancient" is really advancing the solution. The problem
>> seems to have been reported in August, and is still not fixed, I do
>> understand that he would feel there is no progress.
>>
>> How long will you wait before putting in the fix Marc Perkel
>> suggested, perhaps with a warning logged that it's a band-aid? Many
>> users will not be astute enough to find this discussion, the bug
>> report, the fix, configure and build a kernel, etc. And not all
>> distributions will address it either.
>
> As far as the "fix" of disabling the skip-ACPI-timer-override, that is
> not something that can be put in the kernel as it will break other
> boards that require the ACPI timer override not to be used (like many
> nForce2 boards for example). Breaking working setups in order to fix
> others isn't acceptable.
>
> There are clearly some NVIDIA chipsets which require the override be
> skipped, and some which require it not be. I think the ball is currently
> in NVIDIA's court to provide a way of figuring out which chipsets
> require the quirk and which don't..
>
The kernel seems to handle lots of other quirks, I agree that this
should not be the default behavior, but it certainly seems possible to
catch this on the more common cases for which it is needed.
The boards which need it probably should be the exception, 2.6 kernels
did without it for several years, and breaking hardware which worked up
through 2.6.15 is probably not the best way to cope with new boards. I
don't think ignoring the problem while waiting for nVidia is good
policy, since it's a regression.
--
Bill Davidsen <davidsen@....com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists