From: Jens Lucius <incnews@jenslucius.de>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: Different u-boot recipes (machine names and provider)
Date: Fri, 06 Mar 2015 13:29:13 +0100 [thread overview]
Message-ID: <54F99D99.6090806@jenslucius.de> (raw)
Hello,
I am working on a custom machine layer, which until now has it´s own
u-boot recipe for a custom u-boot.
I want to add a recipe for mainline u-boot additional to that. I have
defined a PREFERRED_PROVIDER_u-boot and
PREFERRED_PROVIDER_virtual/bootloader which point to the custom u-boot
to not break the current build, which can be changed to the mainline
u-boot if needed to build the mainline.
First question: Do I need to define both PREFERRED_PROVIDER (u-boot and
virtual/bootloader)? I have seen different approaches in different layers.
Now the hard part: custom u-boot and mainline u-boot have different
UBOOT_MACHINE values for the same hardware. Is it possible to define
different values for different u-boot recipes? Right now they are
defined in the machine configurations. Would it be possible (and
advisable) to define them in the u-boot recipes themselves? Or is there
another approach ?
Thanks,
Jens
next reply other threads:[~2015-03-06 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 12:29 Jens Lucius [this message]
2015-03-07 12:33 ` Different u-boot recipes (machine names and provider) Robert P. J. Day
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=54F99D99.6090806@jenslucius.de \
--to=incnews@jenslucius.de \
--cc=yocto@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.