public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 6/8] omap3_beagle: add nand_spl support
Date: Sat, 08 Jan 2011 14:03:35 +0530	[thread overview]
Message-ID: <4D28215F.5080901@ti.com> (raw)
In-Reply-To: <AANLkTinWhT5x52LXzaZkaBE36kVh_Yz7DHGRjNtJpm9d@mail.gmail.com>

John,
On Saturday 08 January 2011 12:16 PM, John Rigby wrote:
> On Fri, Jan 7, 2011 at 11:33 PM, Aneesh V<aneesh@ti.com>  wrote:
>> Hi John,
>>
>> On Tuesday 28 December 2010 06:17 AM, John Rigby wrote:
>>>
>>> Signed-off-by: John Rigby<john.rigby@linaro.org>
>>> +
>>> +void board_init_f(unsigned long bootflag)
>>> +{
>>> +       nand_boot();
>>> +}
>>> +
>>
>> I see that you have added a call to nand_boot() in start.S too.
>> Which is the intended one?
>> If we jump to nand_boot() here bss will not be cleared, right?
>>
>> Also, I see potential issues in start.S that will prevent bss setup for
>> PRELOADERs. I will correct these in my patch.
>>
>> Best regards,
>> Aneesh
>>
>
> The call to nand_boot in board_init_f makes sense for platforms where
> the spl code does not need to be relocated because it has been loaded
> into SRAM by a mask boot rom.  The later nand_boot called from start.S
> is for the traditional nand_spl case where you are typically running
> in a 4K nand controller buffer so the code needs to be relocated to
> dram after dram init.
>
> Of course my only testing has been on OMAP3 which fits the first case.
>   I'm not sure if the second case even matters.  The arm7 platforms I
> know about all have rom boot loaders and large enough SRAM to run the
> spl u-boot in (OMAP[34]) or have boot headers that can be used to init
> dram before loading a full u-boot into dram (i.mx5[13]).
>
> Also, I was thinking that BSS would not be used in PRELOADERs but of
> the large SRAM case it certainly would be useful to have BSS.
>

Agree. So, how about this?
1. Call relocate_code() in board_init_f() with destination address same
as TEXT_BASE
2. start.S skips the relocation, clears the bss(this needs to be fixed)
and calls board_init_r
3. Call nand_boot() in board_init_r

This is what I am planning to do for OMAP4 preloader.

> This is all new territory since previously all platforms using
> nand_spl were of the small sram variety.
>
> John

Thanks,
Aneesh

  reply	other threads:[~2011-01-08  8:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28  0:47 [U-Boot] [RFC PATCH 0/8] Add nand_spl support for TI OMAP Beagle John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 1/8] NAND: nand_spl/nand_boot.c: add 16-bit and readid support John Rigby
2011-01-04 22:08   ` Scott Wood
2011-01-04 22:19     ` Scott Wood
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 2/8] armv7: add nand_spl support John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 3/8] OMAP3: and " John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 4/8] OMAP3: add dram timing constants from x-loader John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 5/8] NAND: omap_gpmc.c: add nand_spl support John Rigby
2011-01-04 22:24   ` Scott Wood
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 6/8] omap3_beagle: " John Rigby
2010-12-28  6:50   ` Aneesh V
2010-12-28  7:49     ` Dirk Behme
2010-12-29  0:27       ` John Rigby
2010-12-29  0:26     ` John Rigby
2010-12-29  5:37       ` Aneesh V
2011-01-04 22:26         ` Scott Wood
2011-01-08  6:33   ` Aneesh V
2011-01-08  6:46     ` John Rigby
2011-01-08  8:33       ` Aneesh V [this message]
2011-01-08 17:43         ` John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 7/8] mkimage: Add OMAP boot image support John Rigby
2011-01-04 13:43   ` Bedia, Vaibhav
2011-01-04 15:37     ` John Rigby
2010-12-28  0:47 ` [U-Boot] [RFC PATCH 8/8] OMAP3: Add ift target to top level Makefile John Rigby
2010-12-28  9:37   ` Dirk Behme
2010-12-28  6:17 ` [U-Boot] [RFC PATCH 0/8] Add nand_spl support for TI OMAP Beagle Aneesh V
2010-12-29  0:29   ` John Rigby
2010-12-28 19:49 ` Paulraj, Sandeep

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=4D28215F.5080901@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