1. 18 Dec, 2014 1 commit
  2. 08 Dec, 2014 1 commit
  3. 05 Dec, 2014 1 commit
  4. 04 Dec, 2014 1 commit
  5. 23 Nov, 2014 2 commits
    • Masahiro Yamada's avatar
      hush: add CONFIG_HUSH_PARSER to Kconfig · 6c775090
      Masahiro Yamada authored
      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: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
    • Christian Gmeiner's avatar
      fs: make it possible to read the filesystem UUID · 59e890ef
      Christian Gmeiner authored
      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
       - 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
      fsuuid <interface> <dev>:<part>
          - print filesystem UUID
      fsuuid <interface> <dev>:<part> <varname>
          - set environment variable to filesystem UUID
      => fsuuid mmc 0:1
      => fsuuid mmc 0:2
      => fsuuid mmc 0:1 uuid1
      => fsuuid mmc 0:2 uuid2
      => printenv uuid1
      => printenv uuid2
      Signed-off-by: default avatarChristian Gmeiner <christian.gmeiner@gmail.com>
      Acked-by: default avatarStephen Warren <swarren@nvidia.com>
  6. 21 Nov, 2014 2 commits
  7. 17 Nov, 2014 1 commit
  8. 07 Nov, 2014 1 commit
  9. 27 Oct, 2014 2 commits
  10. 23 Oct, 2014 3 commits
  11. 22 Oct, 2014 1 commit
  12. 16 Oct, 2014 1 commit
  13. 25 Sep, 2014 1 commit
    • York Sun's avatar
      driver/ddr: Restruct driver to allow standalone memory space · 1d71efbb
      York Sun authored
      U-boot has been initializing DDR for the main memory. The presumption
      is the memory stays as a big continuous block, either linear or
      interleaved. This change is to support putting some DDR controllers
      to separated space without counting into main memory. The standalone
      memory controller could use different number of DIMM slots.
      Signed-off-by: default avatarYork Sun <yorksun@freescale.com>
  14. 24 Sep, 2014 1 commit
  15. 23 Sep, 2014 1 commit
  16. 21 Sep, 2014 1 commit
  17. 30 Aug, 2014 1 commit
    • Tom Rini's avatar
      cmd_bootm.c: Add 'booti' for ARM64 Linux kernel Images · d2b2ffe3
      Tom Rini authored
      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: default avatarTom Rini <trini@ti.com>
  18. 25 Aug, 2014 1 commit
    • Heiko Schocher's avatar
      mtd, ubi, ubifs: resync with Linux-3.14 · ff94bc40
      Heiko Schocher authored
      resync ubi subsystem with linux:
      commit 455c6fdbd219161bd09b1165f11699d6d73de11c
      Author: Linus Torvalds <torvalds@linux-foundation.org>
      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: default avatarHeiko Schocher <hs@denx.de>
      Signed-off-by: default avatarTom Rini <trini@ti.com>
      Cc: Marek Vasut <marex@denx.de>
      Cc: Sergey Lapin <slapin@ossfans.org>
      Cc: Scott Wood <scottwood@freescale.com>
      Cc: Joerg Krause <jkrause@posteo.de>
  19. 21 Aug, 2014 1 commit
    • Thierry Reding's avatar
      net: More BOOTP retry timeout improvements · 92ac8acc
      Thierry Reding authored
      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 f59be6e8
       ("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: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
  20. 14 Aug, 2014 2 commits
  21. 06 Aug, 2014 1 commit
  22. 05 Aug, 2014 1 commit
  23. 04 Aug, 2014 1 commit
  24. 23 Jul, 2014 4 commits
    • Simon Glass's avatar
      sandbox: Support pre-relocation malloc() · 29afe9e6
      Simon Glass authored
      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: default avatarSimon Glass <sjg@chromium.org>
    • Simon Glass's avatar
      Add a simple malloc() implementation for pre-relocation · d59476b6
      Simon Glass authored
      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
      2. It supports algorithms for reducing memory fragmentation and improving
      performace of free(). Before relocation we could happily just not support
      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: default avatarSimon Glass <sjg@chromium.org>
    • Heiko Schocher's avatar
      spi: add config option to enable the WP pin function on st micron flashes · 562f8df1
      Heiko Schocher authored
      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: default avatarHeiko Schocher <hs@denx.de>
      Cc: Jagannadha Sutradharudu Teki <jagannadh.teki@gmail.com>
    • Heiko Schocher's avatar
      pwm, imx6: add support for pwm modul on imx6 · b2f97cf2
      Heiko Schocher authored
      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: default avatarHeiko Schocher <hs@denx.de>
      Acked-by: default avatarStefano Babic <sbabic@denx.de>
      Cc: Wolfgang Denk <wd@denx.de>
  25. 07 Jul, 2014 4 commits
  26. 03 Jul, 2014 1 commit
  27. 20 Jun, 2014 2 commits
    • Simon Glass's avatar
      dm: Update README to encourage conversion to driver model · 2eb31b13
      Simon Glass authored
      Add a note to encourage people to convert drivers to use driver model.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
    • Simon Glass's avatar
      Add an I/O tracing feature · aa53233a
      Simon Glass authored
      When debugging drivers it is useful to see what I/O accesses were done
      and in what order.
      Even if the individual accesses are of little interest it can be useful to
      verify that the access pattern is consistent each time an operation is
      performed. In this case a checksum can be used to characterise the operation
      of a driver. The checksum can be compared across different runs of the
      operation to verify that the driver is working properly.
      In particular, when performing major refactoring of the driver, where the
      access pattern should not change, the checksum provides assurance that the
      refactoring work has not broken the driver.
      Add an I/O tracing feature and associated commands to provide this facility.
      It works by sneaking into the io.h heder for an architecture and redirecting
      I/O accesses through its tracing mechanism.
      For now no commands are provided to examine the trace buffer. The format is
      fairly simple, so 'md' is a reasonable substitute.
      Note: The checksum feature is only useful for I/O regions where the contents
      do not change outside of software control. Where this is not suitable you can
      fall back to manually comparing the addresses. It might be useful to enhance
      tracing to only checksum the accesses and not the data read/written.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>