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
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
