From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Graeme Gregory <dp@xora.org.uk>, Jason Kridner <jdk@ti.com>,
"k-kooi@ti.com" <k-kooi@ti.com>
Subject: Re: [RFC oe-core] mkcard: Add a script to parition and format an SD Card
Date: Tue, 30 Aug 2011 10:31:58 +0100 [thread overview]
Message-ID: <1314696718.5939.305.camel@rex> (raw)
In-Reply-To: <CA+T6QPmfs0-_k+io3rviuTqxS9-qTT7q0y_=k6JNagB93TGG6Q@mail.gmail.com>
On Mon, 2011-08-29 at 17:03 -0400, Jason Kridner wrote:
> >>>
> >>> This script is BSP specific and shouldn't live in the OE-core layer.
> >>
> >> The only issue is this script is used from within the IMAGE_CMD_sdimg
> >> code which lives in OE-core (meta/classes/image_types.
> >
> > classes shouldn't be calling external scripts
> >
>
> Is the right approach to add parameters to the IMAGE_CMD_sdimg class
> such that it can be used generically to produce SD card images,
> instead of trying to move this to meta-ti? Should it perhaps be a bit
> closer to what is being done by the Linaro image tools [1]?
>
> [1] https://wiki.linaro.org/Source/ImageBuilding
I have heard multiple requests for making general SD card (or USB stick)
style images so I would love to see something generic. The script as it
stands looks like it has some issues due to requiring root access
(and/or special mounts).
There was a previous attempt at this in OE-Core:
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/classes/boot-directdisk.bbclass
but this has some issues making assumptions about sector size that
caused problems. On the plus side it demonstrated it was possible
without root...
Cheers,
Richard
next prev parent reply other threads:[~2011-08-30 9:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 6:12 [RFC oe-core] mkcard: Add a script to parition and format an SD Card Joel A Fernandes
2011-08-29 6:28 ` Joel A Fernandes
2011-08-29 7:58 ` Koen Kooi
2011-08-29 13:32 ` Andrea Adami
2011-08-29 13:37 ` Joel A Fernandes
2011-08-29 15:10 ` Joel A Fernandes
2011-08-29 17:33 ` Koen Kooi
2011-08-29 21:03 ` Jason Kridner
2011-08-29 23:08 ` Joel A Fernandes
2011-08-30 7:13 ` Koen Kooi
2011-08-30 16:46 ` Jason Kridner
2011-08-30 17:47 ` Koen Kooi
2011-08-30 21:08 ` Joel A Fernandes
2011-09-02 15:44 ` Joel A Fernandes
2011-09-02 16:00 ` Koen Kooi
2011-09-02 18:12 ` Joel A Fernandes
2011-08-30 9:31 ` Richard Purdie [this message]
2011-08-30 9:36 ` Graeme Gregory
2011-08-30 10:34 ` Koen Kooi
2011-08-30 10:38 ` Graeme Gregory
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=1314696718.5939.305.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=dp@xora.org.uk \
--cc=jdk@ti.com \
--cc=k-kooi@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox