From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fwd: Re: [PATCH v2 10/22] omap4: utility function to identify the context of hw init
Date: Tue, 17 May 2011 11:56:59 +0530 [thread overview]
Message-ID: <4DD21533.20609@ti.com> (raw)
Copying to the list.
Accidentally missed it last time.
-------- Original Message --------
Subject: Re: [U-Boot] [PATCH v2 10/22] omap4: utility function to
identify the context of hw init
Date: Mon, 16 May 2011 20:03:52 +0530
From: Aneesh V <aneesh@ti.com>
To: Wolfgang Denk <wd@denx.de>
Hi Wolfgang,
On Monday 16 May 2011 01:29 AM, Wolfgang Denk wrote:
> Dear Aneesh V,
>
> In message<1305472900-4004-11-git-send-email-aneesh@ti.com> you wrote:
>> The basic hardware init of OMAP4(s_init()) can happen in 4
>> different contexts:
>> 1. SPL running from SRAM
>> 2. U-Boot running from FLASH
>> 3. Non-XIP U-Boot loaded to SDRAM by SPL
>> 4. Non-XIP U-Boot loaded to SDRAM by ROM code using the
>> Configuration Header feature
> ...
>> + if (uboot_loaded_by_spl())
>> + return OMAP_INIT_CONTEXT_UBOOT_LOADED_BY_SPL;
>> + else if (running_from_sdram())
>> + return OMAP_INIT_CONTEXT_UBOOT_LOADED_BY_CH;
>
> For reasons of consistency, should this not better be
> OMAP_INIT_CONTEXT_UBOOT_LOADED_BY_ROM ?
Ok.
>
>> + return OMAP_INIT_CONTEXT_XIP_UBOOT;
>
> What exactly is OMAP_INIT_CONTEXT_XIP_UBOOT?
>
> Do you mean the situation when booting from NOR flash, before
> relocation?
Yes, this is for the NOR case.
>
> Eventually the "loaded by" definition is not so good, as it does not
> really cover the NOR boot case.
Please note that "loaded by" definition is not there for all the
options. The definition is the 'context' in which the init code is
executing.
>
>
>> +/* HW Init Context */
>> +#define OMAP_INIT_CONTEXT_SPL 0
>> +#define OMAP_INIT_CONTEXT_XIP_UBOOT 1
>> +#define OMAP_INIT_CONTEXT_UBOOT_LOADED_BY_SPL 2
>> +#define OMAP_INIT_CONTEXT_UBOOT_LOADED_BY_CH 3
>
> Boot from NOR?
>
> Best regards,
>
> Wolfgang Denk
>
reply other threads:[~2011-05-17 6:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DD21533.20609@ti.com \
--to=aneesh@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