Messages in this thread |  | | | Date | Wed, 19 Oct 2005 09:27:25 +0200 (METDST) | | From | Clemens Ladisch <> | | Subject | Re: [PATCH 0/7] more HPET fixes and enhancements |
| |
Randy.Dunlap wrote:
> On Tue, 18 Oct 2005, Clemens Ladisch wrote: > > > Randy.Dunlap wrote: > > > hpet_poll, HPET_IE_ON failed: (5) Input/output error > > > > This probably means that the interrupt isn't free. > > Isn't free because it is already in use as a system timer > interrupt, for example?
If it tries to use interrupt 0, yes.
> Does this test work (succeed) for you? If so, is HPET being > used as replacement for legacy timer and RTC? (as it is where I > am testing)
Yes. Yes.
However, I've patched my kernel to initialize the HPET manually because my BIOS doesn't bother to do it at all. A quick Google search shows that in most cases where the BIOS _does_ bother, the third timer (which is the only free one after system timer and RTC have grabbed theirs) didn't get initialized and is still set to interrupt 0 (which isn't actually supported by most HPET hardware).
This means that hpet.c must initialize the interrupt routing register in this case. I'll write a patch for this.
Regards, Clemens
- 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/
|  |