All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Supporting multiple variants of an SoC
Date: Wed, 3 Jul 2013 08:31:04 -0400	[thread overview]
Message-ID: <20130703123104.GR16630@bill-the-cat> (raw)
In-Reply-To: <20130702214546.70E58380E10@gemini.denx.de>

On Tue, Jul 02, 2013 at 11:45:46PM +0200, Wolfgang Denk wrote:
> Dear Tom Rini,
> 
> In message <20130702162829.GG16630@bill-the-cat> you wrote:
> > 
> > That said, when others have suggested something like this before,
> > Wolfgang has pointed out and NAK'd the idea of adding N different
> > configuration as that adds (potentially) a lot of build time for
> > custodians/etc that tend to build --soc or --arch or other group
> > targets.  So, what do we want to do here?  I guess longer term, if we
> > are able to focus on switching to Kconfig, it would become we provide a
> > generic defconfig for am335x (or imx6 or ...) with a best-fit-for-all
> > set and communities can provide tweaked binaries as needed.  But do we
> > want to think about any stop-gap solutions here?
> 
> You can always add extra defines on the make command line...

OK, I'm not spotting the easy way to do that.  Hint?  Thanks!

-- 
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/20130703/62dadb8c/attachment.pgp>

      reply	other threads:[~2013-07-03 12:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 16:28 [U-Boot] [RFC] Supporting multiple variants of an SoC Tom Rini
2013-07-02 17:58 ` Stephen Warren
2013-07-02 20:40   ` Tom Rini
2013-07-03  8:09     ` Lukasz Majewski
2013-07-03 15:58     ` Stephen Warren
2013-07-02 21:47   ` Wolfgang Denk
2013-07-02 21:45 ` Wolfgang Denk
2013-07-03 12:31   ` Tom Rini [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=20130703123104.GR16630@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 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.