From: Wolfgang Grandegger <wg@grandegger•com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: Linuxppc-dev@ozlabs•org
Subject: Re: [PATCH v3 2/4] [POWERPC] 85xx: add board support for the TQM8548 modules
Date: Fri, 06 Jun 2008 09:36:47 +0200 [thread overview]
Message-ID: <4848E90F.5090101@grandegger.com> (raw)
In-Reply-To: <389E58E0-C885-4E8E-B311-C655F52FE23D@kernel.crashing.org>
Kumar Gala wrote:
>
> On Jun 5, 2008, at 3:39 PM, Wolfgang Grandegger wrote:
>
>> Kumar Gala wrote:
>>>
>>>> ===================================================================
>>>> --- /dev/null
>>>> +++ linux-2.6-galak/arch/powerpc/boot/dts/tqm8548.dts
>>>>
>>>
>>>> + memory {
>>>> + device_type = "memory";
>>>> + reg = <0x00000000 0x20000000>;
>>>> + };
>>>
>>> is memory fixed on this board to 256M?
>>
>> Ah, no, actually I have a module with 512 MB but it can be ordered with
>> less or more memory like the other TQM85xx modules as well. Does U-Boot
>> fixup this value? Is it used by Linux?
>
> if u-boot determines the memory it will update this properly. Linux
> expects this to be set to know how much mem is in the system.
>
> if you can try setting the 2nd value to 0x0 and see if it boots that
> will let me know if its safe for me to change.
It works with
memory {
device_type = "memory";
reg = <0x00000000 0x00000000>; // size filled by U-Boot
};
as well. With my previous definition Linux came up with 512 MB of memory
as well and it was already obvious, that U-Boot fills in the right size
value.
Wolfgang.
prev parent reply other threads:[~2008-06-06 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 17:12 [PATCH v3 2/4] [POWERPC] 85xx: add board support for the TQM8548 modules Wolfgang Grandegger
2008-06-05 18:58 ` Kumar Gala
2008-06-05 20:39 ` Wolfgang Grandegger
2008-06-06 0:53 ` Kumar Gala
2008-06-06 7:36 ` Wolfgang Grandegger [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=4848E90F.5090101@grandegger.com \
--to=wg@grandegger$(echo .)com \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
--cc=galak@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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