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 v3 4/4] ARM: tegra: Add support for nyan board
Date: Mon, 24 Nov 2014 10:25:11 -0700	[thread overview]
Message-ID: <547369F7.30403@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ290n57H1QWmCVqeb4g_A3FZBmbVcHQ5i0A=oVa582csQ@mail.gmail.com>

On 11/23/2014 10:02 AM, Simon Glass wrote:
> Hi,
>
> On 23 November 2014 at 09:12, Simon Glass <sjg@chromium.org> wrote:
>>
>> From: Allen Martin <amartin@nvidia.com>
>>
>> Nyan is a Tegra124 clamshell board that is very similar to venice2, but it
>> has a different panel, the sdcard cd and wp sense are flipped, and it has
>> a different revision of the AS3722 PMIC.
>>
>> This is the Acer Chromebook 13 CB5-311-T7NN (13.3-inch HD, NVIDIA
>> Tegra K1, 2GB). The display is not currently supported, so it should
>> boot on other nyan-based Chromebooks also, but only the device tree for
>> nyan-big is provided here.
>>
>> The device tree file is from Linux but with features removed which are
>> unlikely to be supported in U-Boot soon (regulators, pinmux). Also the
>> addresses are updated to 32-bit.
>>
>> Signed-off-by: Allen Martin <amartin@nvidia.com>
>> Signed-off-by: Simon Glass <sjg@chromium.org>
>> (rebase, change to 'nyan', fix pinmux that resets nyan)
>>
>> ---
>>
>> Changes in v3:
>> - Rename to nyan from norrin
>> - Bring in device tree file from Linux v3.18-rc5
>> - Generate pinmux file from tegra-pinmux-scripts
>
> I should say that I'm not thrilled with this approach, particularly as
> the files it generate have no mentioned that they are auto-generated.

Oh I forgot to mention - feel free to send a patch for that. I mainly 
didn't add such a message earlier, since I when I wrote the U-Boot 
header generator in tegra-pinmux-scripts, I wanted to generate exactly 
the same data as was already there in U-Boot in the manually written 
files. If you think updating those files to add a "this is 
auto-generated" message would be useful, feel free to send a patch to 
tegra-pinmux-scripts and we can add it.

  parent reply	other threads:[~2014-11-24 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 16:12 [U-Boot] [PATCH v3 1/4] dts: Bring in Chrome OS keyboard device tree definition Simon Glass
2014-11-23 16:12 ` [U-Boot] [PATCH v3 2/4] tegra: dts: Sync tegra124.dtsi with linux kernel Simon Glass
2014-11-24 17:09   ` Stephen Warren
2014-11-24 17:12     ` Simon Glass
2014-11-23 16:12 ` [U-Boot] [PATCH v3 3/4] tegra: config: Enable FIT and device tree for all boards Simon Glass
2014-11-24 17:11   ` Stephen Warren
2014-11-24 23:49     ` Simon Glass
2014-11-25 16:23       ` Stephen Warren
2014-11-25 17:44         ` Simon Glass
2014-12-01 18:41           ` Stephen Warren
2014-12-01 20:17             ` Simon Glass
2014-11-23 16:12 ` [U-Boot] [PATCH v3 4/4] ARM: tegra: Add support for nyan board Simon Glass
2014-11-23 17:02   ` Simon Glass
2014-11-24 17:21     ` Stephen Warren
2014-11-24 17:25     ` Stephen Warren [this message]
2014-11-24 17:28   ` Stephen Warren
2014-11-24 23:48     ` Simon Glass
2014-11-25 16:14       ` Stephen Warren
2014-11-25 16:18         ` 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=547369F7.30403@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