From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 18 Apr 2014 11:55:36 -0400 Subject: [U-Boot] config: enable CONFIG_API in distro config In-Reply-To: <5351486C.1030601@wwwdotorg.org> References: <1397163348-9343-1-git-send-email-robherring2@gmail.com> <20140418153558.GD5698@bill-the-cat> <5351486C.1030601@wwwdotorg.org> Message-ID: <20140418155536.GF5698@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, Apr 18, 2014 at 09:44:44AM -0600, Stephen Warren wrote: > On 04/18/2014 09:35 AM, Tom Rini wrote: > > On Thu, Apr 10, 2014 at 03:55:48PM -0500, Rob Herring wrote: > > > >> From: Rob Herring > >> > >> CONFIG_API is needed for u-boot apps such as grub2, so enable it for > >> distro config. > >> > >> Cc: Dennis Gilmore > >> Signed-off-by: Rob Herring > > > > This breaks a number of boards that have opted in to the distro config. > > The full list is: > > whistler trimslice beaver tec paz00 ventana cardhu harmony dalmore > > plutux medcom-wide rpi_b venice2 colibri_t20_iris tec-ng seaboard > > Hmm. That's all or most Tegra boards. What's the break? > > That said, I wonder why we need CONFIG_API in the distro config; the > purpose of that config is to allow the "pxe" and "sysboot" commands not > to work. If we start supporting all kinds of other random boot > mechanisms, we'll just end up with a fragmented mess, rather than a > unified boot mechanism. It's to add grub2, as Rob says :) But the breakage is over things like CONFIG_SYS_MAX_MMC_DEVICE, and a few other things (that's just the common one, but I still saw some breakage when I set that to 2 for tegra stuff). > _______________________________________________ > U-Boot mailing list > U-Boot at lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: