From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Anders Darander <anders@chargestorm.se>,
Koen Kooi <koen@dominion.thruhere.net>,
damien.lespiau@intel.com, "Wold, Saul" <saul.wold@intel.com>
Subject: Re: RFC: Braindump on Bootloaders, Image Types, and Installers
Date: Fri, 08 Jun 2012 16:49:13 -0700 [thread overview]
Message-ID: <4FD28F79.5030003@linux.intel.com> (raw)
In-Reply-To: <4FCF8999.4000405@windriver.com>
Restoring the CC list.
On 06/06/2012 09:47 AM, Mark Hatle wrote:
> I don't have specific comments below, but I can share some of what I will be
> working on for my company in the next 6 months or so.
>
> I will be working on moving the image generation: filesystem construction,
> filesystem -> image generation, and similar into a framework that can reside
> externally of OE-core/bitbake.
>
> The idea is that we should have a single framework that can construct the
> filesystem from the package feeds, construct the images (using the parameters
> and more that you list below), and then eventually deploy these images onto the
> target system.
>
> Having this external of oe-core will allow it to be invoked by OE-core, as it is
> today, as well as for on-target installers, people who want to start w/ the
> package feeds, etc.
>
> I believe this fits within the vision you have below, but may throw in some
> issues when we start talking about external capable tooling.
I've been considering external tools to assemble images as well to keep
root permission requirements out of bitbake. This would greatly simplify
partitioning and loop mounting images. Preparing filesystem images in
bitbake, and bootable images outside of bitbake seems like a reasonable
approach to me as well.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-06-09 0:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 20:54 RFC: Braindump on Bootloaders, Image Types, and Installers Darren Hart
2012-06-06 12:39 ` Burton, Ross
2012-06-06 16:28 ` Darren Hart
2012-06-06 16:47 ` Mark Hatle
2012-06-07 16:11 ` Koen Kooi
2012-06-08 6:16 ` Saul Wold
2012-06-08 7:38 ` Koen Kooi
2012-06-08 23:49 ` Darren Hart [this message]
2012-06-07 6:52 ` Anders Darander
-- strict thread matches above, loose matches on Subject: below --
2012-06-05 21:58 Daniel Lazzari
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=4FD28F79.5030003@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=anders@chargestorm.se \
--cc=damien.lespiau@intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox