From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Fri, 18 Apr 2014 09:44:44 -0600
Subject: [U-Boot] config: enable CONFIG_API in distro config
In-Reply-To: <20140418153558.GD5698@bill-the-cat>
References: <1397163348-9343-1-git-send-email-robherring2@gmail.com>
	<20140418153558.GD5698@bill-the-cat>
Message-ID: <5351486C.1030601@wwwdotorg.org>
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 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@kernel.org>
>>
>> CONFIG_API is needed for u-boot apps such as grub2, so enable it for
>> distro config.
>>
>> Cc: Dennis Gilmore <dennis@ausil.us>
>> Signed-off-by: Rob Herring <robh@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?

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.