Re: [PATCH 1/8] Restructuring hpet timer generic clock interfaces

["S.Çağlar Onur" <caglar@pardus.org.tr>]

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

08 May 2007 Sal tarihinde, Pallipadi, Venkatesh şunları yazmıştı: 
> Hmm. Looks like timer was somehow not set correctly.
> Can you try only the first 5 patches in the patchset and leave out the last
> three and check whether it works.

Yep, first 5 patches works fine,

[caglar@zangetsu][~]> dmesg | grep hpet
hpet clocksource registered
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 64-bit timers, 14318180 Hz
hpet clockevent registered
Time: hpet clocksource has been installed.

[caglar@zangetsu][~]> cat /proc/timer_list
...
Tick Device: mode:     1
Clock Event Device: hpet
 max_delta_ns:   2147483647
 min_delta_ns:   3352
 mult:           61496110
 shift:          32
 mode:           3
 next_event:     9223372036854775807 nsecs
 set_next_event: hpet_legacy_next_event
 set_mode:       hpet_legacy_set_mode
 event_handler:  tick_handle_oneshot_broadcast
tick_broadcast_mask: 00000001
tick_broadcast_oneshot_mask: 00000000
...

If you need more output/log etc. please just say :)

Cheers
-- 
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]