From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] ARM: lib: Remove CONFIG_ARCH_CPU_INIT dependency
Date: Mon, 5 Mar 2012 10:56:31 -0700 [thread overview]
Message-ID: <20120305175631.GD18051@bill-the-cat> (raw)
In-Reply-To: <4F4FEDA9.3080307@aribaud.net>
On Thu, Mar 01, 2012 at 10:44:09PM +0100, Albert ARIBAUD wrote:
> How about this approach: since the problem is the presence of CPU-
> (or Soc-)level elements in board-level config files, and since there
> are probably many other such items in board config files (CPU type
> in a SoC and HW IP configurations, for instance) then why not
> introduce some cpu-config and soc-config file which would group all
> those cpu- (resp soc-)level items, including any "#define
> CONFIG_ARCH_CPU_INIT", and replace these items in board config files
> with a single "#include "<cpu>-config.h" (or "<soc>-config.h")? This
> would significantly reduce board config file size.
Note that omap4/5 do something like this already and my hope is to do
this for omap3/similar and make some other common files as well. It's
not the top priority for me atm however...
--
Tom
next prev parent reply other threads:[~2012-03-05 17:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 14:02 [U-Boot] [PATCH 1/3] ARM: lib: Remove CONFIG_ARCH_CPU_INIT dependency Fabio Estevam
2012-03-01 14:02 ` [U-Boot] [PATCH 2/3] ARM: mx6: Remove CONFIG_ARCH_CPU_INIT Fabio Estevam
2012-03-01 18:31 ` Marek Vasut
2012-07-07 11:25 ` Albert ARIBAUD
2012-03-01 14:02 ` [U-Boot] [PATCH 3/3] ARM: mx28: " Fabio Estevam
2012-03-01 18:31 ` Marek Vasut
2012-07-07 11:31 ` Albert ARIBAUD
2012-07-19 17:28 ` Marek Vasut
2012-03-01 18:31 ` [U-Boot] [PATCH 1/3] ARM: lib: Remove CONFIG_ARCH_CPU_INIT dependency Marek Vasut
2012-03-01 20:51 ` Albert ARIBAUD
2012-03-01 20:57 ` Fabio Estevam
2012-03-01 21:44 ` Albert ARIBAUD
2012-03-05 17:56 ` Tom Rini [this message]
2012-03-06 7:26 ` Albert ARIBAUD
2012-03-03 10:01 ` Stefano Babic
2012-03-05 17:52 ` Tom Rini
2012-03-05 17:58 ` Fabio Estevam
2012-03-05 18:12 ` Fabio Estevam
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=20120305175631.GD18051@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