public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Unifying device tree filenames, and U-Boot SoC name
Date: Mon, 21 May 2012 18:01:43 -0700	[thread overview]
Message-ID: <20120522010143.GF30009@nvidia.com> (raw)
In-Reply-To: <CAPnjgZ3rcprV5Es3Omcnwr8EdvP+1E94U__Ou_9wzw1048beNQ@mail.gmail.com>

On Mon, May 21, 2012 at 05:49:03PM -0700, Simon Glass wrote:
> Hi Stephen,
> 
> On Mon, May 21, 2012 at 7:22 AM, Thierry Reding <thierry.reding at avionic-design.de<mailto:thierry.reding@avionic-design.de>> wrote:
> * Stephen Warren wrote:
> >
> > b) In U-Boot, rename the tegra2 support to tegra20 so that U-Boot ends
> > up setting board_soc=tegra20, so this matches the .dts/.dtb filenames.
> > This would involve renaming arch/arm/cpu/armv7/tegra2/ to
> > ./arch/arm/cpu/armv7/tegra20/ and editing boards.cfg to match, and
> > possibly other related changes.
> >
> > This sounds like churn, but I think we could easily fold this into
> > Allen's series that moves the tegra2 directory in order to put it in a
> > common place for separate SPL/non-SPL builds to avoid doing this kind of
> > thing multiple times.
> >
> > Does anyone think this is a good/bad/... idea? Thanks.
> 
> I like it. It's better to have the names consistent.
> 
> Sounds good to me, too.

I'm fine with the proposal, I'll roll it into my SPL patch series
which I need to post a new version of anyway.

-Allen
-- 
nvpublic

      reply	other threads:[~2012-05-22  1:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 17:44 [U-Boot] Unifying device tree filenames, and U-Boot SoC name Stephen Warren
2012-05-21 14:22 ` Thierry Reding
2012-05-22  0:49   ` Simon Glass
2012-05-22  1:01     ` Allen Martin [this message]

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=20120522010143.GF30009@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox