From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Common patch directory for a set of boards.
Date: Thu, 13 Aug 2009 23:23:18 +0200 [thread overview]
Message-ID: <h62087$ns5$1@ger.gmane.org> (raw)
In-Reply-To: <4A847C46.7090306@atmel.com>
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 :-(
>
>
>
next prev parent reply other threads:[~2009-08-13 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 20:49 Common patch directory for a set of boards Ulf Samuelsson
2009-08-13 21:18 ` Phil Blundell
2009-08-13 21:23 ` Koen Kooi [this message]
2009-08-20 19:38 ` Marcin Juszkiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='h62087$ns5$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.