From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] pxa: Passing ATAGs to kernel don't work
Date: Tue, 9 Aug 2011 21:46:31 +0200 [thread overview]
Message-ID: <201108092146.31667.marek.vasut@gmail.com> (raw)
In-Reply-To: <4E4132BE.1040003@cit-ec.uni-bielefeld.de>
On Tuesday, August 09, 2011 03:14:38 PM Stefan Herbrechtsmeier wrote:
> Hi,
>
> after porting my board support from u-boot 2009.11 to 2011.06
> together with adding the relocation support
> the ATAGs passing don't work any more.
>
> I have add icache_disable() and dcache_disable()
> to my board_init() like on other pxa boards.
>
> It looks like the mapping of the Dcache as RAM is not cleared
> and will be re-enabled by the kernel.
Thanks for tracing this, can you submit a patch ?
>
> If I change the initial RAM mapping from first SDRAM partition start
> address to second unused SDRAM partition start address the ATAGs passing
> works.
>
> Can somebody confirm that the ATAGs passing works on u-boot 2011.06 for
> a pxa board.
>
> Is there any reason, that the initial RAM is mapped to SDRAM start
> address range?
I think now it can be changed. Maybe there was something about OneNAND IPL, I'm
not really sure anymore.
>
> Addition there is a bug in pxa_dram_init as it is called before relocation
> and want to trigger some refresh cycles by write some values to the SDRAM
> start address range but instead writes to the mapped initial RAM.
Patch is welcome please.
>
> Regards,
> Stefan
next prev parent reply other threads:[~2011-08-09 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 13:14 [U-Boot] pxa: Passing ATAGs to kernel don't work Stefan Herbrechtsmeier
2011-08-09 19:46 ` Marek Vasut [this message]
2011-08-10 10:47 ` Stefan Herbrechtsmeier
2011-08-17 10:01 ` Stefan Herbrechtsmeier
2011-08-17 10:07 ` Marek Vasut
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=201108092146.31667.marek.vasut@gmail.com \
--to=marek.vasut@gmail.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