From: Darren Hart <dvhart@linux.intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Drop dosfstools -d feature in favor of mtools mcopy
Date: Thu, 15 Dec 2011 22:36:52 -0800 [thread overview]
Message-ID: <4EEAE704.9060003@linux.intel.com> (raw)
In-Reply-To: <cover.1324015563.git.dvhart@linux.intel.com>
On 12/15/2011 10:14 PM, Darren Hart wrote:
> The dosfstools -d feature has been shown to be buggy, and even with Nitin's
> fixes applied to get directory hierarchies working, it still generates
> images that fail dosfsck and don't work with FAT32.
>
> This series presents an alternative means of populating our live images
> using mcopy from mtools.
>
> Applies on top of my earlier pull request:
> [PATCH 0/4] Fix grub efi menu, kernel messages, and live image dosfsck
I should add that I've built this with the fri2 BSP from the meta-intel
layer and tested EFI booting on 3 different platforms and legacy
SYSLINUX booting on 2 platforms - all using the same core-image-minimal
hddimg.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
prev parent reply other threads:[~2011-12-16 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 6:14 [PATCH 0/2] Drop dosfstools -d feature in favor of mtools mcopy Darren Hart
2011-12-16 6:14 ` [PATCH 1/2] bootimg: Use mcopy to construct the hddimg Darren Hart
2011-12-16 16:18 ` Richard Purdie
2011-12-16 6:14 ` [PATCH 2/2] dosfstools: Remove initial directory contents feature Darren Hart
2011-12-16 7:35 ` Koen Kooi
2011-12-16 10:52 ` Richard Purdie
2011-12-16 11:29 ` Koen Kooi
2011-12-16 15:40 ` Darren Hart
2011-12-16 15:47 ` Darren Hart
2011-12-16 6:36 ` Darren Hart [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=4EEAE704.9060003@linux.intel.com \
--to=dvhart@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.