14 Jun, 2019

1 commit


30 May, 2018

3 commits


07 May, 2018

1 commit

  • When U-Boot started using SPDX tags we were among the early adopters and
    there weren't a lot of other examples to borrow from. So we picked the
    area of the file that usually had a full license text and replaced it
    with an appropriate SPDX-License-Identifier: entry. Since then, the
    Linux Kernel has adopted SPDX tags and they place it as the very first
    line in a file (except where shebangs are used, then it's second line)
    and with slightly different comment styles than us.

    In part due to community overlap, in part due to better tag visibility
    and in part for other minor reasons, switch over to that style.

    This commit changes all instances where we have a single declared
    license in the tag as both the before and after are identical in tag
    contents. There's also a few places where I found we did not have a tag
    and have introduced one.

    Signed-off-by: Tom Rini

    Tom Rini
     

28 Jun, 2016

2 commits


13 Nov, 2015

1 commit

  • 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
     

26 Feb, 2015

1 commit

  • 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
     

25 Sep, 2014

1 commit