lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 6 Jun 2010 16:17:00 +0800
From:	Eric Miao <eric.y.miao@...il.com>
To:	Marek Vasut <marek.vasut@...il.com>
Cc:	linux-arm-kernel@...ts.infradead.org,
	balakrishnan <balakrishnan@...onsystems.com>,
	linux-kernel@...r.kernel.org,
	Maharajan <maharajan@...onsystems.com>
Subject: Re: pxa300 - DDRAM base value

On Sun, Jun 6, 2010 at 1:19 AM, Marek Vasut <marek.vasut@...il.com> wrote:
> Dne Út 1. června 2010 07:44:18 balakrishnan napsal(a):
>> I am working on pxa300 based development board and using Linux 2.6.34.
>> This Linux kernel already has support for following boards
>> 1. zylonite_pxa300
>> 2. cm-x300
>> 3. colibri-pxa300
>> 4. littleton
>>
>> My doubt is that pxa300 based boards are using "0xa0000000"  as DDRAM
>> base and PHYS_OFFSET is also defined in
>> "arch/arm/mach-pxa/include/mach/memory.h" as 0xa0000000.
>> But in our board  DDR is mapped in 0x80000000. Does it make any
>> problem?. Because after mmu is turned ON, my board is hanging.
>>
>> "zreladdr-y   := 0x80008000" is defined in
>> "arch/arm/mach-pxa/Makefile.boot" file .
>> my machine_desc is as follows
>> .phys_io        = 0x40000000,
>> .io_pg_offst    = (io_p2v(0x40000000) >> 18) & 0xfffc,
>> .boot_params    = 0x80000100,
>>
>
> Try editing both arch/arm/mach-pxa/Makefile.boot and
> arch/arm/mach/pxa/include/mach/memory.h
>
>> With Thanks
>> J.Balakrishnan
>
> The 0x80000000 should be aliased to 0xa0000000, but looking into the PXA docs,
> it is only on pxa320. Eric, any ideas on this ?
>

Should be working on pxa300/310 as well. If it doesn't, check you bootloader
to make sure the mapping is OK, and memory doesn't exceed
(0xa000_0000 - 0x8000_0000).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ