From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jassi Brar <jassisinghbrar@gmail.com>
Date: Mon, 14 May 2018 18:42:41 +0530
Subject: [U-Boot] [U-Boot,3/3] mmc: support writing sparse images
In-Reply-To: <20180508171547.GB12235@bill-the-cat.ec.rr.com>
References: <1522996524-23376-1-git-send-email-jassisinghbrar@gmail.com>
 <20180508171547.GB12235@bill-the-cat.ec.rr.com>
Message-ID: <CABb+yY1DQbkJd28efGfqvgGY6zT1w2xj=VYoViOweNJ3ASHP5A@mail.gmail.com>
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

Hi Tom,

On Tue, May 8, 2018 at 10:45 PM, Tom Rini <trini@konsulko.com> wrote:
> On Fri, Apr 06, 2018 at 12:05:24PM +0530, jassisinghbrar at gmail.com wrote:
>
>> From: Jassi Brar <jaswinder.singh@linaro.org>
>>
>> Provide an alternate path for sparse-images to be
>> written to MMC. For example, via tftp on platforms
>> that don't support fastboot protocol. Or when an
>> image is to written at some offset, rather than the
>> start of a partition.
>>
>> Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
>
> Applied to u-boot/master, thanks!
>
I see you modified the patch to protect the feature with
CONFIG_FASTBOOT_FLASH, which kills the purpose -- this feature is for
platforms that don't support fastboot.

Do you want me to send the patch to revert the protection?

Thanks.