Re: Cleaning up the "linux" directory

[Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>]

Dnia sobota, 22 sierpnia 2009 o 11:38:41 Ulf Samuelsson napisał(a):
> As everyone knows, the kernel directory is a mess:
> I have been thinking about what to do about this,
> and with the ability to include files in subdirectories,
> I think I have found a nice solution.

I had a look at this and for me it adds lot of things to care when kernel 
needs to be updated/changed.

With current linux_X.Y.Z(.A).bb recipes it is easy to add new device - just 
one file needs to be edited and thats all. If new patch has to be added then 
still one file to edit. New board to be added - same amount of work. If 
patches common for few targets needs to be added then you can create new 
variable for them:

AT91_PATCHES = "\
        file://linux-2.6.30/at91/2.6.30.2/patch-sets/linux-2.6.30.2-at91-001-
andrew-victor.patch;patch=1 \
        file://linux-2.6.30/at91/2.6.30.2/patch-sets/linux-2.6.30.2-at91-002-
experimental.patch;patch=1 \
        file://linux-2.6.30/at91/2.6.30.2/patch-sets/linux-2.6.30.2-at91-003-
ac97-0001-sam9g45-r1.patch;patch=1 \
        file://linux-2.6.30/at91/2.6.30.2/patch-sets/linux-2.6.30.2-at91-003-
ac97-0002-ac97-sam9rlek-r1.patch;patch=1 \
        file://linux-2.6.30/at91/2.6.30.2/patch-sets/linux-2.6.30.2-at91-004-
NAND-001-configurable-partition-size.patch;patch=1 \
        file://linux-2.6.30/at91/2.6.30.2/patch-sets/linux-2.6.30.2-at91-005-
touchscreen-001-sam9g45ek.patch;patch=1 \
        file://linux-2.6.30/at91/2.6.30.2/patch-sets/linux-2.6.30.2-at91-006-
EHCI-001.sam9g45ek.patch;patch=1 \
        file://linux-2.6.30/at91/2.6.30.2/patch-sets/linux-2.6.30.2-at91-007-
CLK-001-debug-clocks.patch;patch=1 \
        "

And use it in SRC_URI for all boards. If patches do not touch files used by 
other devices then adding them directly to default SRC_URI should also be 
possible (thats how at91 patch was added in linux_2.6.30.bb recipe).

With your solution I have to check about 10 files in many directories or 
regenerate all of them by some script (what about caring of manual changes in 
those files?).

Maybe Buildroot uses such way (I do not know because last time I used it 
before OE) but for me as long time OE developer it just adds lot of possible 
errors to do.

Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz