From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: State of the art for creating an image that you can dd to an SD card
Date: Thu, 26 Jun 2014 14:00:46 -0400 [thread overview]
Message-ID: <20140626180046.GF1580@denix.org> (raw)
In-Reply-To: <CAFZh4h80FCq=6u-enoDTzreQhBRB+Sgko+8hRzWRrk1EoS00nw@mail.gmail.com>
On Wed, Jun 25, 2014 at 03:04:31PM -0400, Brian Hutchinson wrote:
> On Wed, Jun 25, 2014 at 2:38 PM, Philip Balister <philip@balister.org> wrote:
> > On 06/25/2014 03:07 AM, Paul Eggleton wrote:
> >> On Tuesday 24 June 2014 16:14:58 Philip Balister wrote:
> >>> What's the best available solution for creating an image you can dd to
> >>> an SD card? It seems like this wheel has been invented several times and
> >>> I am wondering if people are converging on one approach.
> >>>
> >>> Bonus points for resizing the linux partition.
> >>>
> >>> How are people doing this today?
> >>
> >> I think wic has seen some uptake and enhancement since its introduction a
> >> couple of releases ago. It has certainly worked for me in writing SD cards for
> >> Galileo. We seem to be a bit short on documentation for it though...
> >
> > Googling for "wic sd" doesn't help. I've seen some commits, so I'll take
> > a look in the meta data.
> >
> > Philip
>
> I think he's talking about:
> http://patchwork.openembedded.org/patch/59059/
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=3847
A lot of good info is hidden in those 2 obscure places! :)
How about copying all that to a Wiki page for starters?
--
Denys
next prev parent reply other threads:[~2014-06-26 18:01 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
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 [this message]
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=20140626180046.GF1580@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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