Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Allen Martin <amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] [cbootimage-configs] Add support for norrin board
Date: Wed, 02 Jul 2014 12:43:15 -0600	[thread overview]
Message-ID: <53B452C3.7050009@wwwdotorg.org> (raw)
In-Reply-To: <20140702175807.GA30613-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

On 07/02/2014 11:58 AM, Allen Martin wrote:
> On Mon, Jun 30, 2014 at 02:25:37PM -0700, Stephen Warren wrote:
>> On 06/30/2014 02:42 PM, Allen Martin wrote:
>>> Norrin (PM370) is an NVIDIA Tegra124 Chromebook reference platform.
>>> It is also called "nyan" in the ChromeOS tree.
>>
>> I thought only some versions/revisions of Nyan were actually Norrin?
>> Isn't nyan-rev0 Venice2, but nyan-rev1 Norrin?
> 
> Yes, although nyan-rev0 is pretty much orphaned at this point in the
> ChromeOS trees, so any place you see "nyan" without the -rev specifier
> you can assume Tegra124 Norrin FFD.

OK, I'll add a note to the commit description when I apply, that "nyan
rev0" is actually Venice2.

>> When we have Norrins with Tegra132 (which I thought was actually the
>> more common version, but perhaps not), what is the plan for naming them;
>> perhaps norrin-t132?
> 
> In the ChromeOS tree Tegra132 Norrin is called "rush", internally
> we've been calling them norrin-t132 (or t132-norrin, , or norrin64, or
> just "norrin" to make it confusing and you figure it out by context :)

OK, let's go with "norrin-t132" for that upstream when it happens, since
I assume we created the board and I have no idea why it got renamed.

  parent reply	other threads:[~2014-07-02 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 20:42 [PATCH] [cbootimage-configs] Add support for norrin board Allen Martin
     [not found] ` <1404160939-10555-1-git-send-email-amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-06-30 21:25   ` Stephen Warren
     [not found]     ` <53B1D5D1.9060606-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-07-02 17:58       ` Allen Martin
     [not found]         ` <20140702175807.GA30613-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-07-02 18:43           ` Stephen Warren [this message]
2014-07-02 18:49   ` 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=53B452C3.7050009@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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