From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v5, 1/8] omap-common: Common boot code OMAP3 support and cleanup
Date: Tue, 28 Jul 2015 10:58:57 -0400 [thread overview]
Message-ID: <20150728145857.GP25532@bill-the-cat> (raw)
In-Reply-To: <1436968946-16025-2-git-send-email-contact@paulk.fr>
On Wed, Jul 15, 2015 at 04:02:19PM +0200, Paul Kocialkowski wrote:
> This introduces OMAP3 support for the common omap boot code, as well as a
> major cleanup of the common omap boot code.
>
> First, the omap_boot_parameters structure becomes platform-specific, since its
> definition differs a bit across omap platforms. The offsets are removed as well
> since it is U-Boot's coding style to use structures for mapping such kind of
> data (in the sense that it is similar to registers). It is correct to assume
> that romcode structure encoding is the same as U-Boot, given the description
> of these structures in the TRMs.
>
> The original address provided by the bootrom is passed to the U-Boot binary
> instead of a duplicate of the structure stored in global data. This allows to
> have only the relevant (boot device and mode) information stored in global data.
> It is also expected that the address where the bootrom stores that information
> is not overridden by the U-Boot SPL or U-Boot.
>
> The save_omap_boot_params is expected to handle all special cases where the data
> provided by the bootrom cannot be used as-is, so that spl_boot_device and
> spl_boot_mode only return the data from global data.
>
> All of this is only relevant when the U-Boot SPL is used. In cases it is not,
> save_boot_params should fallback to its weak (or board-specific) definition.
> save_omap_boot_params should not be called in that context either.
>
> Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
Applied to u-boot/master, 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/20150728/015f5129/attachment.sig>
next prev parent reply other threads:[~2015-07-28 14:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 14:02 [U-Boot] [PATCH v5 0/8] omap-common: Common boot code OMAP3 support and SYS_BOOT-based fallback boot device Paul Kocialkowski
2015-07-15 14:02 ` [U-Boot] [PATCH v5 1/8] omap-common: Common boot code OMAP3 support and cleanup Paul Kocialkowski
2015-07-28 14:58 ` Tom Rini [this message]
2015-07-15 14:02 ` [U-Boot] [PATCH v5 2/8] omap: SPL boot devices cleanup and completion Paul Kocialkowski
2015-07-28 14:59 ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 3/8] omap-common: Boot device define instead of hardcoded value Paul Kocialkowski
2015-07-28 14:59 ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 4/8] siemens-am33x-common: Hardcoded value instead of non-included define Paul Kocialkowski
2015-07-28 14:59 ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 5/8] omap-common: SYS_BOOT-based fallback boot device selection for peripheral boot Paul Kocialkowski
2015-07-28 14:59 ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-08-25 8:40 ` Schmelzer Hannes
2015-08-25 12:27 ` Paul Kocialkowski
2015-08-25 12:52 ` Hannes Schmelzer
2015-08-25 14:44 ` Paul Kocialkowski
2015-07-15 14:02 ` [U-Boot] [PATCH v5 6/8] omap3: Definitions for SYS_BOOT-based fallback boot device selection Paul Kocialkowski
2015-07-28 14:59 ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 7/8] omap4: " Paul Kocialkowski
2015-07-28 14:59 ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-15 14:02 ` [U-Boot] [PATCH v5 8/8] omap5: " Paul Kocialkowski
2015-07-28 14:59 ` [U-Boot] [U-Boot, v5, " Tom Rini
2015-07-26 16:29 ` [U-Boot] [PATCH v5 0/8] omap-common: Common boot code OMAP3 support and SYS_BOOT-based fallback boot device Paul Kocialkowski
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=20150728145857.GP25532@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 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.