From mboxrd@z Thu Jan  1 00:00:00 1970
From: Robert P. J. Day <rpjday@crashcourse.ca>
Date: Fri, 20 Nov 2009 14:08:05 -0500 (EST)
Subject: [U-Boot] confused ... how do some CONFIG settings "implicitly"
 set others?
In-Reply-To: <20091120184042.268493F6C2@gemini.denx.de>
References: <alpine.LFD.2.00.0911200826340.27923@localhost>
	<20091120184042.268493F6C2@gemini.denx.de>
Message-ID: <alpine.LFD.2.00.0911201405320.19935@localhost>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Fri, 20 Nov 2009, Wolfgang Denk wrote:

> Dear "Robert P. J. Day",
>
> In message <alpine.LFD.2.00.0911200826340.27923@localhost> you wrote:
> >
> >   reading http://www.denx.de/wiki/view/DULG/UBootSplashScreen, and i
> > see:
> >
> > "To enable splash screen support, you have to add a "#define
> > CONFIG_SPLASH_SCREEN" to your board configuration file. This will also
> > implicitly enable U-Boot Bitmap Support."
> >
> >   "implicitly"?  how does that work?  from what i can see in
> > define2mk.sed, the transformation is straightforward and there are no
> > dependencies or selects as in the kernel Kconfig structure.  how does
> > setting splash screen implicitly set bitmap support?  what am i
> > missing?
>
> Simple. The relevant parts of the code use
>
> 	#if defined(CONFIG_CMD_BMP) || defined(CONFIG_SPLASH_SCREEN)
>
> so they get selected when CONFIG_CMD_BMP and/or CONFIG_SPLASH_SCREEN
> is defined.

  ok, i get it, but that's not "implicit," that's *explicit*.
totally different meaning.

rday
--


========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================