From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Zhao Yakui <yakui.zhao@intel.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 00:17:17 +0200 [thread overview]
Message-ID: <200710170017.17854.ak@suse.de> (raw)
In-Reply-To: <471533C5.6050303@redhat.com>
On Tuesday 16 October 2007 23:57:25 Chuck Ebbert wrote:
> On 10/16/2007 05:51 PM, 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?
> >
>
> If I don't use the "force" option, yes. And the timer ends up as an XT-PIC-XT
> interrupt then. But the override is apparently not broken on this system.
I don't know then. Probably didn't work before either.
The early-quirks change was only supposed to fix NF5 without HPET enabled anyways;
if NF3 or 4 don't work it's some other problem.
-And
next prev parent reply other threads:[~2007-10-16 22:17 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 [this message]
2007-10-17 9:00 ` Zhao Yakui
2007-10-17 9:58 ` Andi Kleen
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=200710170017.17854.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