From: Andi Kleen <ak@suse.de>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: Chuck Ebbert <cebbert@redhat.com>,
Linux-acpi@vger.kernel.org, lenb@kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] [PATCH] ACPI :Modify timer override connection in Some NVIDIA systems
Date: Wed, 17 Oct 2007 11:58:19 +0200 [thread overview]
Message-ID: <200710171158.19578.ak@suse.de> (raw)
In-Reply-To: <1192611639.15762.7.camel@yakui_zhao.sh.intel.com>
On Wednesday 17 October 2007 11:00:39 Zhao Yakui wrote:
> On Tue, 2007-10-16 at 23:51 +0200, Andi Kleen wrote:
> > On Tuesday 16 October 2007 23:07:29 Chuck Ebbert wrote:
> >
> > > Do I need something more than early-quirks-unification and nvidia-timer-quirk?
> > > Because those two don't fix anything; I have to manually force
> > > acpi_use_timer_override to get things to work right. The RFC patch seems to
> > > be doing the right thing automatically.
> > >
> > > Hardware: nVidia MCP51/C51 (with HPET)
> > > Host Bridge PCI ID: 10de:02f0
> >
> > Do you see the "Nvidia board detected. Ignoring ACPI timer override." message?
> When booted with acpi=off, the system will print the message ---Nvidia
> board detected .Ignoring ACPI timer override.
> But when booted with acpi on, the system won't print the above message.
That was a NF5 system right? If yes the nvidia-timer-quirk patch should
work on it.
It didn't work on Chuck's system because that wasn't a NF5.
The main change nvidia-timer-quirk adds is to run the override ignore logic
only on NF4 and NF3.
His system seems to be in a new situation: a NF4 system which needs
a timer override (that wasn't the case before!) and since most NF4 overrides
are wrong and Linux is ignoring them it won't work.
I don't really see how to handle this short of a DMI quirk for the board.
Your patch essentially hard codes the timer override for all of Nvidia which is surely
not the correct thing to do -- we have lots of evidence that those varies
widely. Or at least if you really want to hard code you should only do it with a
explicit DMI entry for a specific board.
> The chipset of NVIDIA is used and HPET exists. So the timer_override is
> required. But unfortunately the timer override info provided by BIOS is
> uncorrect.
Most NF5 systems need timer override -- if some of them supply the wrong
one I don't see how to detect this short of a DMI quirk.
-Andi
prev parent reply other threads:[~2007-10-17 9:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 7:04 [RFC] [PATCH] ACPI :Modify timer override connection in Some NVIDIA systems Zhao Yakui
2007-10-15 16:30 ` Chuck Ebbert
2007-10-15 16:32 ` Andi Kleen
2007-10-16 21:07 ` Chuck Ebbert
2007-10-16 21:51 ` Andi Kleen
2007-10-16 21:57 ` Chuck Ebbert
2007-10-16 22:17 ` Andi Kleen
2007-10-17 9:00 ` Zhao Yakui
2007-10-17 9:58 ` Andi Kleen [this message]
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=200710171158.19578.ak@suse.de \
--to=ak@suse.de \
--cc=Linux-acpi@vger.kernel.org \
--cc=cebbert@redhat.com \
--cc=lenb@kernel.org \
--cc=tglx@linutronix.de \
--cc=yakui.zhao@intel.com \
/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