![]() | ||||||||||
Messages in this thread |
Rune Torgersen writes: > CONFIG_HZ is not broken, but the whole clock configuration is. > (I poseded something about it for 8260 earlier this summer) > > Basic problem is that CLOCK_TICK_RATE which is used for setting up the > variables used for advancing the clock, is hardcoded to a value that > only makes sence for an i386. (it is default set at 1193180Hz which > happens to be the timer clock for timer1 on an i386 machine) I do not believe CLOCK_TICK_RATE affects timekeeping at all on ppc or ppc64 machines, but I could be wrong. Can you show us where and how CLOCK_TICK_RATE affects things? Paul. - 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/ | |||||||||
| Last update: 2005-10-04 12:51 [from the cache] ©2003-2008 | ||||||||||