From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 5/8] omap-common: SYS_BOOT-based fallback boot device selection for peripheral boot
Date: Thu, 2 Jul 2015 15:10:43 -0400 [thread overview]
Message-ID: <20150702191043.GT28577@bill-the-cat> (raw)
In-Reply-To: <1435789184-6815-6-git-send-email-contact@paulk.fr>
On Thu, Jul 02, 2015 at 12:19:41AM +0200, Paul Kocialkowski wrote:
> OMAP devices might boot from peripheral devices, such as UART or USB.
> When that happens, the U-Boot SPL tries to boot the next stage (complete U-Boot)
> from that peripheral device, but in most cases, this is not a valid boot device.
>
> This introduces a fallback option that reads the SYS_BOOT pins, that are used by
> the bootrom to determine which device to boot from. It is intended for the
> SYS_BOOT value to be interpreted in the memory-preferred scheme, so that the
> U-Boot SPL can load the next stage from a valid location.
>
> Practically, this options allows loading the U-Boot SPL through USB and have it
> load the next stage according to the memory device selected by SYS_BOOT instead
> of stalling.
Can you elaborate on this more please? The normal flow is that you load
SPL via UART and then load U-Boot via UART, or SPL via USB RNDIS and
then U-Boot via USB RNDIS. It sounds like you're changing things so
that you load first via UART and then via say SD (or whatever the pins
would be set for) unless you have the bits enabled for loading the next
stage via that peripheral, which is the default case.
Now, I know you didn't do this just for fun, so what's the use case you
have here exactly? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150702/9637b28a/attachment.sig>
next prev parent reply other threads:[~2015-07-02 19:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 22:19 [U-Boot] [PATCH v4 0/8] omap-common: Common boot code OMAP3 support and SYS_BOOT-based fallback boot device Paul Kocialkowski
2015-07-01 22:19 ` [U-Boot] [PATCH v4 1/8] omap-common: Common boot code OMAP3 support and cleanup Paul Kocialkowski
2015-07-14 22:11 ` Tom Rini
2015-07-14 23:04 ` Paul Kocialkowski
2015-07-01 22:19 ` [U-Boot] [PATCH v4 2/8] omap: SPL boot devices cleanup and completion Paul Kocialkowski
2015-07-14 22:11 ` Tom Rini
2015-07-01 22:19 ` [U-Boot] [PATCH v4 3/8] omap-common: Boot device define instead of hardcoded value Paul Kocialkowski
2015-07-14 22:11 ` Tom Rini
2015-07-01 22:19 ` [U-Boot] [PATCH v4 4/8] siemens-am33x-common: Hardcoded value instead of non-included define Paul Kocialkowski
2015-07-14 22:11 ` Tom Rini
2015-07-01 22:19 ` [U-Boot] [PATCH v4 5/8] omap-common: SYS_BOOT-based fallback boot device selection for peripheral boot Paul Kocialkowski
2015-07-02 19:10 ` Tom Rini [this message]
2015-07-02 19:53 ` Paul Kocialkowski
2015-07-09 7:59 ` Lokesh Vutla
2015-07-09 8:27 ` Paul Kocialkowski
2015-07-14 19:17 ` Tom Rini
2015-07-15 0:35 ` Paul Kocialkowski
2015-07-14 22:12 ` Tom Rini
2015-07-01 22:19 ` [U-Boot] [PATCH v4 6/8] omap3: Definitions for SYS_BOOT-based fallback boot device selection Paul Kocialkowski
2015-07-14 22:12 ` Tom Rini
2015-07-01 22:19 ` [U-Boot] [PATCH v4 7/8] omap4: " Paul Kocialkowski
2015-07-14 22:12 ` Tom Rini
2015-07-01 22:19 ` [U-Boot] [PATCH v4 8/8] omap5: " Paul Kocialkowski
2015-07-14 22:12 ` Tom Rini
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=20150702191043.GT28577@bill-the-cat \
--to=trini@konsulko.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