linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mike.rapoport@gmail.com (Mike Rapoport)
To: linux-arm-kernel@lists.infradead.org
Subject: pxa300 - DDRAM base value
Date: Sun, 6 Jun 2010 20:03:32 +0300	[thread overview]
Message-ID: <AANLkTikMTZ8bl_B0kvowJmtKyRrPbF7Qds3YMeVCWw7E@mail.gmail.com> (raw)
In-Reply-To: <AANLkTil5TWYILcdp872as8S8LMqQWhPYWLt7cxs2lUm5@mail.gmail.com>

On Sun, Jun 6, 2010 at 11:17 AM, Eric Miao <eric.y.miao@gmail.com> wrote:
> On Sun, Jun 6, 2010 at 1:19 AM, Marek Vasut <marek.vasut@gmail.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).

works on CM-X300 with both pxa300 and pxa310

> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at ?http://www.tux.org/lkml/
>



-- 
	Sincerely Yours,
		Mike.

      parent reply	other threads:[~2010-06-06 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01  5:44 pxa300 - DDRAM base value balakrishnan
2010-06-05 17:19 ` Marek Vasut
2010-06-06  8:17   ` Eric Miao
2010-06-06 16:34     ` Marek Vasut
2010-06-07  6:29       ` balakrishnan
2010-06-07  6:58         ` Marek Vasut
2010-06-07 19:37         ` Mike Rapoport
2010-06-07 19:43           ` Marek Vasut
2010-06-08  6:21             ` Mike Rapoport
2010-06-06 17:03     ` Mike Rapoport [this message]

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=AANLkTikMTZ8bl_B0kvowJmtKyRrPbF7Qds3YMeVCWw7E@mail.gmail.com \
    --to=mike.rapoport@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).