ext An Yang wrote:
在 2010-04-21三的 08:04 -0700，Greg KH写道：
As someone who has maintained kernels with a few dozen config files for
a long time, for different arches and flavors, no, this seems much
easier to keep everything in sync properly.
Let's try it and see, individual config files are very hard to ensure
that they are consistant.
absolutely right. consistant means less mistake.
but to solve is problem, the kernel maintainer should have a clear
maintain rules.
which driver should be in, which driver should be module, which driver
should be out?
Right.
This is what i think.
Minimally there should be 2 config files
1) config-generic
2) config-platform (e.g. config-menlow or config-n900)
config-generic should only stuff that is not specific to any Architecture. It
definitely cannot have any Kconfig option that comes from arch directory. So
usually config-generic would only contain Network protocols, File systems. I
don't think this should contain any device driver options.
config-platform contains all Architecture and board specific bus enablers
(USB/PCI/I2C/etc), power management and device drivers. This should come ideally
from board_defconfig but in real world this can be a separate file.
I don't think it is necessary to have an additional config-arch-generic for ARM
since for example we can't have a config-arm-generic that keeps all ARM
platforms happy and is at the same time optimal. We need to keep kernel size as
small as possible. If any platform e.g. x86 that have a lot in common in their
variants then they could have these common options in config-x86-generic. so
this would be left to the platform guys how they want to have it.
For ARM platforms I would say config-generic and config-platform should suffice.
-roger
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
