28 Jun, 2016

2 commits

• 9bc34799c   fastboot: sparse: resync common/image-sparse.c (part 2) ... Browse Code »

  - update fastboot_okay() and fastboot_fail()

  This file originally came from upstream code.

  While retaining the storage abstraction feature, this is the second
  set of the changes required to resync with the
  cmd_flash_mmc_sparse_img()
  in the file
  aboot.c
  from
  https://us.codeaurora.org/cgit/quic/la/kernel/lk/plain/app/aboot/aboot.c?h=LE.BR.1.2.1

  Signed-off-by: Steve Rae

  Steve Rae

  2016-06-28 04:37:38 +0800  
• 64ece8485   fastboot: sparse: remove session-id logic ... Browse Code »

  This "session-id" alogrithm is not required, and currently corrupts
  the stored image whenever more the one "session" is required.

  Signed-off-by: Steve Rae

  Steve Rae

  2016-06-28 04:36:33 +0800  

13 Nov, 2015

1 commit

• 6c9e00eeb   fastboot: Implement flashing session counter ... Browse Code »

  The fastboot flash command that writes an image to a partition works in
  several steps:

  1 - Retrieve the maximum size the device can download through the
  "max-download-size" variable

  2 - Retrieve the partition type through the "partition-type:%s" variable,
  that indicates whether or not the partition needs to be erased (even
  though the fastboot client has minimal support for that)

  3a - If the image is smaller than what the device can handle, send the image
  and flash it.

  3b - If the image is larger than what the device can handle, create a
  sparse image, and split it in several chunks that would fit. Send the
  chunk, flash it, repeat until we have no more data to send.

  However, in the 3b case, the subsequent transfers have no particular
  identifiers, the protocol just assumes that you would resume the writes
  where you left it.

  While doing so works well, it also means that flashing two subsequent
  images on the same partition (for example because the user made a mistake)
  would not work withouth flashing another partition or rebooting the board,
  which is not really intuitive.

  Since we have always the same pattern, we can however maintain a counter
  that will be reset every time the client will retrieve max-download-size,
  and incremented after each buffer will be flashed, that will allow us to
  tell whether we should simply resume the flashing where we were, or start
  back at the beginning of the partition.

  Signed-off-by: Maxime Ripard
  Reviewed-by: Tom Rini

  Maxime Ripard

  2015-11-13 02:17:32 +0800  

26 Feb, 2015

1 commit

• 897923819   usb: gadget: fastboot: Add fastboot erase ... Browse Code »

  Adds the fastboot erase functionality, to erase a partition
  specified by name. The erase is performed based on erase group size,
  to avoid erasing other partitions. The start address and the size
  is aligned to the erase group size for this.

  Currently only supports erasing from eMMC.

  Signed-off-by: Dileep Katta
  Reviewed-by: Lukasz Majewski

  Dileep Katta

  2015-02-26 00:47:02 +0800  

25 Sep, 2014

1 commit

• c0aebb338   usb/gadget: fastboot: add eMMC support for flash command ... Browse Code »

  - add support for 'fastboot flash' command for eMMC devices

  Signed-off-by: Steve Rae

  Steve Rae

  2014-09-25 06:30:27 +0800