Skip to content

Implement fastboot over NAND and sparse transfers

Hans de Goede u-boot 2 versions New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest posting 2/20 of 14 patches 0 repliesNew
  2. v2 posting 1/20 of 14 patches 0 repliesSuperseded

Patches in v2 posting 2/2 No applies recorded yet

None of the 14 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [U-Boot] [PATCH v2 00/14] Implement fastboot over NAND and sparse transfers

Hi,

Quoted 17 lines · Hans de Goede

Hi,

Quoted 14 lines · Maxime Ripard

Hi everyone,

Here is the second attempt at getting fastboot flashing functions working on top of a NAND, for arbitraly large images.

While the NAND support itself was quite easy to do, the support for the Android sparse images was quite difficult to add, and ended up being a quite huge refactoring of the sparse parse already in tree, that was tied to the MMC layer.

This serie has been tested on a CHIP and an A13-Olinuxino, two Allwinner devices, the CHIP for the NAND, and the Cubietruck to test the MMC.

Quoted 5 lines
Quoted 2 lines

Let me know what you think,
Maxime

Thanks, I've applied the 3 sunxi patches (12 - 14) to u-boot-sunxi/next, with the commit msg fixup suggested by Ian.

Looks like I've spoken too soon, the patch for enabling otg on the cubietruck causes build errors:

arm-linux-gnu-ld.bfd: error: /usr/lib/gcc/arm-linux-gnueabi/5.2.1/libgcc.a(_udivmoddi4.o) uses VFP register arguments, u-boot does not arm-linux-gnu-ld.bfd: failed to merge target specific data of file /usr/lib/gcc/arm-linux-gnueabi/5.2.1/libgcc.a(_udivmoddi4.o) Makefile:1173: recipe for target 'u-boot' failed
make: *** [u-boot] Error 1

Usually this means that some code is using 64 bit int division without using the proper macros for this.

For some reason I'm not seeing the same on the A13-OlinuxIno, that patch for that seems to be missing the id pin, which could have something to do with this.

I think this is caused by some 64 bit math in the fastboot code somewhere ...

For now I've dropped these 2 patches from u-boot-sunxi/next

Regards,

Hans

Read the cover letter in its thread