From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 1/2] sunxi: retrieve FEL-provided values to environment variables
Date: Thu, 10 Sep 2015 20:34:20 +0200 [thread overview]
Message-ID: <55F1CD2C.9080803@redhat.com> (raw)
In-Reply-To: <1441289520-22749-2-git-send-email-bernhard.nortmann@web.de>
Hi,
On 03-09-15 16:11, Bernhard Nortmann wrote:
> This patch extends the misc_init_r() function on sunxi boards
> to test for the presence of a suitable "sunxi" SPL header. If
> found, and the loader ("fel" utility) provided non-zero values
> for either data address or size, then corresponding environment
> variables get set.
>
> misc_init_r() also sets (or clears) the "fel_booted" variable depending
> on the active boot device, using the same logic as spl_boot_device().
>
> The goal is to provide sufficient information (within the U-Boot
> environment) to make intelligent decisions on how to continue the boot
> process, allowing specific customizations for the "FEL boot" case.
>
> Signed-off-by: Bernhard Nortmann <bernhard.nortmann@web.de>
> ---
>
> board/sunxi/board.c | 59 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 59 insertions(+)
>
> diff --git a/board/sunxi/board.c b/board/sunxi/board.c
> index 9c855f6..ceab1e0 100644
> --- a/board/sunxi/board.c
> +++ b/board/sunxi/board.c
> @@ -516,6 +516,54 @@ void get_board_serial(struct tag_serialnr *serialnr)
> }
> #endif
>
> +#if !defined(CONFIG_SPL_BUILD)
> +static int check_signature(unsigned long io_addr, const char *signature,
> + int length)
> +{
> + do {
> + if (readb(io_addr) != *signature)
> + return 0;
> + io_addr++;
> + signature++;
> + } while (--length > 0);
> + return 1;
> +}
> +
> +#define SPL_SIGNATURE "SPL" /* marks "sunxi" header */
> +#define SPL_EXPECTED_VERSION 1
> +
> +/*
> + * Check the SPL header for the "sunxi" variant. If found: parse values
> + * that might have been passed by the loader ("fel" utility), and update
> + * the environment accordingly.
> + */
> +static void parse_spl_header(void)
> +{
> + uint8_t spl_header_version;
> + uint32_t fel_data_address;
> + uint32_t fel_data_size;
> +
> + if (check_signature(0x14, SPL_SIGNATURE, 3)) {
> + spl_header_version = readb(0x17);
> + if (spl_header_version == SPL_EXPECTED_VERSION) {
> + fel_data_address = readl(0x18);
> + fel_data_size = readl(0x1C);
> + if (fel_data_address)
> + setenv_hex("fel_data_addr", fel_data_address);
> + else
> + setenv("fel_data_addr", NULL);
> + if (fel_data_size)
> + setenv_hex("fel_data_size", fel_data_size);
> + else
> + setenv("fel_data_size", NULL);
> + } else {
> + printf("sunxi SPL header version mismatch: expected %u, got %u\n",
> + SPL_EXPECTED_VERSION, spl_header_version);
> + }
> + }
> +}
What if the user interrupts auto-boot with a fel provided boot.scr
and then does "saveenv" ?
Then we end up with a fel_data_addr and fel_data_size permanently
in the env.
At a minimum this function must always do:
setenv("fel_data_addr", NULL);
setenv("fel_data_size", NULL);
(rather then only when we've a spl fel header but no addr / size)
So that we do not end up trying to interpret old values ever.
Ideally though we would find another way not involving putting these
in the environment (not sure if that is easily doable).
> +#endif /* !defined(CONFIG_SPL_BUILD) */
> +
> #ifdef CONFIG_MISC_INIT_R
> int misc_init_r(void)
> {
> @@ -524,6 +572,17 @@ int misc_init_r(void)
> uint8_t mac_addr[6];
> int ret;
>
> +#if !defined(CONFIG_SPL_BUILD)
> + /* determine if we are running in FEL mode */
> + if (readl(4) != 0x4E4F4765 || readl(8) != 0x3054422E) { /* eGON.BT0 */
> + setenv("fel_booted", "1");
> + parse_spl_header();
> + } else {
> + /* not in FEL mode, delete/clear env var (if present) */
> + setenv("fel_booted", NULL);
Maybe clear all env variables here?
Or even better clear them all unconditionally, and then set
them when the checks succeed ?
> + }
> +#endif
> +
> ret = sunxi_get_sid(sid);
> if (ret == 0 && sid[0] != 0 && sid[3] != 0) {
> if (!getenv("ethaddr")) {
>
Regards,
Hans
next prev parent reply other threads:[~2015-09-10 18:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 14:11 [U-Boot] [RFC PATCH 0/2] sunxi: support FEL-provided environment vars and "fel" boot target Bernhard Nortmann
2015-09-03 14:11 ` [U-Boot] [RFC PATCH 1/2] sunxi: retrieve FEL-provided values to environment variables Bernhard Nortmann
2015-09-10 18:34 ` Hans de Goede [this message]
2015-09-11 9:08 ` Bernhard Nortmann
2015-09-12 11:58 ` Ian Campbell
2015-09-12 12:24 ` Hans de Goede
2015-09-14 13:12 ` Bernhard Nortmann
2015-09-03 14:12 ` [U-Boot] [RFC PATCH 2/2] sunxi: add "fel" boot target Bernhard Nortmann
2015-09-10 18:36 ` Hans de Goede
2015-09-11 9:31 ` Bernhard Nortmann
2015-09-12 12:48 ` Hans de Goede
2015-09-13 7:15 ` Ian Campbell
2015-09-14 10:33 ` Siarhei Siamashka
2015-09-14 11:42 ` Hans de Goede
2015-09-14 11:46 ` Hans de Goede
2015-09-26 21:03 ` Siarhei Siamashka
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=55F1CD2C.9080803@redhat.com \
--to=hdegoede@redhat.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