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: Len Brown <lenb@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Daniel Mierswa <impulze@impulze.org>,
	Andy Currid <acurrid@nvidia.com>
Subject: Re: ASUS M2NPV-VM APIC/ACPI Bug (patched)
Date: Thu, 19 Oct 2006 14:44:53 +0200	[thread overview]
Message-ID: <200610191444.53968.ak@suse.de> (raw)
In-Reply-To: <4536C9DA.4060704@shaw.ca>


> I think the intent of the HPET check was that the quirk wasn't needed on 
> chipsets new enough to have an HPET. 

Yes.

> Unfortunately, even if the chipset  
> has an HPET it isn't always enabled by the BIOS.

It was supposed to be correct in the NF5 reference BIOS, but somehow Asus
must have managed to break the reference BIOS.

> Clearly this quirk is too broad, it should likely be only triggering on 
> known chipset revisions with the bad timer overrides and not on all 
> NVIDIA chipsets. 

That was impossible at the point where it was implemented.

> What I am wondering is how these boards manage to work  
> fine in Windows, (presumably) without any such chipset-specific tweaks..

They use the RTC interrupt for timing instead AFAIK so a broken interrupt 0
won't affect them. That's probably why we have so many problems with
interrupt 0 on cheap systems.

I tried it once to use in Linux too BTW, but it unfortunately cannot generate
any of the standard Linux timer frequencies.

-Andi

  reply	other threads:[~2006-10-19 12:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.09mXx81eXfIStK3wap/U1OZn+kg@ifi.uio.no>
     [not found] ` <fa.1/QTOTFQC91cwKwinVDxrePnGHo@ifi.uio.no>
2006-10-19  0:42   ` ASUS M2NPV-VM APIC/ACPI Bug (patched) Robert Hancock
2006-10-19 12:44     ` Andi Kleen [this message]
2006-10-19 15:52     ` Allen Martin
2006-10-19 16:11       ` Andi Kleen
2006-10-20  1:08         ` Allen Martin
2006-10-20 13:04           ` Andi Kleen
2006-11-01 14:21             ` impulze
2006-11-01 14:27               ` Arjan van de Ven
2006-10-18  6:44 Daniel Mierswa
2006-10-18  7:30 ` Len Brown
2006-10-19 12:41   ` 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=200610191444.53968.ak@suse.de \
    --to=ak@suse.de \
    --cc=acurrid@nvidia.com \
    --cc=hancockr@shaw.ca \
    --cc=impulze@impulze.org \
    --cc=lenb@kernel.org \
    --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