From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: State of the art for creating an image that you can dd to an SD card
Date: Thu, 26 Jun 2014 19:50:10 -0400 [thread overview]
Message-ID: <20140626235010.GI1580@denix.org> (raw)
In-Reply-To: <CAK8F28kHj_JJh84XWcVt7wy2p70BvpV+WCF4n2r1=FWrRQT8cQ@mail.gmail.com>
On Thu, Jun 26, 2014 at 12:23:35PM -0700, Ash Charles wrote:
> On Thu, Jun 26, 2014 at 11:09 AM, Denys Dmytriyenko <denis@denix.org> wrote:
> > "CHS business", as Philip called it, was only partially required in the early
> > days of OMAP3 SoCs few years ago, due to some "specific" FAT implementation of
> > the BootROM. These days it's not required on modern Sitara SoCs.
> Which OMAP3 SOCs need the CHS business?
Definitely OMAP34xx/35xx family. I'm not very sure if OMAP36xx/37xx had a
fixed BootROM already, but probably it had, as Beagleboard xM was much more
forgiving to SD card format, IIRC...
--
Denys
next prev parent reply other threads:[~2014-06-26 23:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 23:14 State of the art for creating an image that you can dd to an SD card Philip Balister
2014-06-25 0:12 ` Joe MacDonald
2014-06-25 10:07 ` Paul Eggleton
2014-06-25 18:38 ` Philip Balister
2014-06-25 18:55 ` Denys Dmytriyenko
2014-06-25 23:13 ` Diego Sueiro
2014-06-25 23:27 ` Philip Balister
2014-06-25 23:45 ` Diego Sueiro
2014-06-26 18:09 ` Denys Dmytriyenko
2014-06-26 19:23 ` Ash Charles
2014-06-26 19:28 ` Philip Balister
2014-06-26 20:12 ` Ash Charles
2014-06-26 23:43 ` Denys Dmytriyenko
2014-06-26 23:46 ` Philip Balister
2014-06-26 23:55 ` Denys Dmytriyenko
2014-06-26 23:50 ` Denys Dmytriyenko [this message]
2014-06-26 23:53 ` Ash Charles
2014-06-26 22:06 ` Diego Sueiro
2014-06-25 19:04 ` Brian Hutchinson
2014-06-26 18:00 ` Denys Dmytriyenko
2014-07-05 22:05 ` Otavio Salvador
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=20140626235010.GI1580@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@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.