From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: John Hawley <john.hawley@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] mkefidisk.sh: add deprecation warning to the output
Date: Wed, 9 Nov 2016 10:05:26 +0200 [thread overview]
Message-ID: <20161109080526.GA10546@linux.intel.com> (raw)
In-Reply-To: <77d63518-4bd4-0688-438b-07778f754733@intel.com>
On Tue, Nov 08, 2016 at 01:05:23PM -0800, John Hawley wrote:
> On 11/08/2016 12:44 PM, Randy Witt wrote:
> >>>> We should also document, the wic steps in wiki pages e.g.
> >>>> http://wiki.minnowboard.org/Yocto_Project
> >>> It's already documented in README.hardware:
> >>> https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/README.hardware
> >>>
> >>> And in Yocto manual:
> >>> http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#building-an-image-for-hardware
> >>>
> >>
> >> Thanks, now can you also nudge the minnowboard.org to do the same ?
> >>
> >
> > Pinging you John. :)
>
> So two obvious questions in reading the documentation off the YP site:
>
> 1) Does WIC actually handle the EFI partition for booting off of UEFI
> systems? (guessing yes, but wanted to double check)
Yes, it does.
> 2) I assume it only creates MBR based images, seeing as the suggestion
> is to DD the image down, how does GPT based images work since you can't
> (exactly) DD a GPT image down and have it work "correctly"?
>
Please, elaborate on "correctly". Do you mean that kernel will complain
that backup GPT header is not at the end of disk? This is not handled by
wic obviously. However, even without this image is bootable and
functional.
> Sorry, I'm sure that's covered somewhere else, just want to double check
> this will be ok before I update the documentation on MB
--
Regards,
Ed
prev parent reply other threads:[~2016-11-09 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 10:46 [PATCH] mkefidisk.sh: add deprecation warning to the output Ed Bartosh
2016-11-03 21:42 ` Khem Raj
2016-11-04 2:23 ` Christopher Larson
2016-11-07 23:02 ` Ed Bartosh
2016-11-07 23:00 ` Ed Bartosh
2016-11-07 23:44 ` Khem Raj
2016-11-08 20:44 ` Randy Witt
[not found] ` <77d63518-4bd4-0688-438b-07778f754733@intel.com>
2016-11-09 8:05 ` Ed Bartosh [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=20161109080526.GA10546@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=john.hawley@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox