From: Lee Revell <rlrevell@joe-job.com>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Clemens Ladisch <clemens@ladisch.de>
Subject: RE: x86-64 with nvidia MCP51 chipset: kernel does not find HPET
Date: Mon, 30 Oct 2006 14:00:44 -0500 [thread overview]
Message-ID: <1162234845.27037.37.camel@mindpipe> (raw)
In-Reply-To: <1449F58C868D8D4E9C72945771150BDF153774@SAUSEXMB1.amd.com>
On Mon, 2006-10-30 at 11:07 -0600, Langsdorf, Mark wrote:
> > I have a 6 month old x86-64 machine with nvidia MCP51 chipset on which
> > the kernel does not detect the HPET. According to HPET maintainer
> > Clemens Ladisch, this machine certainly has one, but it cannot be
> > enabled for lack of hardware documentation.
> >
> > Is there anything I can do to help debug this?
>
> If the hardware is not providing the HPET description in ACPI,
> there's little you can do, and most vendors do not provide
> the HPET description.
>
> Do you know if there's an entry for HPET in the ACPI?
I'm not exactly an ACPI expert, but I do not think there is an entry for
HPET in the ACPI, as the check in arch/x86_64/kernel/io_apic.c fails:
358 /*
359 * All timer overrides on Nvidia are
360 * wrong unless HPET is enabled.
361 */
362 nvidia_hpet_detected = 0;
363 acpi_table_parse(ACPI_HPET,
364 nvidia_hpet_check);
365 if (nvidia_hpet_detected == 0) {
366 acpi_skip_timer_override = 1;
367 printk(KERN_INFO "Nvidia board "
368 "detected. Ignoring ACPI "
369 "timer override.\n");
370 }
But, with some help from anonymous sources, I have been able to find the
HPET and make it work using a userspace driver that pokes registers by
mmap'ing /dev/mem. So we just need a way to tell the kernel it's there.
Presumably this would require a PCI quirk.
Is this likely to be worth the trouble?
Lee
next prev parent reply other threads:[~2006-10-30 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 22:15 x86-64 with nvidia MCP51 chipset: kernel does not find HPET Lee Revell
2006-10-30 17:07 ` Langsdorf, Mark
2006-10-30 19:00 ` Lee Revell [this message]
2006-10-31 17:24 ` Langsdorf, Mark
2006-11-15 20:55 ` Prakash Punnoor
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=1162234845.27037.37.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.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