[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11444.1230910752@turing-police.cc.vt.edu>
Date: Fri, 02 Jan 2009 10:39:12 -0500
From: Valdis.Kletnieks@...edu
To: Jaswinder Singh Rajput <jaswinderlinux@...il.com>
Cc: Ingo Molnar <mingo@...e.hu>, Bryan Donlan <bdonlan@...il.com>,
Ingo Brueckl <ib@...peronline.de>,
linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: x86 (Linux Tiny): configure out support for some processors
On Fri, 02 Jan 2009 20:40:16 +0530, Jaswinder Singh Rajput said:
> If I know what is my CPU there is no point for supporting all related
> CPUs in my kernel.
EMBEDDED is for a large assortment of things, all of which are of the form:
General users won't want to change Y, but if I know I don't need Y, there is
no point in supporting Y in the kernel.
Y might be "this kernel doesn't need sysctl"
Y might be "support for hot-plug"
Y might be "printk"
Y might be "support generic CPUs"
See the pattern?
Yes, we probably could have come up with a better name than EMBEDDED for
that list of optionals.
CONFIG_TRAINED_TECHNICIANS_ONLY_NO_USER_SERVICABLE_PARTS_INSIDE maybe?
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists