On Fri, 2002-06-14 at 11:57, Dave Jones wrote:
> -#ifndef CONFIG_X86_TSC
> +#if !defined(CONFIG_X86_TSC)||defined(CONFIG_TSC_DISABLE)
> +#ifdef CONFIG_TSC_DISABLE
> +static int tsc_disable __initdata = 1;
> +#else /*CONFIG_TSC_DISABLE*/
> static int tsc_disable __initdata = 0;
> +#endif /*CONFIG_TSC_DISABLE*/
>
> This looks *really horrible*
True, I agree here.
> Why not just unset CONFIG_X86_TSC for those machines ?
I was actually hoping for a suggestion like this when I posted this
patch earlier. Can one really just unset CONFIG_ options that have
previously been set? I'd actually prefer this, but doing so generated a
.config that looked like:
CONFIG_X86_TSC=y
...
# CONFIG_X86_TSC is not set
So I assumed CONFIG_X86_TSC would still hold. Am I wrong, or is there
another way to do this?
Thanks
-john
-
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/
This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:32 EST