public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mkconfig: Make CONFIG_SYS_BOARD_NAME default to the configured target name
Date: Mon, 26 Nov 2012 14:05:56 -0700	[thread overview]
Message-ID: <20121126210556.GA8657@bill-the-cat> (raw)
In-Reply-To: <20121126093241.3F9AC201056@gemini.denx.de>

On Mon, Nov 26, 2012 at 10:32:41AM +0100, Wolfgang Denk wrote:
> Dear Henrik Nordstr??m,
> 
> In message <1353918095.10834.9.camel@home.hno.se> you wrote:
> > s??n 2012-11-25 klockan 21:01 +0100 skrev Wolfgang Denk:
> > 
> > > I think you should avoid doing that.  It's ugly, and I see no real
> > > advantages for it.
> > 
> > Avoid using the same board config file for multiple boards even when
> > they differ only in one config parameter or in the SoC model mounted on
> > the board?
> 
> No.  Avoid introducing yet another CONFIG_SYS_*_NAME.

I think part of the solution is that in the environment now we have
board_name for the unique run-time-determined board we are on (which
defaults to CONFIG_SYS_BOARD).  In each of these Allwiner SoCs do we
have the ability to tell at run-time what we are on, or only build-time?

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121126/2dcf4c9a/attachment.pgp>

  reply	other threads:[~2012-11-26 21:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-25 11:22 [U-Boot] [PATCH 1/2] mkconfig: Make CONFIG_SYS_BOARD_NAME default to the configured target name Henrik Nordström
2012-11-25 17:43 ` Wolfgang Denk
2012-11-25 17:55   ` Henrik Nordström
2012-11-25 20:01     ` Wolfgang Denk
2012-11-26  8:21       ` Henrik Nordström
2012-11-26  9:32         ` Wolfgang Denk
2012-11-26 21:05           ` Tom Rini [this message]
2012-11-26 21:41             ` Henrik Nordström
2012-11-26 21:51               ` Tom Rini
2012-11-26 22:01                 ` Henrik Nordström
2012-11-27 14:53                   ` Tom Rini

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=20121126210556.GA8657@bill-the-cat \
    --to=trini@ti.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