28 Feb, 2018

1 commit


06 Sep, 2017

1 commit

  • 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
     

09 Jul, 2015

1 commit

  • Instead of selecting REGEX when NET is enabled, make it the default, but
    allow boards that are tiny to disable it and lose functionality on all
    but the first Ethernet adapter.

    cm-bf548, bf538f-ezkit, and bf533-stamp need this. None appear to have
    more than one Ethernet interface.

    Signed-off-by: Joe Hershberger

    Joe Hershberger
     

21 May, 2015

3 commits

  • When the ethaddr is changed in the env, update the device pdata at the
    same time (only if it is probed for the DM case; only if registered for
    the non-DM case). Again this gets us closer to completely non-polled
    env needed to simplify the net_loop.

    This requires that the NET feature select the REGEX feature.

    Signed-off-by: Joe Hershberger

    Joe Hershberger
     
  • Instead of checking for changes to the env each time we enter the
    net_loop, use the env callbacks to update the values of the variables.
    Don't update the variables when the source was programmatic, since the
    variables were the source of the new value.

    Signed-off-by: Joe Hershberger
    Reviewed-by: Simon Glass

    Joe Hershberger
     
  • Allow the features that use env_attrs to specify regexs for the name

    Signed-off-by: Joe Hershberger
    Reviewed-by: Simon Glass

    Joe Hershberger
     

19 Jul, 2014

1 commit

  • When static inline is used in a header file the function
    should preferably be inlined and if not possible made a
    static function. When declared inside a c file there is a
    static function, which might be inlined. Since SPL uses a
    define to declare the static inline it becomes part of the
    c file although it is declared in a header and clang will
    warn that you have introduced unused static functions. Add
    maybe_unused to prevent such warnings.

    Signed-off-by: Jeroen Hofstee

    Jeroen Hofstee
     

24 Jul, 2013

1 commit


28 Mar, 2013

1 commit


13 Mar, 2013

1 commit

  • Refactor linker-generated array code so that symbols
    which were previously linker-generated are now compiler-
    generated. This causes relocation records of type
    R_ARM_ABS32 to become R_ARM_RELATIVE, which makes
    code which uses LGA able to run before relocation as
    well as after.

    Note: this affects more than ARM targets, as linker-
    lists span possibly all target architectures, notably
    PowerPC.

    Conflicts:
    arch/arm/cpu/arm926ejs/mxs/u-boot-spl.lds
    arch/arm/cpu/arm926ejs/spear/u-boot-spl.lds
    arch/arm/cpu/armv7/omap-common/u-boot-spl.lds
    board/ait/cam_enc_4xx/u-boot-spl.lds
    board/davinci/da8xxevm/u-boot-spl-da850evm.lds
    board/davinci/da8xxevm/u-boot-spl-hawk.lds
    board/vpac270/u-boot-spl.lds

    Signed-off-by: Albert ARIBAUD

    Albert ARIBAUD
     

11 Mar, 2013

1 commit

  • On some architectures certain values of splashimage will lead to
    a data abort exception.

    Document the problem, and implement a callback for splashimage to
    reject such values.

    Cc: Anatolij Gustschin
    Cc: Wolfgang Denk
    Signed-off-by: Nikita Kiryanov
    Acked-by: Igor Grinberg

    Nikita Kiryanov
     

22 Dec, 2012

1 commit

  • SPL doesn't write to the environment. These list entries prevent the
    functions from being garbage-collected, even though nothing will look at
    the list. This caused several SPL builds (e.g. P2020RDB-PC_NAND) to
    break due to size limitations and/or unresolved symbols.

    A static inline function is used to provide a context in which we
    can consume the callback, and thus avoid unused function warnings.

    Signed-off-by: Scott Wood
    Acked-by: Joe Hershberger
    Acked-by: Kim Phillips

    Scott Wood
     

14 Dec, 2012

7 commits