21 Dec, 2018

2 commits


18 Dec, 2018

1 commit


17 Dec, 2018

4 commits

  • Android code base is growing, so since Android "Pie" the size of
    system.img grew up to be about 740 MiB. Let's increase system.img to
    1 GiB to accommodate for those changes and leave some margin for future
    changes. We don't want to make it more than 1 GiB, because we should
    keep userdata partition big enough (for user files, like media etc.),
    and eMMC size on BeagleBoard-X15 is only 3.5 GiB.

    Signed-off-by: Sam Protsenko
    Acked-by: Praneeth Bajjuri

    Sam Protsenko
     
  • Output the device model migration warnings to stderr. This allows tools
    like buildman to pick them up rather than suppressing them along with
    the normal build output on stdout.

    Signed-off-by: Chris Packham

    Chris Packham
     
  • Commit a2b96ece5be146f4995d737f047e5bbb76079b8f breaks the enumeration
    of the Image Types. New image types can be appended, but they cannot be
    inserted in the list else backward compatibility is broken.

    This restores the images types as before 2018.11 and move i.MX8 related
    images at the end.

    Signed-off-by: Robert Berger
    Signed-off-by: Stefano Babic
    CC: Tom Rini

    Stefano Babic
     
  • Improvements and fixes or u-boot-rockchip:
    - new board: adds rv1108-elgin-r1 board support
    - rk3288-evb: dts: remove 'vmmc' from emmc node
    - rk3399-puma: dts: remove obsolete DTS node 'vcc5v0_host'

    Tom Rini
     

16 Dec, 2018

15 commits

  • Add the initial support for Elgin R1 board, which is based on the
    RV1108 SoC and has the following features currently supported in
    U-Boot:

    - UART
    - eMMC
    - USB

    Signed-off-by: Otavio Salvador
    Reviewed-by: Philipp Tomsich

    Otavio Salvador
     
  • - Second half of the USB Gadget DM conversion

    Tom Rini
     
  • - Introduce tools-only build for host tools
    - Bugfixes to poplar, syscon and the hashtable, a tee return code
    - Fix a warning on gcc-8 by reworking part of mtk_image to be not unsafe
    wrt strings.
    - serial_stm32 reset support

    Tom Rini
     
  • This is a sync with kernel mainline dts.

    The U-Boot eMMC does not need to care about the power for Rockchip
    SoCs, because if the board is using eMMC, the power will default on
    (for bootrom), so the 'vmmc', 'vqmmc' is only useful for SD in U-Boot.

    Signed-off-by: Kever Yang
    Reviewed-by: Philipp Tomsich

    Kever Yang
     
  • vcc5v0_host and usbhub_enable share gpio4 RK_PA3,
    which is a problem during probing (the second probe
    will trigger a -EBUSY, when trying to get the gpio handle).

    An analysis of the situation shows, that both regulators
    are actually describing the same supply.

    This patch removes the (currenlty not successful probing)
    regulator vcc5v0_host from the DTS and adds the pinctrl-*
    setting to usbhub_enable.

    Signed-off-by: Christoph Muellner
    Reviewed-by: Phiilipp Tomsich

    Christoph Muellner
     
  • + Update the function syscon_node_to_regmap() to force bound on
    syscon uclass and directly use the list of device from DM.
    + Remove the static list syscon_list.

    This patch avoid issue (crash) when syscon_node_to_regmap() is called
    before and after reallocation (list content is invalid).

    Signed-off-by: Patrick Delaunay

    Patrick Delaunay
     
  • Starting from version 8 the GCC, i.e. C compiler, starts complaining about
    possible '\0' terminator loss or, as in this case, garbage copy.

    In function ‘mtk_image_set_gen_header’,
    inlined from ‘mtk_image_set_header’ at tools/mtk_image.c:733:3:
    tools/mtk_image.c:659:2: warning: ‘strncpy’ specified bound 12 equals destination size [-Wstringop-truncation]
    strncpy(hdr->boot.name, bootname, sizeof(hdr->boot.name));
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    In function ‘mtk_brom_parse_imagename’,
    inlined from ‘mtk_image_check_params’ at tools/mtk_image.c:388:9:
    tools/mtk_image.c:325:5: warning: ‘strncpy’ specified bound 32 equals destination size [-Wstringop-truncation]
    strncpy(lk_name, val, sizeof(lk_name));
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Replace it with snprintf() to tell compiler how much room we have in the
    destination buffer for source string.

    Fixes: 3b975a147c3c ("tools: MediaTek: add MTK boot header generation to mkimage")
    Cc: Ryder Lee
    Cc: Weijie Gao
    Signed-off-by: Andy Shevchenko
    Reviewed-by: Weijie Gao

    Andy Shevchenko
     
  • In some cases, UART is configured by early boot stage.
    To be sure of the initial state of UART and to avoid
    spurious chars on console, reset the serial block before
    configuring it.

    Signed-off-by: Patrice Chotard
    Reviewed-by: Simon Glass

    Patrice Chotard
     
  • Commit 4687919684e0 ("serial: Remove DM_FLAG_PRE_RELOC flag in various
    drivers") essentially drops flag DM_FLAG_PRE_RELOC from serial_pl01x
    driver for Poplar platform, because the platform falls into the
    following strategy category made by the commit.

    Surround DM_FLAG_PRE_RELOC flag with OF_CONTROL check, for
    drivers that support both statically declared devices and
    configuration from device tree

    Before the commit lands, Poplar platform works by statically declaring
    pl011 serial device via U_BOOT_DEVICE() with DM_FLAG_PRE_RELOC flag set
    in the driver. But since Poplar also supports device configuration from
    device tree, the commit practically drops the flag for Poplar, and hence
    breaks the platform from booting.

    This patch changes platform code and device tree to initiate pl011
    serial device from device tree rather than static declaration, so that
    above strategy about DM_FLAG_PRE_RELOC applies to Poplar, and therefore
    the reported boot failure gets fixed.

    Reported-by: Igor Opaniuk
    Fixes: 4687919684e0 ("serial: Remove DM_FLAG_PRE_RELOC flag in various drivers")
    Cc: Bin Meng
    Cc: Simon Glass
    Signed-off-by: Shawn Guo
    Reviewed-by: Igor Opaniuk
    Tested-by: Igor Opaniuk
    Reviewed-by: Bin Meng

    Shawn Guo
     
  • Add myself as co-maintainer for poplar board, as I'm actively working
    on the board.

    Signed-off-by: Shawn Guo

    Shawn Guo
     
  • The motivation for this is to allow distributions to distribute all
    possible tools in a generic way, avoiding the need of specific tools
    building for each machine.

    Especially on OpenEmbedded / Yocto Project ecosystem, it is very
    common each BSP to end providing their specific tools when they need
    to generate images for some SoC (e.g MX23 / MX28 in meta-freescale
    case).

    Using this, we can package the tools doing:

    $: make tools-only_defconfig
    $: make tools-only

    Signed-off-by: Otavio Salvador
    [trini: Add MAINTAINERS entry for myself, add to .travis.yml, make
    U-Boot itself buildable to not trip up other frameworks]
    Signed-off-by: Tom Rini

    Otavio Salvador
     
  • The contents of the test subdirectories only make sense when we have
    CONFIG_UNIT_TEST set. We will otherwise attempt to build code on for
    example sandbox that needs CONFIG_UNIT_TEST otherwise and rather than
    complicate the Makefiles simply leave them out when we can.

    Signed-off-by: Tom Rini

    Tom Rini
     
  • The "dm" command under CONFIG_CMD_DM should live under cmd/ rather than
    test/dm/ so move it.

    Signed-off-by: Tom Rini

    Tom Rini
     
  • The commit below incorrectly fixed hexport_r();
    > size = totlen + 1;
    One extra byte is necessary to NULL-terminate a whole buffer, "resp."

    Fixes: f1b20acb4a03 ("hashtable: Fix length calculation in hexport_r")
    Signed-off-by: AKASHI Takahiro

    AKASHI Takahiro
     
  • If OP-TEE core is compiled with support of REE FS and RPMB
    at the same time (CFG_RPMB_FS ?= y; CFG_RPMB_FS ?= y), and persistent
    storage API is used with TEE_STORAGE_PRIVATE storage id, it will
    lead to TA panic.

    E/TC:? 0 TA panicked with code 0xffff0009
    .....
    E/TC:? 0 Call stack:
    E/TC:? 0 0x000000004002f2f8 TEE_OpenPersistentObject at
    lib/libutee/tee_api_objects.c:422

    In this particular case TEE_ERROR_STORAGE_NOT_AVAILABLE is more suitable
    than TEE_ERROR_NOT_IMPLEMENTED, as it provides to a TA a possibility
    to handle this error code [1].

    >From GPD TEE Internal Core specification [2]:
    TEE_ERROR_STORAGE_NOT_AVAILABLE - if the persistent object is stored in a
    storage area which is currently inaccessible. It may be associated with
    the device but unplugged, busy, or inaccessible for some other reason.

    [1]: https://github.com/OP-TEE/optee_os/blob/94db01ef448d1e552161c2d861d57a5f8bda0cc0/lib/libutee/tee_api_objects.c#L419
    [2]: https://globalplatform.org/wp-content/uploads/2018/06/GPD_TEE_Internal_Core_API_Specification_v1.1.2.50_PublicReview.pdf

    Signed-off-by: Igor Opaniuk
    Reviewed-by: Jens Wiklander

    Igor Opaniuk
     

15 Dec, 2018

18 commits