Hi,
if you have that chip on your mainboard and want to play with it's
hpet, this might get you going.
Karsten
Karsten Wiese wrote:
> if you have that chip on your mainboard and want to play with it's
> hpet, this might get you going.
I'm using similar code for my ICH5 southbridge, but I patched
arch/i386/kernel/acpi/boot.c instead so that the kernel can use it
for its own purposes.
> One exception: Timer1 says it can do PERIODIC mode,
> but this doesn't work here. One shot is ok.
This may be because your patch doesn't initialize the interrupt
routing registers (which would have been the BIOS' job).
Regards,
Clemens
Am Montag, 26. September 2005 17:49 schrieb Clemens Ladisch:
> Karsten Wiese wrote:
> > if you have that chip on your mainboard and want to play with it's
> > hpet, this might get you going.
>
> I'm using similar code for my ICH5 southbridge, but I patched
> arch/i386/kernel/acpi/boot.c instead so that the kernel can use it
> for its own purposes.
The kernel uses the hpet here too with my patch.
Please send me your acpi/boot.c patch.
I guess you setup an ACPI_HPET entry, if none has been found?
Maybe your approach is safer/better, 'cause you can scan other ACPI
assigned Hardware addresses there.
>
> > One exception: Timer1 says it can do PERIODIC mode,
> > but this doesn't work here. One shot is ok.
>
> This may be because your patch doesn't initialize the interrupt
> routing registers (which would have been the BIOS' job).
No. Interrupt works fine (IRQ 8). Reliably @10000/s.
Regards,
Karsten
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
Karsten Wiese wrote:
> Am Montag, 26. September 2005 17:49 schrieb Clemens Ladisch:
> > Karsten Wiese wrote:
> > > if you have that chip on your mainboard and want to play with it's
> > > hpet, this might get you going.
> >
> > I'm using similar code for my ICH5 southbridge, but I patched
> > arch/i386/kernel/acpi/boot.c instead so that the kernel can use it
> > for its own purposes.
>
> The kernel uses the hpet here too with my patch.
Uh, yes. I wasn't sure where I could add a hook to be called early
enough so that the assignment to hpet_address still takes effect, so I
just unconditionally replaced acpi_parse_hpet.
> Please send me your acpi/boot.c patch.
Attached.
> I guess you setup an ACPI_HPET entry, if none has been found?
This would be a good idea for a patch that would have any chance of
being applied to the kernel.
> Maybe your approach is safer/better,
You didn't yet see it ... ;-)
Regards,
Clemens