public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/7] Tegra114: Dalmore: Add DT files
Date: Thu, 17 Jan 2013 16:11:35 -0700	[thread overview]
Message-ID: <50F88527.2020803@wwwdotorg.org> (raw)
In-Reply-To: <CA+m5__LSMPM2Hhdc3rS82zO33KFhQPxSEsmB2NjCpG6UmjHeZA@mail.gmail.com>

On 01/17/2013 03:58 PM, Tom Warren wrote:
> Stephen,
> 
> On Thu, Jan 17, 2013 at 3:25 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 01/17/2013 10:58 AM, Tom Warren wrote:
>>> Stephen,
>>>
>>> On Wed, Jan 16, 2013 at 3:47 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>>> On 01/16/2013 02:14 PM, Tom Warren wrote:
>>>>> These are stripped down for bringup, They'll be filled out later
>>>>> to match-up with the kernel DT contents, and/or as devices are
>>>>> brought up (mmc, usb, spi, etc.).
>>>>
>>>>> diff --git a/board/nvidia/dts/tegra114-dalmore.dts b/board/nvidia/dts/tegra114-dalmore.dts
>>>>
>>>>> +     memory {
>>>>> +             device_type = "memory";
>>>>> +             reg = <0x80000000 0x40000000>;
>>>>> +     };
>>>>
>>>> Indeed, that says just 1GB...
>>>>
>>>
>>> True, but that's what's in current Cardhu DTS, and Harmony, Seaboard,
>>> and Ventana DTS files. Only Whistler has 0x20000000 (512MB).
>>>
>>> How is this used, and how do we keep it in sync with what's really on
>>> the board/in the ODMDATA field?
>>
>> I don't believe U-Boot uses that property from the DT. Probably the DT
>> isn't parsed early enough for it to be useful. But if we add it to the
>> .dts file, it may as well be correct even so. Or, perhaps we should just
>> remove it from the U-Boot DT since it isn't useful.
> 
> Another candidate for a clean-up pass patchset over all Tegra code.
> For now, I'll bump it to 2GB for Dalmore (and Cardhu), since that's
> what's on the sample boards.

1GB would be safer for Cardhu; there are certainly very commonly used
Cardhu SKUs with only 1GB of RAM. I have one. In fact, I once heard that
most Linux-oriented Cardhu were 1GB and the 2GB devices were mostly used
for Windows development.

  reply	other threads:[~2013-01-17 23:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 21:14 [U-Boot] [PATCH 0/7] Add support for NVIDIA Tegra114 SoC Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 1/7] Tegra114: Add arch-tegra114 include files Tom Warren
2013-01-16 22:32   ` Stephen Warren
2013-01-17 17:51     ` Tom Warren
2013-01-17 22:23       ` Stephen Warren
2013-01-17 22:56         ` Tom Warren
2013-01-16 22:39   ` Allen Martin
2013-01-17 17:50     ` Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 2/7] Tegra114: Add AVP (arm720t) files Tom Warren
2013-01-16 22:42   ` Stephen Warren
2013-01-17 19:15     ` Tom Warren
2013-01-17 22:42       ` Stephen Warren
2013-01-16 23:01   ` Allen Martin
2013-01-17 19:28     ` Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 3/7] Tegra114: Add CPU (armv7) files Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 4/7] Tegra114: Add common CPU (shared) files Tom Warren
2013-01-16 22:46   ` Stephen Warren
2013-01-17 17:55     ` Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 5/7] Tegra114: Dalmore: Add DT files Tom Warren
2013-01-16 22:47   ` Stephen Warren
2013-01-17 17:58     ` Tom Warren
2013-01-17 22:25       ` Stephen Warren
2013-01-17 22:58         ` Tom Warren
2013-01-17 23:11           ` Stephen Warren [this message]
2013-01-17 23:29             ` Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 6/7] Tegra114: Add generic Tegra114 build support Tom Warren
2013-01-16 21:14 ` [U-Boot] [PATCH 7/7] Tegra114: Add/enable Dalmore build (T114 reference board) Tom Warren
2013-01-16 22:51   ` Stephen Warren
2013-01-17 18:01     ` Tom Warren
2013-01-21 23:07     ` Simon Glass
2013-01-22 20:47       ` Tom Warren
2013-01-22 20:56         ` Simon Glass

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=50F88527.2020803@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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