From: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] UNCACHED_SDRAM macro issue
Date: Fri, 15 Feb 2008 09:43:15 +0900 [thread overview]
Message-ID: <47B4E023.3080305@necel.com> (raw)
In-Reply-To: <1202979717.29669.87.camel@cartesio>
Luigi 'Comio' Mantellini wrote:
>> So it seems Alchemy-based SoC. if so,
>>
>
> No. I'm working on a SoC that uses a IP core from MIPS (mips4kec). The
> mips core should be (formally) a standard mips core.
>
>>> What I need to change on my board specific u-boot in order to use the
>>> KSEG1 address space?
>> what do you mean "in order to use the KSEG1 address space?" I'm not
>> familiar with Au1XXX, but you might need CONFIG_AU1X00 in your board
>> config. Some URLs added[1][2].
>>
>
> The CONFIG_AU1X00 doesn't work for me. from datasheet there aren't
> differences between my SoC and the standalone mips4kec. This is the
> memory map how depicted by the datasheet:
>
> 0x00000000--0x7fffffff KUser - Cached / Mapped
> 0x80000000--0x9fffffff KSEG0 - Cached / Unmapped
> 0xA0000000--0x9fffffff KSEG1 - Uncached / Unmapped
> ....
Then I'm confused. Physical address map of your SoC will be helpful.
Where is the SDRAM mapped to?
> I think that on my application the UNCACHED_SDRAM should map the address
> on KSEG1 (how it is now) but this simply doesn't work. Instead, using
> the PHYSADDR(a) macro... the kernel is able to start.
>
> I suspect that there are issues on cache management. Can be?
IMHO it's not related to cache.
Shinya
next prev parent reply other threads:[~2008-02-15 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 8:59 [U-Boot-Users] UNCACHED_SDRAM macro issue Luigi 'Comio' Mantellini
2008-02-14 3:55 ` Shinya Kuribayashi
2008-02-14 9:01 ` Luigi 'Comio' Mantellini
2008-02-15 0:43 ` Shinya Kuribayashi [this message]
2008-02-15 9:11 ` Shinya Kuribayashi
2008-02-16 9:06 ` Shinya Kuribayashi
2008-02-16 11:50 ` Luigi 'Comio' Mantellini
2008-02-28 8:23 ` Luigi 'Comio' Mantellini
2008-02-28 8:34 ` Shinya Kuribayashi
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=47B4E023.3080305@necel.com \
--to=shinya.kuribayashi@necel.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