From: Philip Balister <philip@balister.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: meta-ti@yoctoproject.org
Subject: Re: [RFC] u-boot recipe naming
Date: Fri, 20 Jan 2012 12:10:09 -0500 [thread overview]
Message-ID: <4F199FF1.8090606@balister.org> (raw)
In-Reply-To: <9F2249DF-2E56-4B4E-98CB-CE746690DCEC@dominion.thruhere.net>
On 01/20/2012 07:41 AM, Koen Kooi wrote:
> Hi,
>
> We currently have a problem with other layers including their own version of u-boot_2011.12.bb which confuses bitbake. To avoid such hassle in the future I'm going to propose using the kernel naming scheme for u-boot recipes as well:
>
> u-boot-denx_2011.12.bb -> u-boot from git.denx.de master + patches
> u-boot-ti_git.bb -> u-boot from git.denx.de ti branch + patches
> u-boot-psp-<soc>_git.bb -> u-boot from psp tree for $SoC + patches e.g. u-boot-psp-am18x_git.bb
Since I kind of started the problem, some background....
I'm very nervous using a shared u-boot recipe to ship to customers,
since there always seems to be some regression creeping in as other
people fix things for their hardware (the recent L2 cache turn off for
omap3 to fix omap4 booting comes to mind).
So I want to control my u-boot with an iron fist!
But, I tried to be lazy and not pollute the u-boot package namespace by
calling the recipe u-boot-usrp-e1xx. Apparently this did not work so well :)
Philip
>
> This should avoid filename based conflicts between layers and make it clearer which tree the recipe will be building.
>
> Thoughts/flames/opinions?
>
> regards,
>
> Koen
prev parent reply other threads:[~2012-01-20 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 12:41 [RFC] u-boot recipe naming Koen Kooi
2012-01-20 14:07 ` Andreas Müller
2012-01-20 14:20 ` Koen Kooi
2012-01-20 15:39 ` Tom Rini
2012-01-20 16:40 ` Koen Kooi
2012-01-20 17:10 ` Philip Balister [this message]
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=4F199FF1.8090606@balister.org \
--to=philip@balister.org \
--cc=koen@dominion.thruhere.net \
--cc=meta-ti@yoctoproject.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.