From: Kinsella, Ray <ray.kinsella@intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7] board: add support for Intel Galileo Gen 2
Date: Mon, 16 Nov 2015 18:17:02 +0000 [thread overview]
Message-ID: <1447697823.26837.3.camel@intel.com> (raw)
In-Reply-To: <1447694994.6537.51.camel@intel.com>
ignore this - in working out my reasoning below, I have worked out an
alternative that allows the consolidation into a single file.
Ray K
On Mon, 2015-11-16 at 17:29 +0000, Kinsella, Ray wrote:
> > > diff --git a/board/intel/galileo/genimage.cfg b/board/intel/galileo/genimage.cfg
> > > new file mode 100644
> > > index 0000000..b1db6f7
> > > --- /dev/null
> > > +++ b/board/intel/galileo/genimage.cfg
> > > @@ -0,0 +1,15 @@
> > > +image sdcard.img {
> > > + hdimage {
> > > + }
> > > +
> > > + partition boot {
> > > + partition-type = 0xC
> > > + image = "efi-part.vfat"
> >
> > Doesn't genimage allow to specify this in a single file?
>
> Hi Arnout,
>
> Needed to do a bit of investigation to refresh my memory here - on why I
> implemented this way. To understand what genimage does requires a bit of
> understanding of what tools it is using under the hood. Typically using
> hdimage and vfat are mutually exclusive.
>
> * hdimage - typically I use hdimage where I have 1 or more partitions I
> want to aggregate into a single image ... so I want pull the ext3/ext4
> image created by buildroot as a partition.
> * vfat - typically I use vfat where I want to use an overlay fs, i.e. a
> sdcard that has been formatted as vfat with a EFI, Kernel, Ext3 overlay
> image and perhaps also an initramfs.
>
> So you are usually doing one or the other. The constraint with Galileo
> Gen 2 is that it's UEFI BIOS can only read VFAT or EFI partitions when
> looking for bootloader EFI binaries like grub-efi or gummiboot. So this
> leaves me with a couple of options:-
>
> * I can use hdimage - I can create the VFAT/EFI partition myself
> calling mtools, and then use hdimage above to aggregate this partition
> into an image along with the rootfs image produced by buildroot
> * I can use vfat with the overlay fs approach, however this typically
> comes with a boottime performance penalty.
>
> So my approach is as follows ...
>
> * Use genimage vfat instead to create my first 'image' as vfat, under
> the hood genimage uses dd + mkfs.vfat to create the image and then uses
> mtools (mmd + mcopy) to copy in the EFI binaries.
> * I then use hdimage to pull in the vfat image above as an EFI parition
> and the ext3 image created by buildroot as the rootfs partition.
>
> For me this was simplest approach to layout the sdcard image as the
> Galileo requires, much simpler than rewriting lots of mtools logic that
> already exists in genimage. Make sense ?
>
> Ray K
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2015-11-16 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 16:48 [Buildroot] [PATCH v7] board: add support for Intel Galileo Gen 2 Kinsella, Ray
2015-10-28 22:28 ` Arnout Vandecappelle
2015-11-10 17:10 ` Kinsella, Ray
2015-11-10 19:59 ` Arnout Vandecappelle
2015-11-16 17:29 ` Kinsella, Ray
2015-11-16 18:17 ` Kinsella, Ray [this message]
2015-11-04 20:53 ` Thomas Petazzoni
2015-11-05 8:46 ` Kinsella, Ray
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=1447697823.26837.3.camel@intel.com \
--to=ray.kinsella@intel.com \
--cc=buildroot@busybox.net \
/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.