On Mon, Sep 22, 2008 at 3:01 AM, Takashi Iwai <tiwai@suse.de> wrote:
The white list is marginally useful. But it is very complicate to do.
In order to preform white list. You have to know the dependency
of the module. e.g. You need to know exactly which options to
turn on so the modules will show up. The current dependency
analyze is the other way around. It knows which device should
show up when some config option is enabled. Answering the
question of which option should enable in order that device
show up is a much harder problem.
Also, as long as the user can get a boot able kernel out of
the minimal config. It is easy enough to recompile the kernel
with white list modules and install them as needed.
The white list should be a secondary step to do because
its complexity. The first priority is to have some thing simple
and provide a good minimal kernel module option. Then we
can go from there, how to add extra white list from it. The white
list is a very different game any way. I found the minimal config
option is a sweet spot to have in terms of feature and simplicity.
Some module does not want to be compile as build-in.
Chris
--
