All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: ed.bartosh@linux.intel.com
Cc: Gary Thomas <gary@mlbassoc.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: Create more than one image with WIC
Date: Tue, 14 Mar 2017 18:49:45 +0100	[thread overview]
Message-ID: <1489513785.6396.83.camel@intel.com> (raw)
In-Reply-To: <20170314171147.GA28498@linux.intel.com>

On Tue, 2017-03-14 at 19:11 +0200, Ed Bartosh wrote:
> On Mon, Mar 13, 2017 at 05:16:31PM +0100, Daniel Schultz wrote:
> > Do I have misunderstood the design of wic?
> >
> > I mean MMC and EMMC are very similar, but different in the
> > bootloader and it would be a overhead to create an extra image for
> > all EMMC images.
> 
> You don't need to create more than one rootfs with the same content. You
> can refer to the same rootfs in multiple .wks files, but the recipes
> have to be unique. In your example MMC and EMMC image recipes can create
> directories for boot partition and their .wks files can use those
> directories and common root directory produced by another recipe, e.g.
> by core-image-minimal.

But beware of interaction with rm_work.bbclass when doing that...

> It's not a big deal to run wic sequentially to produce multiple images,
> but it will create more problems than it solves I believe. It will be slower and
> will make a mess in image naming in deploy directory.

I personally would prefer to support generating more than one wic image
per image recipe. The different output files could be distinguished with
an additional suffix (".efi.wic", ".live.wiC", etc.) where the suffix is
either specified by the WKS file or the configuration where the WKS file
is selected - the latter might be a bit more flexible.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2017-03-14 17:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  9:44 Create more than one image with WIC Daniel Schultz
2017-03-08 10:57 ` Ed Bartosh
2017-03-08 13:41   ` Gary Thomas
2017-03-08 13:43     ` Ed Bartosh
2017-03-13 16:16       ` Daniel Schultz
2017-03-14 17:11         ` Ed Bartosh
2017-03-14 17:49           ` Patrick Ohly [this message]
2017-03-14 18:06             ` Ed Bartosh
2017-03-15  7:24               ` Patrick Ohly
2017-03-15 12:58                 ` Ed Bartosh
2017-03-15 13:39                   ` Patrick Ohly
2017-03-15 13:41                     ` Patrick Ohly
2017-03-15 14:01                       ` Ed Bartosh
2017-03-15 14:47                         ` Ed Bartosh
2017-03-15 15:09                           ` Patrick Ohly
2017-03-15 15:04                         ` Patrick Ohly

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=1489513785.6396.83.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=ed.bartosh@linux.intel.com \
    --cc=gary@mlbassoc.com \
    --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.