From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Clean up omap3.inc
Date: Thu, 10 Nov 2011 21:27:01 +0100 [thread overview]
Message-ID: <j9hc2l$b8u$3@dough.gmane.org> (raw)
In-Reply-To: <4EBC2FEF.5020405@kernelconcepts.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 10-11-11 21:11, Florian Boor schreef:
> Hi all,
>
> omap3.inc currently contains this line:
>
> EXTRA_IMAGEDEPENDS += "u-boot x-load"
>
> This makes it hard to build for an OMAP3 based machine without providing
> a x-load configuration for it.
Wrong. You can do the following in your machine.conf:
require omap3.inc
EXTRA_IMAGEDEPENDS = "whatever"
to reset it.
> Actually I do not think hardcoding a particular bootloader for a class of
> SoC is a good idea at all. The selection whether a bootloader needs to be
> build and which one to select should be a matter of the machine
> configuration.
>
> Could we please get rid of this and fix the board descriptions?
In OE classic, no. In meta-ti the cleanup is already underway.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFOvDOVMkyGM64RGpERAunKAKC7udUOfCyn4wLKlPYg5/kMJPSNEgCgqgp9
lFTgVwMfsUQuNuC6mI8VZrg=
=ndzI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-11-10 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 20:11 RFC: Clean up omap3.inc Florian Boor
2011-11-10 20:27 ` Koen Kooi [this message]
2011-11-10 20:54 ` Florian Boor
2011-11-10 21:55 ` Tom Rini
2011-11-12 10:28 ` Paul Menzel
2011-11-12 21:21 ` Tom Rini
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='j9hc2l$b8u$3@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.