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
     

02 Feb, 2018

1 commit


11 Oct, 2016

1 commit


27 Sep, 2016

1 commit

  • Introduce a hidden USB_FUNCTION_DFU Kconfig option and select it for
    CMD_DFU (as we must have the DFU command enabled to do anything DFU).
    Make all of the entries in drivers/dfu/Kconfig depend on CMD_DFU and add
    options for all of the back end choices that DFU can make use of.

    Cc: Lukasz Majewski
    Signed-off-by: Tom Rini
    Acked-by: Lukasz Majewski

    Tom Rini
     

26 Apr, 2016

1 commit


20 Apr, 2016

4 commits


26 Mar, 2016

1 commit

  • The description was borrowed from kernel. "tristate" type was changed
    to "bool" (I believe we don't support modules for u-boot yet, right?).
    CONFIG_USB_GADGET requires CONFIG_USB to be defined too, so add it along
    as well.

    Definitions were added to defconfig files in a way that
    "make savedefconfig" generates exactly the same file as used defconfig.

    Signed-off-by: Sam Protsenko
    [trini: Add zynq_zc702 conversion]
    Signed-off-by: Tom Rini

    Sam Protsenko
     

12 Sep, 2015

2 commits

  • This allows transferring data directly to/from RAM. For example, one
    could create a boot script that starts DFU on a RAM region, then once
    DFU exits (which is under the control of the attached USB host, via a
    USB bus reset), uses the code/data that was received over DFU.

    Signed-off-by: Stephen Warren

    Stephen Warren
     
  • CONFIG_SYS_DFU_DATA_BUF_SIZE defines the size of chunks transferred
    across USB. This doesn't need to be particularly large, since it doesn't
    limit the overall transfer size.

    CONFIG_SYS_DFU_MAX_FILE_SIZE is used to buffer an entire file before
    writing it to a filesystem. This define limits the maximum file size that
    may be transferred. Bump this up to 32MiB in order to support large
    uncompressed kernel images.

    Both of these buffers are dynamically allocated, and so the size of both
    needs to be taken into account when calculating the required malloc
    region size.

    Signed-off-by: Stephen Warren

    Stephen Warren
     

14 Aug, 2015

1 commit


22 Jul, 2015

1 commit

  • This introduces a coherent scheme for naming USB download gadget and functions
    config options. The download USB gadget config option is moved to
    CONFIG_USB_GADGET_DOWNLOAD for better consistency with other gadgets and each
    function's config option is moved to a CONFIG_USB_FUNCTION_ prefix.

    Signed-off-by: Paul Kocialkowski
    Tested-by: Lukasz Majewski

    Test HW: Odroid_XU3 (Exynos5422), trats (Exynos4210)

    Paul Kocialkowski
     

19 Aug, 2014

1 commit

  • Enable DFU protocol support (via the "dfu" command) on Tegra boards where
    USB device/gadget mode is enabled.

    Note that for DFU to operate correctly on Tegra, we still need some DFU
    fixes/enhancements that are going through the DFU -> USB trees. However,
    the code builds just fine without those changes, and applying this patch
    now will allow both sets of patches to meet in the main U-Boot tree much
    more quickly.

    In order to run test/dfu/dfu_gadget_test.sh, you would need to add the
    following to the board configuration:

    CONFIG_EXT4_WRITE
    CONFIG_CMD_EXT4_WRITE

    However, I haven't enabled those here, since I believe the main use-case
    for DFU on Tegra is raw flash writing, rather than filesystem access, so
    we don't need the additional code-size hit. However, I could be persuaded
    otherwise! We should probably add a separate test script for raw flash
    access.

    Signed-off-by: Stephen Warren
    Acked-by: Simon Glass
    Signed-off-by: Tom Warren

    Stephen Warren