From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] what is the *recommended* split between defconfig file and header file?
Date: Wed, 20 Jul 2016 08:20:16 -0400 [thread overview]
Message-ID: <20160720122016.GU7260@bill-the-cat> (raw)
In-Reply-To: <ca341d19-bb32-4506-5703-07df0ad77263@suse.de>
On Wed, Jul 20, 2016 at 12:21:16PM +0200, Andreas F?rber wrote:
> Am 20.07.2016 um 10:56 schrieb Robert P. J. Day:
> > On Tue, 19 Jul 2016, Tom Rini wrote:
> >
> >> On Tue, Jul 19, 2016 at 04:15:47AM -0400, Robert P. J. Day wrote:
> >>
> >>>
> >>> kind of a style question but what is the preferred way to define a
> >>> board in the sense of what belongs in the defconfig file and what
> >>> belongs in the header file?
> >>
> >> The header files will eventually go away. Most of the contents are
> >> things that could be, but haven't yet been, converted. A few things
> >> like default environment are going to be harder to figure out.
> >
> > and what about the advantage of header files that allow the
> > inclusion of other header files to reduce duplication? will config
> > files be extended to allow the same thing? (they don't do that now, do
> > they?)
>
> Use Kconfig files for setting defaults or adding selects.
Yes. I am in favour of making heavy use of "default y if ..."
constructs and when possible some meta-options such as DISTRO_DEFAULTS
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160720/f723a6e1/attachment.sig>
next prev parent reply other threads:[~2016-07-20 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 8:15 [U-Boot] what is the *recommended* split between defconfig file and header file? Robert P. J. Day
2016-07-19 19:24 ` Tom Rini
2016-07-20 8:56 ` Robert P. J. Day
2016-07-20 10:21 ` Andreas Färber
2016-07-20 12:20 ` Tom Rini [this message]
2016-07-21 11:24 ` Robert P. J. Day
2016-07-21 14:44 ` 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=20160720122016.GU7260@bill-the-cat \
--to=trini@konsulko.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