From: Stephen Warren <swarren@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 3/3] tegra2: Add support for Paz00 (Toshiba AC100)
Date: Mon, 21 Nov 2011 09:46:06 -0700 [thread overview]
Message-ID: <4ECA804E.4050401@nvidia.com> (raw)
In-Reply-To: <1370119.BTXLFhsFep@ax5200p>
On 11/20/2011 10:39 AM, Marc Dietrich wrote:
> On Sunday 20 November 2011 13:10:08 Thierry Reding wrote:
>> * Stephen Warren wrote:
>>> The Toshiba AC100 (code-name Paz00m a/k/a Dynabook AZ) is an netbook
>>> derived from the NVIDIA Tegra Harmony reference board. It ships with
>>> Ubuntu, but is often repurposed to run Linux. This patch adds just
>>> enough support to get a U-Boot serial console, and the ability access
>>> built-in eMMC and the external SD slot.
...
>>> +#define TEGRA2_SYSMEM "mem=384M at 0M nvmem=128M at 384M"
>>
>> Can we get rid of this? I think I remember some discussion about the same
>> topic going on the linux-tegra/devicetree mailing lists, where it was
>> decided that /mem-reserve/ entries should be dropped until some driver in
>> the mainline kernel was actually going to use this memory. Perhaps U-Boot
>> should take the same approach.
>
> I also vote for this. Additionally, most users prefer mem=448M here. The
> device was original ships with 448 MB user memory, which was later reduced to
> 384 MB, maybe because of flash player requirements. I'm also not sure if nvmem
> is needed at all (maybe for android original kernel only)
Sounds like a plan. I've done this, and also moved the files to
board/compal/paz00 as suggested elsewhere.
>>> +#define V_PROMPT "Tegra2 (Paz00) # "
>>> +#define CONFIG_TEGRA2_BOARD_STRING "NVIDIA Paz00"
>>> +
>>> +/* Board-specific serial config */
>>> +#define CONFIG_SERIAL_MULTI
>>> +#define CONFIG_TEGRA2_ENABLE_UARTA
>>> +#define CONFIG_SYS_NS16550_COM1 NV_PA_APB_UARTA_BASE
>>> +
>>> +#define CONFIG_MACH_TYPE MACH_TYPE_PAZ00
>>> +/*
>>> + * The following should be 512MB, but I don't know how to set that
>>> value
>>> + * It doesn't matter, since this isn't really used any more
>>> + */
>>> +#define CONFIG_SYS_BOARD_ODMDATA 0x200d8011 /* lp1, 1GB */
>
> I don't know what is the effect of this paramter, but paz00 has 512 MB. The
> original valu was 0x8000c0085, AFAIK, which leaves most stuff on the default
> value.
OK, I've switched to that value (where did you extract it from, BTW),
and after fixing a bug in
arch/arm/cpu/armv7/tegra2/board.c:query_sdram_size() (default==512M, not
1G), it all works.
--
nvpublic
next prev parent reply other threads:[~2011-11-21 16:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 20:47 [U-Boot] [RFC PATCH 0/3] tegra2: Add paz00 support Stephen Warren
2011-11-19 20:47 ` [U-Boot] [RFC PATCH 1/3] MAINTAINERS: Fix my email address Stephen Warren
2011-11-28 18:58 ` Wolfgang Denk
2011-11-28 19:01 ` Wolfgang Denk
2011-11-28 19:34 ` Stephen Warren
2011-11-28 19:41 ` Wolfgang Denk
2011-11-28 19:45 ` Stephen Warren
2011-11-28 20:39 ` Wolfgang Denk
2011-11-19 20:47 ` [U-Boot] [RFC PATCH 2/3] tegra2: Fix conflicting pinmux for UARTA Stephen Warren
2011-11-19 20:47 ` [U-Boot] [RFC PATCH 3/3] tegra2: Add support for Paz00 (Toshiba AC100) Stephen Warren
2011-11-20 12:10 ` Thierry Reding
2011-11-20 17:39 ` Marc Dietrich
2011-11-21 16:46 ` Stephen Warren [this message]
2011-11-20 12:05 ` [U-Boot] [RFC PATCH 0/3] tegra2: Add paz00 support Thierry Reding
2011-11-20 17:45 ` Marc Dietrich
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=4ECA804E.4050401@nvidia.com \
--to=swarren@nvidia.com \
--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