From: Patrick Ohly <patrick.ohly@intel.com>
To: ed.bartosh@linux.intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bootimg-efi.py: Use IMGDEPLOYDIR instead of DEPLOY_DIR_IMAGE for initrd
Date: Mon, 03 Jul 2017 16:10:05 +0200 [thread overview]
Message-ID: <1499091005.5259.84.camel@intel.com> (raw)
In-Reply-To: <20170703124424.GA5790@linux.intel.com>
On Mon, 2017-07-03 at 15:44 +0300, Ed Bartosh wrote:
> On Mon, Jul 03, 2017 at 11:27:53AM +0200, Patrick Ohly wrote:
> > On Mon, 2017-07-03 at 11:36 +0300, Ed Bartosh wrote:
> > > On Fri, Jun 30, 2017 at 10:53:30AM -0700, Alejandro Hernandez wrote:
> > > > When using wic to create an image from a certain build, wic is expecting
> > > > to find initrd at the final destination of our images (DEPLOY_DIR_IMAGE),
> > > > which is wrong, since the initrd file has not been copied to the final
> > > > directory yet,
> > >
> > > Is it possible to ensure that initrd is deployed before wic is run by
> > > making do_image_wic depend on initrd deploy task?
> >
> > Not in this case, because both do_image_wic and do_image_cpio share the
> > same deploy task.
>
> Now I understand what's going on here. Basically Alejandro is trying to
> use one format of the same image in another. It's like trying to put
> .wic image inside ext2 image or something similar.
>
> I believe it doesn't fit current design of oe image creation system.
> I'd suggest to use different image recipes to achieve this.
Yes, that is also my preferred solution (see other email from this
morning).
--
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.
prev parent reply other threads:[~2017-07-03 14:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 17:53 [PATCH] bootimg-efi.py: Use IMGDEPLOYDIR instead of DEPLOY_DIR_IMAGE for initrd Alejandro Hernandez
2017-06-30 18:43 ` Patrick Ohly
2017-06-30 20:38 ` Alejandro Hernandez
2017-07-01 15:09 ` Patrick Ohly
2017-07-01 21:48 ` Alejandro Hernandez
2017-07-03 6:45 ` Patrick Ohly
2017-07-03 9:06 ` Ed Bartosh
2017-07-03 8:36 ` Ed Bartosh
2017-07-03 9:27 ` Patrick Ohly
2017-07-03 12:44 ` Ed Bartosh
2017-07-03 14:10 ` Patrick Ohly [this message]
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=1499091005.5259.84.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=ed.bartosh@linux.intel.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.