public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Bill Davidsen <davidsen@tmr.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: lspci output needed was Re: Frustrated with Linux, Asus, and nVidia, and AMD
Date: Tue, 31 Oct 2006 15:28:19 +0100	[thread overview]
Message-ID: <200610311528.20013.ak@suse.de> (raw)
In-Reply-To: <454432DC.9030006@shaw.ca>


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

My current plan is to switch in 2.6.20 to automatic probing of more pins
for the timer routing (suggested by Tim Hockin, I've got a test patch). 

But that's too risky for .19.

For 2.6.19 we'll likely add some more PCI-IDs disabling the quirk
and a command line option to disable the skip timer override quirk. 

Doing this per PCI ID isn't that bad because afaik Vista certification
requires enabling the HPET table and I assume most boards will get
Vista certification soon. This will force Asus to fix their BIOS.

Can people who use a Nvidia based AM2/SocketF board (especially when they have timer 
troubles but otherwise would be useful too) please report their lspcis in private 
mail to me?

-Andi



  parent reply	other threads:[~2006-10-31 14:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.nWSYbiDM13Z4b2OlxoSzmqud/lI@ifi.uio.no>
     [not found] ` <fa.NxAEaSXPSQSEviWvGDBmTZn07UE@ifi.uio.no>
     [not found]   ` <fa.i/oIAoig46I/apLGccQ0BesB0W8@ifi.uio.no>
2006-10-29  4:49     ` Frustrated with Linux, Asus, and nVidia, and AMD Robert Hancock
2006-10-30  2:10       ` Bill Davidsen
2006-10-31 14:28       ` Andi Kleen [this message]
2006-10-31 16:11         ` lspci output needed was " Bill Davidsen
2006-11-01 22:17         ` Gerd v. Egidy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200610311528.20013.ak@suse.de \
    --to=ak@suse.de \
    --cc=davidsen@tmr.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox