All of lore.kernel.org
 help / color / mirror / Atom feed
From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] ARM: tegra: Add support for norrin board
Date: Mon, 4 Aug 2014 11:38:14 -0700	[thread overview]
Message-ID: <20140804183813.GB30474@nvidia.com> (raw)
In-Reply-To: <53DACF87.1050304@wwwdotorg.org>

On Thu, Jul 31, 2014 at 04:21:43PM -0700, Stephen Warren wrote:
> On 07/31/2014 05:14 PM, Allen Martin wrote:
> > 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.
> 
> At a *very* quick glance, this looks OK. But, you'll need to do a bit of 
> work to rebase it onto the latest u-boot/master. Kconfig has been 
> introduced now, so you'll need to do at least:
> 
> * Don't touch boards.cfg (it's been removed)
> * Add configs/norrin_defconfig
> * Add board/nvidia/norrin/MAINTAINERS
> 
> I think that's it.

I based the patch on u-boot-tegra/master, is there a tegra branch that
has already been rebased?  Or has the upstream workflow changed, so
we're not collecting patches on u-boot-tegra for next merge window?

-Allen

nvpublic

  reply	other threads:[~2014-08-04 18:38 UTC|newest]

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