Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: x86-64 with nvidia MCP51 chipset: kernel does not find HPET
Date: Tue, 31 Oct 2006 11:24:02 -0600
Message-ID: <1449F58C868D8D4E9C72945771150BDF153784@SAUSEXMB1.amd.com>
In-Reply-To: <1162234845.27037.37.camel@mindpipe>
Thread-Topic: x86-64 with nvidia MCP51 chipset: kernel does not find
 HPET
Thread-Index: Acb8Vjl53HD0tZWxSGC/r5MMqP/NLQAuuZOw
From: "Langsdorf, Mark" <mark.langsdorf@amd.com>
To: "Lee Revell" <rlrevell@joe-job.com>
cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
       "Clemens Ladisch" <clemens@ladisch.de>
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1100
Lines: 32


 > > 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:
>
> 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?

It's not a general purpose solution, but if you can write
up the quirk, Andi might be willing to white list the 
machine in question.

-Mark Langsdorf
AMD, Inc.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/