From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] dra7xx: booting from eMMC raw boot partition
Date: Thu, 21 Nov 2013 14:02:14 -0500 [thread overview]
Message-ID: <20131121190214.GQ420@bill-the-cat> (raw)
In-Reply-To: <528E4ED8.8030809@ruggedcom.com>
On Thu, Nov 21, 2013 at 01:20:08PM -0500, Richard Retanubun wrote:
> On 21/11/13 01:09 PM, Tom Rini wrote:
> >I've done RAW mode booting on my omap5_uevm as well as am335x-based
> >platforms, on SD card and eMMC. But in the case of eMMC it's always the
> >user partitions. I suspect the answer is that for automotive booting
> >you need silicon that supports that, much like the difference between HS
> >and GP devices.
>
> Agreed. If by silicon you mean the CPU, then all the docs I've seen
> (the TRM for DRA7xx and SYSBOOT in automotive peripheral mode seem to
> indicate that the SoC is capable or Raw eMMC boot partition booting.
Well, I think it's a little more than that, perhaps depending on eFuse
stuff or similar as well.
> >I'm not sure what code in p-ti-u-boot-2013.04 hasn't
> >been merged to mainline but if you can give me some pointers I can go
> >and poke some folks.
> Thanks for the offer, poke gently :)
>
> I think it is essentially all the code that touches /drivers/mmc/spl_mmc.c on the ti tree here:
>
> http://git.omapzoom.org/?p=repo/u-boot.git;a=history;f=drivers/mmc/spl_mmc.c;h=bd7e34bed35a1518d714232a8aedbc2e38d43632;hb=refs/heads/p-ti-u-boot-2013.04
Ah, OK, I see where the confusion comes from. There are three things in
that tree, roughly, from reading the commits on that file:
1) Android Fastboot support
2) A custom version of "falcon mode"
3) Other odds and ends changes
Looking over the code there, one might think mainline doesn't support
eMMC booting or needs changes, because we always say "use mmc device 0".
That's fine however because SPL looks at if we came in (hardware
numbering now) from MMC1 or MMC2 and then only register that MMC device.
So we're always s/w wise mmc device 0.
There's a few patches floating around to add Fastboot support to
mainline, and I'd love to see one pushed all the way to mainline.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131121/3b5891bc/attachment.pgp>
prev parent reply other threads:[~2013-11-21 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 22:27 [U-Boot] dra7xx: booting from eMMC raw boot partition Richard Retanubun
2013-11-20 22:39 ` Shankar Rao
2013-11-21 5:39 ` Michael Pratt
2013-11-21 14:02 ` Richard Retanubun
2013-11-21 16:42 ` Rao, Shankar
2013-11-21 16:49 ` Tom Rini
2013-11-21 17:57 ` Richard Retanubun
2013-11-21 18:09 ` Tom Rini
2013-11-21 18:20 ` Richard Retanubun
2013-11-21 19:02 ` Tom Rini [this message]
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=20131121190214.GQ420@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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