From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: [RFC PATCH 0/3] Machine/tune files overhaul
Date: Mon, 11 Jul 2011 16:57:34 +0100 [thread overview]
Message-ID: <1310399854.20015.978.camel@rex> (raw)
We talked a bit about what might be needed to overhaul the machine/tune
config files to improve their usability, feature control and various
other things.
I've been experimenting locally with the following patchset. Its sent
based against poky since it requires a bitbake change and I also tested
beagleboard specifically and this was the easiest way to do it.
Obviously these can be split out easily enough.
The reason a bitbake change was needed was so that the "contains"
functionality could be used in core variables before base.bbclass is
loaded.
The patches themselves have further details about what they change and
why. The transition for this could be a little tricky but is dectable
when it hasn't happened by looking if TUNE_PKGARCH is set. Its easy to
add a check for that and error.
I've not completed the machine/tune files conversion preferring to
discuss the patches at this point before going any further.
Cheers,
Richard
reply other threads:[~2011-07-11 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1310399854.20015.978.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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.