From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFC common omap3 subconfig ? was Re: [PATCH] OMAP3EVM: Increase bootargs string length.
Date: Thu, 17 Dec 2009 19:23:58 +0100 [thread overview]
Message-ID: <4B2A773E.2010609@denx.de> (raw)
In-Reply-To: <200912171736.11000.sr@denx.de>
Hello Stefan,
Stefan Roese wrote:
> On Thursday 17 December 2009 17:07:01 Dirk Behme wrote:
>>>> It seems like a lot of the omap3 boards share common config options.
>>>> What do you think about consolidating the common options to
>>>> a sub config file ?
>>> Seems a good idea; only if we are sure that the next board doesn't
>>> break the current list of common configs. Else, we would be having
>>> patches to move config options back to board specific files.
>> Does Wolfgang have a basic opinion about sub-configs for configuration
>> stuff common for similar boards?
>
> We already have some similar common config files. Take a look for example at
> the AMCC config header:
>
> include/configs/amcc-common.h
I vote for collecting "common config files" in a subdir:
include/configs/common
for example:
include/configs/common/mpc83xx.h
collects all common config options for 83xx boards.
and so on for all other architectures/manufacturer ...
And a "#include "configs/common/..." provides enough
information, what will come in with that include ...
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2009-12-17 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 13:29 [U-Boot] [PATCH] OMAP3EVM: Increase bootargs string length Sriramakrishnan
2009-12-17 14:26 ` Dirk Behme
2009-12-17 14:48 ` Govindarajan, Sriramakrishnan
2009-12-17 15:55 ` [U-Boot] RFC common omap3 subconfig ? was " Tom
2009-12-17 15:58 ` Premi, Sanjeev
2009-12-17 16:07 ` Dirk Behme
2009-12-17 16:36 ` Stefan Roese
2009-12-17 18:23 ` Heiko Schocher [this message]
2009-12-18 8:43 ` Stefan Roese
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=4B2A773E.2010609@denx.de \
--to=hs@denx.de \
--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.