On Fri, Sep 04, 2015 at 01:02:49PM -0400, Tom Rini wrote: > On Tue, Sep 01, 2015 at 10:44:58AM +0300, Siarhei Siamashka wrote: > > > On Tue, 01 Sep 2015 08:22:04 +0100 > > Ian Campbell <[email protected]> wrote: > > > > > On Mon, 2015-08-31 at 16:46 +0200, Maxime Ripard wrote: > > > > When using fastboot and flashing a larger image such as the main > > > > partition > > > > of a system, the current 32MB limit for the buffer is quite small. > > > > > > (Apart from rooting/rescuing the odd phone I'm completely unfamiliar > > > with fastboot, so sorry if this is all obvious). > > > > > > The main partition of a system these days is measured in GB, I think. > > > So why does going from 32MB to 256MB for the buffer make a useful > > > difference? > > > > > > Is there some enormous per-buffer overhead which needs to be amortised? > > > Or is something else going on? > > > > > > IOW what is the practical impact of this change? > > > > I don't know what are Maxime's plans. But if fastboot is fast and > > can load the kernel and initrd to the device over USB, then it > > becomes a useful alternative to using FEL for loading kernel. > > This is in fact a common use case for development. Other platforms / > SoCs do use fastboot in non-Android development as how to pass in a new > testing kernel / initrd / device tree combo.
AFAIK, there's no support in fastboot for a dt yet. You can only give it a kernel with an appended DT. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
