05 May, 2020

1 commit

  • CONFIG_MTD_NOR_FLASH flag needs to be enable for all
    boot sources,as all flash drivers need to compile in
    TFA Boot.Probe ifc nor flash only when there is nor
    flash available on board.So needs to detect ifc-nor
    flash at run-time for probing.

    Signed-off-by: Pankit Garg

    Pankit Garg
     

10 Apr, 2020

1 commit

  • Rather than keeping the asynchronous schedule running always, keep it
    running only across USB mass storage transfers for now, as it seems
    that keeping it running all the time interferes with certain control
    transfers during device enumeration.

    Note that running the async schedule all the time should not be an
    issue, especially on EHCI HCD, as that one implements most of the
    transfers using async schedule.

    Note that we have usb_disable_asynch(), which however is utterly broken.
    The usb_disable_asynch() blocks the USB core from doing async transfers
    by setting a global flag. The async schedule should however be disabled
    per USB controller. Moreover, setting a global flag does not prevent the
    controller from using the async schedule, which e.g. the EHCI HCD does.

    This patch implements additional callback to the controller, which
    permits it to lock the async schedule and keep it running across
    multiple transfers. Once the schedule is unlocked, it must also be
    disabled. This thus prevents the async schedule from running outside
    of the USB mass storage transfers.

    Signed-off-by: Marek Vasut
    Cc: Lukasz Majewski
    Cc: Tom Rini
    Tested-by: Tom Rini [omap3_beagle, previously failing]

    Marek Vasut
     

03 Apr, 2020

1 commit


02 Apr, 2020

1 commit

  • Enable pre console buffer for rk3399 platform.

    This would help to capture the console messages prior to
    the console being initialised. Enabling this would help
    to capture all the console messages on video output source
    like HDMI. So we can find the full console messages of
    U-Boot proper on HDMI display when enabled it for RK3399
    platform boards.

    Buffer address used for pre console is 0x0f200000 which is
    ram base plus 240MiB. right now the Allwinner SoC is using
    similar computation.

    Signed-off-by: Jagan Teki
    Reviewed-by: Kever Yang
    Tested-by: Peter Robinson

    Jagan Teki
     

01 Apr, 2020

6 commits


31 Mar, 2020

1 commit


13 Mar, 2020

1 commit

  • GCC-10 reports:

    In file included from tools/common/image-fit.c:1:
    include/image.h: In function ‘fit_image_get_data_and_size’:
    ./tools/../common/image-fit.c:1015:9: warning: ‘len’ may be used
    uninitialized in this function [-Wmaybe-uninitialized]
    1015 | *size = len;
    | ~~~~~~^~~~~
    ./tools/../common/image-fit.c:996:6: note: ‘len’ was declared here
    996 | int len;
    | ^~~

    Add the missing check of the return value of fit_image_get_data_size().

    Fixes: c3c863880479 ("add FIT data-position & data-offset property support")
    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Goldschmidt

    Heinrich Schuchardt
     

09 Mar, 2020

1 commit


19 Feb, 2020

1 commit

  • Enable pre console buffer for rk3288 platform.

    This would help to capture the console messages prior to
    the console being initialised. Enabling this would help
    to capture all the console messages on video output source
    like HDMI. So we can find the full console messages of
    U-Boot proper on HDMI display when enabled it for RK3288
    platform boards.

    Buffer address used for pre console is 0x0f000000 which is
    ram base plus 240MiB. right now the Allwinner SoC is using
    similar computation.

    Signed-off-by: Jagan Teki
    Reviewed-by: Kever Yang

    Jagan Teki
     

13 Feb, 2020

2 commits

  • clear_bss is already used by 3 arches (x86, arc, xtensa), so make it generic
    and provide a weak nop stub for it. This also removes arch-specific ifdef
    duplications around clear_bss.

    Signed-off-by: Ovidiu Panait

    Ovidiu Panait
     
  • Avoid errors of like

    common/console.c: In function ‘console_record_reset’:
    common/console.c:615:16: error: passing argument 1 of ‘membuff_purge’
    discards ‘volatile’ qualifier from pointer target type
    [-Werror=discarded-qualifiers]
    615 | membuff_purge(&gd->console_out);
    | ^~~~~~~~~~~~~~~~

    by casting to non-volatile.

    The volatile property stems from declarations like

    arch/arm/include/asm/global_data.h:114:

    But there is no need to treat gd->console_out and gd->console_in as
    volatile in the context of common/console.c.

    Fixes: b612312816ff ("console: Add a function to read a line of the output / eof")
    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Glass

    Heinrich Schuchardt
     

11 Feb, 2020

2 commits


06 Feb, 2020

8 commits


04 Feb, 2020

2 commits

  • Android Boot Image v1 adds "Recovery DTB" field in image header and
    associate payload in boot image itself [1]. Payload should be in
    Android DTB/DTBO format [2]. That "Recovery DTB" area should be only
    populated for non-A/B devices, and only in recovery image.

    Add function to get an address and size of that payload. That function
    can be further used e.g. in 'abootimg' command to provide the user a way
    to get the address of recovery dtbo from U-Boot shell, which can be
    further parsed using 'adtimg' command.

    [1] https://source.android.com/devices/bootloader/boot-image-header
    [2] https://source.android.com/devices/architecture/dto/partitions

    Signed-off-by: Sam Protsenko
    Signed-off-by: Lokesh Vutla

    Sam Protsenko
     
  • Android Boot Image v2 adds "DTB" payload (and corresponding field in the
    image header). Provide functions for its handling:

    - android_image_get_dtb_by_index(): Obtain DTB blob from "DTB" part of
    boot image, by blob's index
    - android_image_print_dtb_contents(): Iterate over all DTB blobs in
    "DTB" part of boot image and print those blobs info

    "DTB" payload might be in one of the following formats:
    1. concatenated DTB blobs
    2. Android DTBO format

    The latter requires "android-image-dt.c" functionality, so this commit
    selects that file for building for CONFIG_ANDROID_BOOT_IMAGE option.

    Right now this new functionality isn't used, but it can be used further.
    As it's required to apply some specific dtbo blob(s) from "dtbo"
    partition, we can't automate this process inside of "bootm" command. But
    we can do next:
    - come up with some new command like "abootimg" to extract dtb blob
    from boot image (using functions from this patch)
    - extract desired dtbo blobs from "dtbo" partition using "adtimg"
    command
    - merge dtbo blobs into dtb blob using "fdt apply" command
    - pass resulting dtb blob into bootm command in order to boot the
    Android kernel with Android ramdisk from boot image

    Signed-off-by: Sam Protsenko
    Signed-off-by: Lokesh Vutla

    Sam Protsenko
     

31 Jan, 2020

1 commit


27 Jan, 2020

2 commits


26 Jan, 2020

1 commit

  • On m68k, block_cache list is relocated, but next and prev list
    pointers are not adjusted to the relocated struct list_head address,
    so the first iteration over the block_cache list hangs.

    This patch initializes the block_cache list after relocation.

    Signed-off-by: Angelo Durgehello
    Reviewed-by: Eric Nelson

    Angelo Durgehello
     

25 Jan, 2020

8 commits