08 Sep, 2017

6 commits


07 Sep, 2017

8 commits


06 Sep, 2017

4 commits

  • The target is not currently mentioned anywhere. Add it to the help so
    people can find it.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • This was broken by the recent environment refactoring. Specifically:

    $ make environ
    scripts/Makefile.build:59: tools/environ/Makefile: No such file or directory
    make[1]: *** No rule to make target 'tools/environ/Makefile'. Stop.
    make: *** [Makefile:1469: environ] Error 2

    Fix this by updating the Makefile and adjusting the #include filesnames in
    two C files.

    Fixes: ec74f5f (Makefile: Rename 'env' target to 'environ')
    Reported-by: Måns Rullgård
    Signed-off-by: Simon Glass

    Simon Glass
     
  • Since commit 842778a09104 ("usb: gadget: g_dnl: only set iSerialNumber
    if we have a serial#") "fastboot devices" stopped to show correct device
    serial number for TI boards, showing this line instead:

    ???????????? fastboot

    This is because serial# env variable could be set after g_dnl gadget was
    initialized (e.g. by using env_set() in the board file).

    To fix this, let's update internal serial number variable (g_dnl_serial)
    when "serial#" env var is changed.

    Signed-off-by: Sam Protsenko
    Cc: Felipe Balbi
    Tested-by: Heiko Schocher
    Acked-by: Łukasz Majewski
    Reviewed-by: Marek Vasut

    Sam Protsenko
     
  • With the move of environment code from common/ to env/ a number of
    changes needed to be made to various make targets. We missed updating
    some of the files required for out of tree builds of the tools. Correct
    the 'environ' target to know that we need to work under tools/env/ still
    (not tools/environ/) and then update the wrappers in env_attr.c and
    env_flags.c to point to the new correct file.

    Reported-by: Peter Robinson
    Tested-by: Peter Robinson
    Signed-off-by: Tom Rini

    Tom Rini
     

05 Sep, 2017

15 commits


04 Sep, 2017

7 commits

  • Signed-off-by: Tom Rini

    Tom Rini
     
  • When enabling CONFIG_CMD_BLOB and/or CONFIG_CMD_DEKBLOB, the build fails
    with a linker error:
    ...
    LD u-boot
    arch/arm/mach-imx/built-in.o: In function `blob_encap_dek':
    /home/clemens/dev/u-boot/arch/arm/mach-imx/cmd_dek.c:46: undefined
    reference to `blob_dek'

    This is due to an error in the Makefile, resulting in obj-yy/obj-yn/..
    and fsl_blob.o is therefore not linked.

    Fix it by splitting it up into two obj-y lines.

    Signed-off-by: Clemens Gruber
    Reviewed-by: Fabio Estevam

    Clemens Gruber
     
  • Signed-off-by: Lukasz Majewski

    Lukasz Majewski
     
  • Add some documentation for the live device tree support in U-Boot. This
    was missing from the initial series.

    Signed-off-by: Simon Glass
    Suggested-by: Lukasz Majewski
    Reviewed-by: Łukasz Majewski

    Simon Glass
     
  • Since ee95d10 (fdt: Build the new python libfdt module), a number of
    additional files are auto-generated/installed into the tools directory.
    List these in .gitignore to suppress having them listed as untracked.

    Signed-off-by: Philipp Tomsich
    References: ee95d10 (fdt: Build the new python libfdt module)
    Reviewed-by: Simon Glass

    Philipp Tomsich
     
  • This commit brings things back to the well known working state of the
    command.
    -
    With commit 9620d87259572ef21f0df60988d9a932ca673779
    (cmd/fdt: support single value replacement within an array)

    there was an error introduced modifying (inserting) a property to a
    device-tree node.
    fdt_getprop(...) returnes a len with -1 for a non-existing property, but
    a memcpy with len -1 isn't a good idea and things went wrong (crash).
    -
    Some times later Tom did repair this
    with commit 99bb38e2cce9d99238458e0f6d1880c6d2e80a4d
    (fdt: Check for NULL return from fdt_getprop in 'fdt set')

    This repairs the crash but the behaviour of the command isn't like
    before, it makes it impossible to insert a property.
    -

    Signed-off-by: Hannes Schmelzer
    Acked-by: Simon Glass

    Hannes Schmelzer
     
  • The CONFIG_BLK conversion involves quite invasive changes in the U-Boot
    code, with #ifdefs and different code paths. We should try to move over to
    this soon so we can drop the old code.

    Set a deadline of 9 months for this work, rounded up to the next release.

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

    Simon Glass