From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>, josh@linux.intel.com
Subject: [PATCH 0/4][edison] Fix bootimg bug 2138 for 1.1.2
Date: Thu, 5 Apr 2012 14:09:45 -0700 [thread overview]
Message-ID: <cover.1333660034.git.dvhart@linux.intel.com> (raw)
Backport the following patches to edison. The backport involves massaging
this minimal set of patches to apply to bootimg.bbclass without pulling
in the refactoring or EFI support added in master about the same time.
These patches have been tested by building atom-pc core-image-minimal with
edison, a dosfsck and mount test on resulting image, and booting on the n450.
The following changes since commit 0fbd6a161576b2cafa8583adde0ffb15347c884a:
poky.conf: Bumping SKD_VERSION (2012-03-14 15:49:33 -0700)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib dvhart/edison/bug/2138
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/edison/bug/2138
Darren Hart (4):
bootimg: Use mcopy to construct the hddimg
bootimg: Account for FAT filesystem overhead in image size
bootimg: Fix a math thinko in the block count calculation
bootimg: Do not force FAT32 on all images, it violates the FAT
specification
meta/classes/bootimg.bbclass | 53 ++++++++++++++++++++++++++++++++++++-----
1 files changed, 46 insertions(+), 7 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-04-05 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 21:09 Darren Hart [this message]
2012-04-05 21:09 ` [PATCH 1/4] bootimg: Use mcopy to construct the hddimg Darren Hart
2012-04-05 21:09 ` [PATCH 2/4] bootimg: Account for FAT filesystem overhead in image size Darren Hart
2012-04-05 21:09 ` [PATCH 3/4] bootimg: Fix a math thinko in the block count calculation Darren Hart
2012-04-05 21:09 ` [PATCH 4/4] bootimg: Do not force FAT32 on all images, it violates the FAT specification Darren Hart
2012-04-06 17:33 ` [PATCH 0/4][edison] Fix bootimg bug 2138 for 1.1.2 Joshua Lock
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=cover.1333660034.git.dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=josh@linux.intel.com \
--cc=yocto@yoctoproject.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.