[U-Boot] config: enable CONFIG_API in distro config

Rob Herring robherring2 at gmail.com
Fri Apr 18 17:58:52 CEST 2014


On Fri, Apr 18, 2014 at 10:44 AM, Stephen Warren <swarren at wwwdotorg.org> 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 <robh at kernel.org>
>>>
>>> CONFIG_API is needed for u-boot apps such as grub2, so enable it for
>>> distro config.
>>>
>>> Cc: Dennis Gilmore <dennis at ausil.us>
>>> Signed-off-by: Rob Herring <robh at kernel.org>
>>
>> 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?

Missing CONFIG_SYS_MMC_MAX_DEVICE at least for trimslice which is only
ever set on zynq. I'll look into it.

> 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.

As the commit says, distro's want to support grub2 which runs as a
u-boot application.

Rob


More information about the U-Boot mailing list