From: Heilpern, M. <mar...@au...> - 2006-11-15 17:26:10
|
What's the proper way to change the kernel's tick rate these days? (I'm using 2.6.18). include/asm/param.h wants to refer to CONFIG_HZ, which I can't find a way to change in menuconfig. If I edit .config manually to change it from 100 to 1000, it gets reset back to 100 (as can be verified by comparing /proc/uptime and /proc/interrupts). If I replace CONFIG_HZ with 1000 in param.h, my kernel boots but I can't actually log in (the system seems to lock up during the login process). _______________________________________________________ NOTE: The information in this message is intended for the personal and = confidential use of the designated recipient(s) named above. To the extent the = recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an = obligation of confidentiality, with AuthenTec, then this message and/or any = attachments shall be considered confidential information and subject to the confidentiality = terms of that agreement. If the reader of this message is not the intended recipient = named above, you are notified that you have received this document in error, and any = review, dissemination, distribution or copying of this message is strictly prohibited. If you = have received this document in error, please delete the original message and notify the = sender immediately. Thank you. AuthenTec, Inc. http://www.authentec.com |
From: ken s. <ken...@gm...> - 2006-11-15 17:37:14
|
try editing the config here: ./target/device/Gumstix/basix-connex/linux.config --- ken On 11/15/06, Heilpern, Mark <mar...@au...> wrote: > > > What's the proper way to change the kernel's tick rate these days? (I'm > using 2.6.18). include/asm/param.h wants to refer to CONFIG_HZ, which I > can't find a way to change in menuconfig. If I edit .config manually to > change it from 100 to 1000, it gets reset back to 100 (as can be verified by > comparing /proc/uptime and /proc/interrupts). If I replace CONFIG_HZ with > 1000 in param.h, my kernel boots but I can't actually log in (the system > seems to lock up during the login process). > |