From mboxrd@z Thu Jan  1 00:00:00 1970
From: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
Date: Fri, 15 Feb 2008 09:43:15 +0900
Subject: [U-Boot-Users] UNCACHED_SDRAM macro issue
In-Reply-To: <1202979717.29669.87.camel@cartesio>
References: <1202893181.26414.141.camel@cartesio>	 <47B3BBBD.7090707@necel.com>
	<1202979717.29669.87.camel@cartesio>
Message-ID: <47B4E023.3080305@necel.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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