23 Nov, 2014

2 commits

  • The README file states that the macros beginning with "CONFIG_SYS_"
    depend on the hardware etc. and should not be meddled with if you do
    not what you're doing.
    We have already screwed up with this policy; we have given the prefix
    "CONFIG_SYS_" to many user-selectable configurations.
    Here, "CONFIG_SYS_HUSH_PARSER" is one of them. Users can enable it
    if they want to use a more powerful command line parser, or disable it
    if they only need a simple one.

    This commit attempts to rename CONFIG_SYS_HUSH_PARSER to
    CONFIG_HUSH_PARSER and move it to Kconfig.

    Every board maintainer is expected to enable CONFIG_HUSH_PARSER
    (= add "CONFIG_HUSH_PARSER=y" to his defconfig file) and remove
    "#define CONFIG_SYS_HUSH_PARSER" from his header file.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     
  • Some filesystems have a UUID stored in its superblock. To
    allow using root=UUID=... for the kernel command line we
    need a way to read-out the filesystem UUID.

    changes rfc -> v1:
    - make the environment variable an option parameter. If not
    given, the UUID is printed out. If given, it is stored in the env
    variable.
    - corrected typos
    - return error codes

    changes v1 -> v2:
    - fix return code of do_fs_uuid(..)
    - document do_fs_uuid(..)
    - implement fs_uuid_unsuported(..) be more consistent with the
    way other optional functionality works

    changes v2 -> v3:
    - change ext4fs_uuid(..) to make use of #if .. #else .. #endif
    construct to get rid of unreachable code

    Hit any key to stop autoboot: 0
    => fsuuid
    fsuuid - Look up a filesystem UUID

    Usage:
    fsuuid :
    - print filesystem UUID
    fsuuid :
    - set environment variable to filesystem UUID

    => fsuuid mmc 0:1
    d9f9fc05-45ae-4a36-a616-fccce0e4f887
    => fsuuid mmc 0:2
    eb3db83c-7b28-499f-95ce-9e0bb21cda81
    => fsuuid mmc 0:1 uuid1
    => fsuuid mmc 0:2 uuid2
    => printenv uuid1
    uuid1=d9f9fc05-45ae-4a36-a616-fccce0e4f887
    => printenv uuid2
    uuid2=eb3db83c-7b28-499f-95ce-9e0bb21cda81
    =>

    Signed-off-by: Christian Gmeiner
    Acked-by: Stephen Warren

    Christian Gmeiner
     

17 Nov, 2014

1 commit


08 Nov, 2014

1 commit


28 Oct, 2014

1 commit


27 Oct, 2014

2 commits


24 Oct, 2014

1 commit

  • CONFIG_SYS_HZ is always defined as 1000 in config_fallbacks.h
    (but some boards still have redundant definitions).

    This commit moves the definition and the document in README to
    Kconfig. Since lib/Kconfig can assure that CONFIG_SYS_HZ is 1000,
    the sanity check in lib/time.c should be removed.

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Marek Vasut

    Masahiro Yamada
     

23 Oct, 2014

3 commits


17 Oct, 2014

1 commit


26 Sep, 2014

1 commit


25 Sep, 2014

2 commits


24 Sep, 2014

2 commits


22 Sep, 2014

1 commit


30 Aug, 2014

1 commit

  • The default format for arm64 Linux kernels is the "Image" format,
    described in Documentation/arm64/booting.txt. This, along with an
    optional gzip compression on top is all that is generated by default.
    The Image format has a magic number within the header for verification,
    a text_offset where the Image must be run from, an image_size that
    includes the BSS and reserved fields.

    This does not support automatic detection of a gzip compressed image.

    Signed-off-by: Tom Rini

    Tom Rini
     

29 Aug, 2014

1 commit


26 Aug, 2014

1 commit

  • resync ubi subsystem with linux:

    commit 455c6fdbd219161bd09b1165f11699d6d73de11c
    Author: Linus Torvalds
    Date: Sun Mar 30 20:40:15 2014 -0700

    Linux 3.14

    A nice side effect of this, is we introduce UBI Fastmap support
    to U-Boot.

    Signed-off-by: Heiko Schocher
    Signed-off-by: Tom Rini
    Cc: Marek Vasut
    Cc: Sergey Lapin
    Cc: Scott Wood
    Cc: Joerg Krause

    Heiko Schocher
     

25 Aug, 2014

1 commit


22 Aug, 2014

1 commit

  • It's not unusual for DHCP servers to take a couple hundred milliseconds
    to respond to DHCP discover messages. One possible reason for the delay
    can be that the server checks (typically using an ARP request) that the
    IP it's about to hand out isn't in use yet. To make matters worse, some
    servers may also queue up requests and process them sequentially, which
    can cause excessively long delays if clients retry too fast.

    Commit f59be6e850b3 ("net: BOOTP retry timeout improvements") shortened
    the retry timeouts significantly, but the BOOTP/DHCP implementation in
    U-Boot doesn't handle that well because it will ignore incoming replies
    to earlier requests. In one particular setup this increases the time it
    takes to obtain a DHCP lease from 630 ms to 8313 ms.

    This commit attempts to fix this in two ways. First it increases the
    initial retry timeout from 10 ms to 250 ms to give DHCP servers some
    more time to respond. At the same time a cache of outstanding DHCP
    request IDs is kept so that the implementation will know to continue
    transactions even after a retransmission of the DISCOVER message. The
    maximum retry timeout is also increased from 1 second to 2 seconds. An
    ID cache of size 4 will keep DHCP requests around for 8 seconds (once
    the maximum retry timeout has been reached) before dropping them. This
    should give servers plenty of time to respond. If it ever turns out
    that this isn't enough, the size of the cache can easily be increased.

    With this commit the DHCP lease on the above-mentioned setup still takes
    longer (1230 ms) than originally, but that's an acceptable compromise to
    improve DHCP lease acquisition time for a broader range of setups.

    To make it easier to benchmark DHCP in the future, this commit also adds
    the time it took to obtain a lease to the final "DHCP client bound to
    address x.x.x.x" message.

    Tested-by: Stephen Warren
    Signed-off-by: Thierry Reding

    Thierry Reding
     

14 Aug, 2014

2 commits


11 Aug, 2014

1 commit


08 Aug, 2014

1 commit


06 Aug, 2014

3 commits


04 Aug, 2014

1 commit


23 Jul, 2014

4 commits

  • Set up and zero global data before board_init_f() is called so that we can
    remove the need for CONFIG_SYS_GENERIC_GLOBAL_DATA.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • If we are to have driver model before relocation we need to support some
    way of calling memory allocation routines.

    The standard malloc() is pretty complicated:

    1. It uses some BSS memory for its state, and BSS is not available before
    relocation

    2. It supports algorithms for reducing memory fragmentation and improving
    performace of free(). Before relocation we could happily just not support
    free().

    3. It includes about 4KB of code (Thumb 2) and 1KB of data. However since
    this has been loaded anyway this is not really a problem.

    The simplest way to support pre-relocation malloc() is to reserve an area
    of memory and allocate it in increasing blocks as needed. This
    implementation does this.

    To enable it, you need to define the size of the malloc() pool as described
    in the README. It will be located above the pre-relocation stack on
    supported architectures.

    Note that this implementation is only useful on machines which have some
    memory available before dram_init() is called - this includes those that
    do no DRAM init (like tegra) and those that do it in SPL (quite a few
    boards). Enabling driver model preior to relocation for the rest of the
    boards is left for a later exercise.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • enable the W#/Vpp signal to disable writing to the status
    register on ST MICRON flashes like the N25Q128 thorugh
    the new config option CONFIG_SYS_SPI_ST_ENABLE_WP_PIN

    Signed-off-by: Heiko Schocher
    Cc: Jagannadha Sutradharudu Teki

    Heiko Schocher
     
  • add basic support for the pwm modul found on imx6.
    Pieces of this code are based on linux code from drivers/pwm/pwm-imx.c
    Commit "cd3de83f1476 Linux 3.16-rc4"

    Signed-off-by: Heiko Schocher
    Acked-by: Stefano Babic
    Cc: Wolfgang Denk

    Heiko Schocher
     

08 Jul, 2014

4 commits


03 Jul, 2014

1 commit

  • Adding support to load and start the Layerscape Management Complex (MC)
    firmware. First, the MC GCR register is set to 0 to reset all cores. MC
    firmware and DPL images are copied from their location in NOR flash to
    DDR. MC registers are updated with the location of these images.
    Deasserting the reset bit of MC GCR register releases core 0 to run.
    Core 1 will be released by MC firmware. Stop bits are not touched for
    this step. U-boot waits for MC until it boots up. In case of a failure,
    device tree is updated accordingly. The MC firmware image uses FIT format.

    Signed-off-by: J. German Rivera
    Signed-off-by: York Sun
    Signed-off-by: Lijun Pan
    Signed-off-by: Shruti Kanetkar

    J. German Rivera