Andrea Adami píše v Út 08. 06. 2010 v 17:03 +0200:
> I post here a single msg from the mega-thread, because even if it is
> rejected by Linus we could reuse it in OE :)
> The idea is reducing the defconfigs: for Zaurus we have very much in
> common between defconfigs, so much that Iwas thinking to just create
> the diffs.
> Now Eric seems having a better method...
>
> Opinions?
I was thinking about metaconfigs, but never made a clean image of my
idea. It could be something like this:
- list of config options for chips inside device xxx
- sub list of the configs required for boot
(device specific)
- meta list "common drivers for small USB hosts"
- can be activated as modules or built in
- sub list of the common drivers that may be used for boot (e. g. mass
storage)
(common for all devices and probably all platforms)
- meta list "common drivers for small CF hosts"
- the same options like small USB hosts
- meta list "common drivers for small SD hosts"
- meta list "common drivers for small USB hosts"
- meta list "common drivers for router USB hosts"
- meta list "common drivers for desktop USB hosts"
(it may be everything from small USB hosts plus DVB drivers etc.)
- meta list "all drivers for desktop USB hosts"
- meta list "common drivers for server USB hosts"
- meta list "common drivers for industry USB hosts"
The config for say zaurus may consist of these metaconfigs:
chips inside Zaurus (yes) + common drivers for small USB hosts (modules
+ yes for "may be used for boot") + common drivers for small CF hosts
(modules + yes for "may be used for boot") + common drivers for small SD
hosts (modules + yes for "may be used for boot")
________________________________________________________________________
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus
_______________________________________________
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
