15 Jan, 2019

1 commit


11 Jan, 2019

2 commits


10 Jan, 2019

1 commit


09 Jan, 2019

4 commits


08 Jan, 2019

1 commit


03 Jan, 2019

1 commit


02 Jan, 2019

2 commits


01 Jan, 2019

3 commits


18 Dec, 2018

1 commit


17 Dec, 2018

1 commit


16 Dec, 2018

1 commit


13 Dec, 2018

2 commits

  • Building U-Boot with CONFIG_PCI and CONFIG_DM_PCI enabled, but
    CONFIG_SPL_PCI_SUPPORT disabled, results in following linker
    error:

    lib/built-in.o: In function `fdtdec_get_pci_bar32':
    lib/fdtdec.c:305: undefined reference to `dm_pci_read_bar32'
    fdtdec.c:305:(.text.fdtdec_get_pci_bar32+0x24): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `dm_pci_read_bar32'

    This is because reference to dm_pci_read_bar32() remains in lib/fdtdec.c
    while SPL build does not descend into drivers/pci directory in
    drivers/Makefile if CONFIG_SPL_PCI_SUPPORT is not enabled.

    Fix this by applying appropriate #define guards in lib/fdtdec.c.
    It looks like ns16550.c has the same problem, so fixed that too.

    To simplify this, CONFIG_SPL_PCI_SUPPORT is renamed to CONFIG_SPL_PCI
    (enables use of CONFIG_IS_ENABLED() macro).

    Suggested-by: Vignesh R
    Signed-off-by: Sekhar Nori
    Reviewed-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Sekhar Nori
     
  • This option has crept into use with some boards. Add a warning to try to
    prevent this.

    As an example:
    https://lists.denx.de/pipermail/u-boot/2017-September/304966.html

    Signed-off-by: Simon Glass
    Reviewed-by: Tom Rini

    Simon Glass
     

04 Dec, 2018

4 commits

  • Signed-off-by: Tom Rini

    Tom Rini
     
  • As the core of the subsystem has been converted along with some of the
    drivers, formalize a deadline for migration.

    Cc: Akshay Bhat
    Cc: Andreas Geisreiter
    Cc: Bin Meng
    Cc: Christian Gmeiner
    Cc: Fabio Estevam
    Cc: Jason Liu
    Cc: Ken Lin
    Cc: Ludwig Zenz
    Cc: Marek Vasut
    Cc: Max Krummenacher
    Cc: Nikita Kiryanov
    Cc: Otavio Salvador
    Cc: Peng Fan
    Reviewed-by: Simon Glass
    Cc: Soeren Moch
    Cc: Stefan Roese
    Cc: Stefano Babic
    Cc: Tim Harvey
    Cc: Troy Kisky
    Cc: Tuomas Tynkkynen
    Cc: York Sun
    Signed-off-by: Tom Rini

    Tom Rini
     
  • As much of the USB system has been migrated to DM now, formalize a
    deadline for migration.

    Reviewed-by: Marek Vasut
    Reviewed-by: Simon Glass
    Signed-off-by: Tom Rini

    Tom Rini
     
  • Given that at this point the MMC subsystem itself has been migrated
    along with a number of subsystem drivers, formalize a deadline for
    migration.

    Reviewed-by: Simon Glass
    Cc: Jaehoon Chung
    Signed-off-by: Tom Rini
    Reviewed-by: Simon Goldschmidt
    Reviewed-by: Philipp Tomsich

    Tom Rini
     

30 Nov, 2018

1 commit

  • At present tests are quite slow to run, over a minute on my machine. This
    presents a considerable barrier to bisecting for failures.

    The slowest tests are the filesystem ones and the buildman --fetch-arch
    test. Add a new 'qcheck' target that skips these tests. This reduces test
    time down to about 40 second, still too long, but bearable.

    Signed-off-by: Simon Glass

    Simon Glass
     

29 Nov, 2018

1 commit


21 Nov, 2018

1 commit


15 Nov, 2018

1 commit


30 Oct, 2018

1 commit


20 Oct, 2018

1 commit

  • To prevent accidental build failures the change converts a number of
    NXP LPC32xx specific image targets to be conditionally dependent on
    target build configuration. The wrapped image targets always contain
    a U-Boot SPL binary and the images are supposed to be directly flashed
    on a NAND flash device for read access by LPC32xx NAND MLC controller.

    Signed-off-by: Vladimir Zapolskiy

    Vladimir Zapolskiy
     

16 Oct, 2018

1 commit


09 Oct, 2018

1 commit


08 Oct, 2018

1 commit


05 Oct, 2018

1 commit

  • u-boot.itb depends on u-boot-nodtb.bin, which in turn depends on u-boot.
    u-boot.its from Rockchip make_fit_atf.py (used by {evb,firefly}-rk3399)
    wants to read u-boot but is lacking this dependency, so that u-boot.itb
    cannot be built in one go. Detect its use and add the missing dependency.

    Reported-by: Yousaf Kaukab
    Signed-off-by: Andreas Färber
    Reviewed-by: Philipp Tomsich

    Andreas Färber
     

03 Oct, 2018

1 commit


02 Oct, 2018

1 commit


29 Sep, 2018

1 commit


28 Sep, 2018

1 commit

  • Below is the sequence to embed dtb inside U-Boot,
    1. Remove bootpg and resetvec section if needed
    2. Append dtb
    3. Append bootpg and resetvec section back if removed in step 1

    Above procedure is required only when CONFIG_MPC85xx and
    CONFIG_OF_SEPARATE are defined.

    Add new config CONFIG_MPC85XX_HAVE_RESET_VECTOR to indicate that
    image has resetvec section. Step 1 and step 3 described above are
    required only if this config is y.

    Signed-off-by: Jagdish Gediya
    Reviewed-by: Simon Glass
    Reviewed-by: York Sun

    Jagdish Gediya
     

26 Sep, 2018

1 commit

  • The -fstrict-aliasing option is implicitly enabled at levels -O2,
    -O3, -Os by GCC. This option allows the compiler to assume the
    strictest aliasing rules applicable to the language being compiled.
    For example, the practice of reading from a different union member
    than the one most recently written to (called "type-punning") is
    common. In this case, "type-punning" only works if the memory is
    accessed through the union type, but might not work by taking the
    address, casting the resulting pointer and dereferencing the result,
    which is an undefined behavior per the "strict aliasing rules".

    GCC's -Wstrict-aliasing (included in -Wall) option does not catch
    all cases, but does attempt to catch the more common pitfalls. So
    there are cases that GCC does not report but the codes are violating
    the "strict aliasing rules".

    Given lots of codes that may be written to rely on "type-punning",
    and Linux kernel disables it by -fno-strict-aliasing globally, since
    U-Boot currently does this on nds32/riscv/x86 builds only, extend
    this for all architecture builds.

    Signed-off-by: Bin Meng
    Reviewed-by: Tom Rini
    Reviewed-by: Simon Glass

    Bin Meng
     

20 Sep, 2018

1 commit

  • NAND flavors, like serial and parallel, have a lot in common and would
    benefit to share code. Let's move raw (parallel) NAND specific code in a
    raw/ subdirectory, to ease the addition of a core file in nand/ and the
    introduction of a spi/ subdirectory specific to SPI NANDs.

    Signed-off-by: Miquel Raynal

    Miquel Raynal