Common patch directory for a set of boards.

Common patch directory for a set of boards.

[Ulf Samuelsson]

Is there a way to store a patch which is applied to a list of boards,
but not every board, in a common directory?

SRC_URI_append_at91sam9263ek += "file://atmel.patch;patch=1"
SRC_URI_append_at32stk1000 += "file://atmel.patch;patch=1"
SRC_URI_append_at572d940hf += "file://atmel.patch;patch=1"
SRC_URI_append_beta1 += "file://beta.patch;patch=1"
SRC_URI_append_beta2 += "file://beta.patch;patch=1"
SRC_URI_append_beta3 += "file://beta.patch;patch=1"
SRC_URI_append_caesar1 += "file://caesar.patch;patch=1"
SRC_URI_append_caesar2 += "file://caesar.patch;patch=1"

with a file system like:

<recipe>
	recipe-1.0/atmel/atmel.patch
	recipe-1.0/beta/beta.patch
	recipe-1.0/caesar/caesar.patch
	recipe-1.0.bb


instead of

<recipe>
	recipe-1.0/at91sam9263ek/atmel.patch
	recipe-1.0/at32stk1000/atmel.patch
	recipe-1.0/at572d940hf/atmel.patch
	recipe-1.0/beta1/beta.patch
	recipe-1.0/beta2/beta.patch
	recipe-1.0/beta3/beta.patch
	recipe-1.0/caesar1/caesar.patch
	recipe-1.0/caesar2/caesar.patch
	recipe-1.0.bb


I can think of symlinking at91sam9263ek to at572d940hf
but then you cannot have a defconfig file per board.

Maybe you can specify:

SRC_URI_append_at91sam9263ek += "file://../atmel/atmel.patch;patch=1"

but this has a fould look about it.

FOr the at91 patches, I took the easy way out and put all the patches
on www.at91.com, which is no good, since it has been down for
almost two days :-(



-- 
Best Regards
Ulf Samuelsson

Re: Common patch directory for a set of boards.

[Phil Blundell]

On Thu, 2009-08-13 at 22:49 +0200, Ulf Samuelsson wrote:
> Is there a way to store a patch which is applied to a list of boards,
> but not every board, in a common directory?
> 
> SRC_URI_append_at91sam9263ek += "file://atmel.patch;patch=1"
> SRC_URI_append_at32stk1000 += "file://atmel.patch;patch=1"
> SRC_URI_append_at572d940hf += "file://atmel.patch;patch=1"
> SRC_URI_append_beta1 += "file://beta.patch;patch=1"
> SRC_URI_append_beta2 += "file://beta.patch;patch=1"

So long as the leafnames don't collide, you can just put them in one of
the standard directories (files, ${PN}, ...) and everything will be
fine.

If the leafnames do collide then you can selectively add new directories
to FILESPATHPKG based on ${MACHINE}.

p.

Re: Common patch directory for a set of boards.

[Koen Kooi]

On 13-08-09 22:49, Ulf Samuelsson wrote:
> Is there a way to store a patch which is applied to a list of boards,
> but not every board, in a common directory?
>
> SRC_URI_append_at91sam9263ek += "file://atmel.patch;patch=1"
> SRC_URI_append_at32stk1000 += "file://atmel.patch;patch=1"
> SRC_URI_append_at572d940hf += "file://atmel.patch;patch=1"
> SRC_URI_append_beta1 += "file://beta.patch;patch=1"
> SRC_URI_append_beta2 += "file://beta.patch;patch=1"
> SRC_URI_append_beta3 += "file://beta.patch;patch=1"
> SRC_URI_append_caesar1 += "file://caesar.patch;patch=1"
> SRC_URI_append_caesar2 += "file://caesar.patch;patch=1"
>
> with a file system like:
>
> <recipe>
> 	recipe-1.0/atmel/atmel.patch
> 	recipe-1.0/beta/beta.patch
> 	recipe-1.0/caesar/caesar.patch
> 	recipe-1.0.bb

Sort of, for the above you would do:

SRC_URI_append_at91sam9263ek = " file://atmel/atmel.patch;patch=1"
SRC_URI_append_at32stk1000 = " file://atmel/atmel.patch;patch=1"
SRC_URI_append_at572d940hf = " file://atmel/atmel.patch;patch=1"
SRC_URI_append_beta1 = " file://beta/beta.patch;patch=1"
SRC_URI_append_beta2 = " file://beta/beta.patch;patch=1"
SRC_URI_append_beta3 = " file://beta/beta.patch;patch=1"
SRC_URI_append_caesar1 = " file://caesar/caesar.patch;patch=1"
SRC_URI_append_caesar2 = " file://caesar/caesar.patch;patch=1"

The linux-omap_2.6.29.bb recipe has something like that since I had to 
find a way to retain my sanity with that amount of patches.

regards,

Koen


>
>
> instead of
>
> <recipe>
> 	recipe-1.0/at91sam9263ek/atmel.patch
> 	recipe-1.0/at32stk1000/atmel.patch
> 	recipe-1.0/at572d940hf/atmel.patch
> 	recipe-1.0/beta1/beta.patch
> 	recipe-1.0/beta2/beta.patch
> 	recipe-1.0/beta3/beta.patch
> 	recipe-1.0/caesar1/caesar.patch
> 	recipe-1.0/caesar2/caesar.patch
> 	recipe-1.0.bb
>
>
> I can think of symlinking at91sam9263ek to at572d940hf
> but then you cannot have a defconfig file per board.
>
> Maybe you can specify:
>
> SRC_URI_append_at91sam9263ek += "file://../atmel/atmel.patch;patch=1"
>
> but this has a fould look about it.
>
> FOr the at91 patches, I took the easy way out and put all the patches
> on www.at91.com, which is no good, since it has been down for
> almost two days :-(
>
>
>

Re: Common patch directory for a set of boards.

[Marcin Juszkiewicz]

Dnia czwartek, 13 sierpnia 2009 o 22:49:10 Ulf Samuelsson napisał(a):
> Is there a way to store a patch which is applied to a list of boards,
> but not every board, in a common directory?

Bitbake checks:

files/
files/MACHINE/
PN/
PN/MACHINE/
PN-PV/
PN-PV/MACHINE/

Each of those directories can contain MACHINE related patch and 3 of them can 
contain files for recipe (never mind which MACHINE used).

> For the at91 patches, I took the easy way out and put all the patches
> on www.at91.com, which is no good, since it has been down for
> almost two days :-(

I would choose simpler one and apply AT91 patch by default as it does not 
change non-at91 devices.

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