From: Eric Nelson <eric.nelson@boundarydevices.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Cc: Troy <troy.kisky@boundarydevices.com>
Subject: Kernel 3.10.31 and SD card numbering and boot scripts
Date: Thu, 09 Oct 2014 17:00:58 -0700 [thread overview]
Message-ID: <543721BA.9080804@boundarydevices.com> (raw)
Hi all,
The 3.10.31 kernel contains a nifty bit of code from Sascha Hauer
that addresses the question of SD card numbering (device naming)
quite well:
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/commit/drivers/mmc/card/block.c?h=imx_3.10.31_1.1.0_beta&id=5f9447e5d97060207c4742d5a06e5548de45972d
https://www.mail-archive.com/linux-mmc@vger.kernel.org/msg26472.html
Unfortunately, it also changes the requirements for the kernel
command-line and breaks our boot scripts.
This is probably a good time to ask a related question about
where we're keeping boot scripts.
We have been compiling boot scripts out of our U-Boot tree
from a Yocto-specific "6x_bootscript-yocto.txt" that implements
the conventions of the Freescale Community BSP (kernel in
the root of partition 1 and rootfs in partition 2).
Since boot scripts have dependencies on a lot of things, it's
not clear to me that they belong in the U-Boot source tree
and that a Yocto-specific boot script really belongs directly
in the Yocto tree somewhere.
Since a Yocto build knows about the PREFERRED_VERSION of the
kernel, it would be straightforward to have multiple versions
of a boot script.
Otherwise, we'd need to place a couple of versions in the
U-Boot tree:
6x_bootscript-yocto.txt
6x_bootscript-yocto-after-3.10.17.txt
and we'd also need some logic in u-boot-script-boundary.bb
to choose between them.
Before crafting a patch to do this, I'd like to get some feedback.
Regards,
Eric
next reply other threads:[~2014-10-10 0:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 0:00 Eric Nelson [this message]
2014-10-10 1:18 ` Kernel 3.10.31 and SD card numbering and boot scripts Otavio Salvador
2014-10-10 1:45 ` Eric Nelson
2014-10-10 12:23 ` Otavio Salvador
2014-10-10 14:04 ` Eric Nelson
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=543721BA.9080804@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=meta-freescale@yoctoproject.org \
--cc=troy.kisky@boundarydevices.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 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.