All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] ARM: tegra: Add support for norrin board
Date: Wed, 12 Nov 2014 11:59:04 -0700	[thread overview]
Message-ID: <5463ADF8.1000100@wwwdotorg.org> (raw)
In-Reply-To: <1415732664-18138-1-git-send-email-sjg@chromium.org>

On 11/11/2014 12:04 PM, Simon Glass wrote:
> From: Allen Martin <amartin@nvidia.com>
>
> Norrin (PM370) 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
> board is also refered to as "nyan" in the ChromeOS trees.
>
> This is the Acer Chromebook 13 CB5-311-T7NN (13.3-inch HD, NVIDIA
> Tegra K1, 2GB).

Isn't Norrin a development board for that? I believe there are 
differences between Norrin and the final CB5. If this patch really is 
for CB5 specifically, shouldn't it be named that way? Ideally, the 
U-Boot board name should exactly match the DTB filename in the DT tree 
(i.e. arch/arm/boot/dts in the Linux kernel at present) so that the 
U-Boot environment doesn't have to override the automatic $dtbfile 
calculation.

  parent reply	other threads:[~2014-11-12 18:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 19:04 [U-Boot] [PATCH v2] ARM: tegra: Add support for norrin board Simon Glass
2014-11-12 18:57 ` Stephen Warren
2014-11-12 19:35   ` Simon Glass
2014-11-12 18:59 ` Stephen Warren [this message]
2014-11-12 19:33   ` Simon Glass
  -- strict thread matches above, loose matches on Subject: below --
2014-07-31 23:14 Allen Martin
2014-07-31 23:21 ` Stephen Warren
2014-08-04 18:38   ` Allen Martin
2014-08-04 18:58     ` Stephen Warren

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=5463ADF8.1000100@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.