From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Ripard Date: Sun, 6 Sep 2015 17:57:25 +0200 Subject: [U-Boot] [PATCH 07/13] fastboot: Implement NAND backend In-Reply-To: <20150904172049.GM26226@bill-the-cat> References: <1441032373-16992-1-git-send-email-maxime.ripard@free-electrons.com> <1441032373-16992-8-git-send-email-maxime.ripard@free-electrons.com> <20150904172049.GM26226@bill-the-cat> Message-ID: <20150906155725.GP31584@lukather> 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, Sep 04, 2015 at 01:20:49PM -0400, Tom Rini wrote: > On Mon, Aug 31, 2015 at 04:46:07PM +0200, Maxime Ripard wrote: > > > So far the fastboot code was only supporting MMC-backed devices for its > > flashing operations (flash and erase). > > > > Add a storage backend for NAND-backed devices. > > > > Signed-off-by: Maxime Ripard > > In general: > > Reviewed-by: Tom Rini > > But would it be possible to do this similar to how DFU is where we can > have NAND and MMC and whatever else built-in and then use the right one > as instructed by the user? ie change the command from 'fastboot > ' to 'fastboot [interface]' (or maybe > have to make interface required, not sure). Thanks! As in something like "fastboot 0 mmc 0" ? Sounds good, however, since fastboot only refers to partitions by name, we could simply allow mix and matching them. What do you think? Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: