From: Carlos Corbacho <carlos@strangeworlds.co.uk>
To: "f.cecco77@tiscali.it" <f.cecco77@tiscali.it>, tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: hpet on nforce4/MCP51 in asus a6t
Date: Mon, 4 Feb 2008 12:20:19 +0000 [thread overview]
Message-ID: <200802041220.20849.carlos@strangeworlds.co.uk> (raw)
In-Reply-To: <19861822.1202063637753.JavaMail.root@ps23>
[Adding tglx to CC as he knows more about HPET's than I]
On Sunday 03 February 2008 18:33:57 f.cecco77@tiscali.it wrote:
> Hello,
> I have a asus a6t with nforce4/MCP51 chipset. I pass to kernel 2.6.24
> 32 bit the options acpi_use_timer_override and hpet=force, in this way
> and the timer IRQ ends up routed as IO-APIC-edge instead of XT-PIC.
> With acpi_use_timer_override I just get:
>
> TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
>
> and it works through the IO-APIC.
>
> Instead the hpet is disabled and I just get :
>
> Time: acpi_pm clocksource has been installed.
> Clocksource tsc unstable (delta = -85010975 ns)
>
> Is possible to have hpet working also with if the BIOS doesn't support
> it ?
One point before we start - MCP51 is nForce 5, not nForce 4 (which is CK804).
If my understanding is correct, acpi_use_timer_override is only a workaround
required for those nForce 5 boards that don't enable the HPET for you.
So IIUC, you should be able to use either 'hpet=force'
or 'acpi_use_timer_override', either of which should solve any timing issues
you see, but you shouldn't need both (which should solve your problem of
acpi_use_timer_override ignoring the HPET - it shouldn't be needed
if 'hpet=force' enables the HPET).
-Carlos
--
E-Mail: carlos@strangeworlds.co.uk
Web: strangeworlds.co.uk
GPG Key ID: 0x23EE722D
next prev parent reply other threads:[~2008-02-04 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 18:33 f.cecco77
2008-02-04 12:20 ` Carlos Corbacho [this message]
2008-02-04 18:10 ` cecco
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=200802041220.20849.carlos@strangeworlds.co.uk \
--to=carlos@strangeworlds.co.uk \
--cc=f.cecco77@tiscali.it \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®