1. 01 Aug, 2016 1 commit
  2. 22 Jul, 2016 2 commits
    • yeongjun Kim's avatar
      fixing typo error in README file. CPU15 -> CP15 · 90211f77
      yeongjun Kim authored and Tom Rini's avatar Tom Rini committed
      It looks typo error.
      Not CPU15, CP15(CoProcessor15)
      Signed-off-by: default avataryeongjun Kim <iam.yeongjunkim@gmail.com>
    • Thomas Gleixner's avatar
      spl: Lightweight UBI and UBI fastmap support · 6f4e7d3c
      Thomas Gleixner authored and Tom Rini's avatar Tom Rini committed
      Booting a payload out of NAND FLASH from the SPL is a crux today, as
      it requires hard partioned FLASH. Not a brilliant idea with the
      reliability of todays NAND FLASH chips.
      The upstream UBI + UBI fastmap implementation which is about to
      brought to u-boot is too heavy weight for SPLs as it provides way more
      functionality than needed for a SPL and does not even fit into the
      restricted SPL areas which are loaded from the SoC boot ROM.
      So this provides a fast and lightweight implementation of UBI scanning
      and UBI fastmap attach. The scan and logical to physical block mapping
      code is developed from scratch, while the fastmap implementation is
      lifted from the linux kernel source and stripped down to fit the SPL
      The text foot print on the board which I used for development is:
      6854	0	0	6854	1abd
      Attaching a NAND chip with 4096 physical eraseblocks (4 blocks are
      reserved for the SPL) takes:
      In full scan mode:      1172ms
      In fa...
  3. 16 Jul, 2016 1 commit
    • Robert P. J. Day's avatar
      Various, unrelated tree-wide typo fixes. · 62a3b7dd
      Robert P. J. Day authored and Tom Rini's avatar Tom Rini committed
          Fix a number of typos, including:
           * "compatble" -> "compatible"
           * "eanbeld" -> "enabled"
           * "envrionment" -> "environment"
           * "FTD" -> "FDT" (for "flattened device tree")
           * "ommitted" -> "omitted"
           * "overriden" -> "overridden"
           * "partiton" -> "partition"
           * "propogate" -> "propagate"
           * "resourse" -> "resource"
           * "rest in piece" -> "rest in peace"
           * "suport" -> "support"
           * "varible" -> "variable"
      Signed-off-by: default avatarRobert P. J. Day <rpjday@crashcourse.ca>
  4. 15 Jul, 2016 2 commits
  5. 11 Jul, 2016 1 commit
  6. 01 Jul, 2016 1 commit
  7. 12 Jun, 2016 1 commit
  8. 27 May, 2016 1 commit
  9. 20 May, 2016 1 commit
    • Nikita Kiryanov's avatar
      cmd: eeprom: add support for layout aware commands · aa9e6044
      Nikita Kiryanov authored and Tom Rini's avatar Tom Rini committed
      Introduce the (optional) eeprom print and eeprom update commands.
      These commands are eeprom layout aware:
      * The eeprom print command prints the contents of the eeprom in a human
        readable way (eeprom layout fields, and data formatted to be fit for human
      * The eeprom update command allows user to update eeprom fields by specifying
        the field name, and providing the new data in a human readable format (same
        format as displayed by the eeprom print command).
      * Both commands can either auto detect the layout, or be told which layout to
      New CONFIG options:
      CONFIG_CMD_EEPROM_LAYOUT - enables commands.
      CONFIG_EEPROM_LAYOUT_HELP_STRING - tells user what layout names are supported
      Feature API:
      __weak int parse_layout_version(char *str)
      	- override to provide your own layout name parsing
      __weak void __eeprom_layout_assign(struct eeprom_layout *layout, int layout_version);
      	- override to setup the layout metadata based on the version
      __weak int eeprom_layout_detect(unsigned char *data)
      	- override to provide your own algorithm for detecting layout version
      	- contains various printing and updating functions for common types of
      	  eeprom fields. Can be used for defining custom layouts.
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Marek Vasut <marex@denx.de>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Cc: Tom Rini <trini@konsulko.com>
      Signed-off-by: default avatarNikita Kiryanov <nikita@compulab.co.il>
  10. 17 May, 2016 2 commits
  11. 11 Apr, 2016 1 commit
  12. 01 Apr, 2016 1 commit
  13. 22 Mar, 2016 1 commit
  14. 14 Mar, 2016 1 commit
    • Simon Glass's avatar
      Kconfig: Move CONFIG_FIT and related options to Kconfig · 73223f0e
      Simon Glass authored and Tom Rini's avatar Tom Rini committed
      There are already two FIT options in Kconfig but the CONFIG options are
      still in the header files. We need to do a proper move to fix this.
      Move these options to Kconfig and tidy up board configuration:
      Unfortunately the first one is a little complicated. We need to make sure
      this option is not enabled in SPL by this change. Also this option is
      enabled automatically in the host builds by defining CONFIG_FIT in the
      image.h file. To solve this, add a new IMAGE_USE_FIT #define which can
      be used in files that are built on the host but must also build for U-Boot
      and SPL.
      Note: Masahiro's moveconfig.py script is amazing.
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      [trini: Add microblaze change, various configs/ re-applies]
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
  15. 26 Feb, 2016 1 commit
    • Alexandre Messier's avatar
      net: bootp: Add environment variable for timeout period · 50768f5b
      Alexandre Messier authored and Joe Hershberger's avatar Joe Hershberger committed
      There is currently one config option (CONFIG_NET_RETRY_COUNT) that
      is available to tune the retries of the network stack.
      Unfortunately, it is global to all protocols, and the value is
      interpreted differently in all of them.
      Add a new environment variable that directly sets the retry period for
      BOOTP timeouts. If this new value is not set, the period is still derived
      from the default number of retries, or from CONFIG_NET_RETRY_COUNT if
      defined. When both the new variable is set and CONFIG_NET_RETRY_COUNT
      is defined, the variable has precedence.
      Signed-off-by: default avatarAlexandre Messier <amessier@tycoint.com>
  16. 08 Feb, 2016 2 commits
  17. 06 Feb, 2016 1 commit
  18. 29 Jan, 2016 2 commits
  19. 25 Jan, 2016 1 commit
  20. 19 Jan, 2016 1 commit
    • Tom Rini's avatar
      vsprintf.c: Always enable CONFIG_SYS_VSNPRINTF · 947c626d
      Tom Rini authored
      Enabling this function always removes some class of string saftey issues.
      The size change here in general is about 400 bytes and this seems a reasonable
      Cc: Peng Fan <peng.fan@nxp.com>
      Cc: Peter Robinson <pbrobinson@gmail.com>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      Cc: Adrian Alonso <aalonso@freescale.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Hans de Goede <hdegoede@redhat.com>
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
  21. 14 Jan, 2016 1 commit
  22. 08 Jan, 2016 1 commit
  23. 15 Dec, 2015 3 commits
    • York Sun's avatar
      armv8: fsl-layerscale: Rewrite reserving memory for MC and debug server · c0492141
      York Sun authored
      MC and debug server are not board-specific. Move reserving memory to SoC
      file, using the new board_reserve_ram_top function. Reduce debug server
      memory by 2MB to make room for secure memory.
      In the system with MC and debug server, the top of u-boot memory
      is not the end of memory. PRAM is not used for this reservation.
      Signed-off-by: default avatarYork Sun <yorksun@freescale.com>
    • York Sun's avatar
      common: Rewrite hiding the end of memory · aabd7ddb
      York Sun authored
      As the name may be confusing, the CONFIG_SYS_MEM_TOP_HIDE reserves
      some memory from the end of ram, tracked by gd->ram_size. It is not
      always the top of u-boot visible memory. Rewrite the macro with a
      weak function to provide flexibility for complex calcuation. Legacy
      use of this macro is still supported.
      Signed-off-by: default avatarYork Sun <yorksun@freescale.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    • York Sun's avatar
      Reserve secure memory · e8149522
      York Sun authored
      Secure memory is at the end of memory, separated and reserved
      from OS, tracked by gd->secure_ram. Secure memory can host
      MMU tables, security monitor, etc. This is different from PRAM
      used to reserve private memory. PRAM offers memory at the top
      of u-boot memory, not necessarily the real end of memory for
      systems with very large DDR. Using the end of memory simplifies
      MMU setup and avoid memory fragmentation.
      "bdinfo" command shows gd->secure_ram value if this memory is
      marked as secured.
      Signed-off-by: default avatarYork Sun <yorksun@freescale.com>
  24. 30 Nov, 2015 1 commit
  25. 22 Nov, 2015 1 commit
  26. 20 Nov, 2015 4 commits
  27. 13 Nov, 2015 1 commit
    • Fabio Estevam's avatar
      board_init: Change the logic to setup malloc_base · 9ac4fc82
      Fabio Estevam authored and Tom Rini's avatar Tom Rini committed
      Prior to commit 5ba534d2
       ("arm: Switch 32-bit ARM to using generic
      global_data setup") we used to have assembly code that configured the
      malloc_base address.
      Since this commit we use the board_init_f_mem() function in C to setup
      malloc_base address.
      In board_init_f_mem() there was a deliberate choice to support only
      early malloc() or full malloc() in SPL, but not both.
      Adapt this logic to allow both to be used, one after the other, in SPL.
      This issue has been observed in a Congatec board, where we need to
      retrieve the manufacturing information from the SPI NOR (the SPI API
      calls malloc) prior to configuring the DRAM. In this case as malloc_base
      was not configured we always see malloc to fail.
      With this change we are able to use malloc in SPL prior to DRAM gets
      Also update the CONFIG_SYS_SPL_MALLOC_START entry in the README file.
      Signed-off-by: default avatarFabio Estevam <fabio.estevam@freescale.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
  28. 12 Nov, 2015 1 commit
  29. 28 Oct, 2015 1 commit
    • Albert ARIBAUD \(3ADEV\)'s avatar
      net: TFTP: variables cleanup and addition · f5fb7346
      Albert ARIBAUD \(3ADEV\) authored and Joe Hershberger's avatar Joe Hershberger committed
      TFTP source and destination port variable names are
      'tftpsrcp' and 'tftpdstp' in the code, but 'tftpsrcport'
      and 'tftpdstport' in the README file. Fix the README.
      Add environment variable 'tftptimeoutcountmax'. As per the
      comments about the global variable tftp_timeout_count_max,
      make sure tftptimeoutcountmax is nonnegative.
      Introduce configuration option CONFIG_NET_TFTP_VARS,
      which controls whether environment variables tftpblocksize,
      tftptimeout, and tftptimoueoutcountmax are read by the TFTP
      client code. CONFIG_NET_TFTP_VARS defaults to y but can be
      set to n by targets with to tight size contraints.
      Make bf527-ezkit set CONFIG_NET_TFTP_VARS to n to keep the
      target size below limit.
  30. 26 Oct, 2015 1 commit