1. 28 Nov, 2016 1 commit
    • Max Krummenacher's avatar
      tools/env: fix environment alignment tests for block devices · 333ee16d
      Max Krummenacher authored
      commit 183923d3 enforces that the
      environment must start at an erase block boundary.
      
      For block devices the sample fw_env.config does not mandate a erase block size
      for block devices. A missing setting defaults to the full env size.
      
      Depending on the environment location the alignment check now errors out for
      perfectly legal settings.
      
      Fix this by defaulting to the standard blocksize of 0x200 for environments
      stored in a block device.
      That keeps the fw_env.config files for block devices working even with that
      new check.
      Signed-off-by: default avatarMax Krummenacher <max.krummenacher@toradex.com>
      333ee16d
  2. 08 Oct, 2016 1 commit
    • B, Ravi's avatar
      env: tool: add command line option to input lockfile path · d40dbfb7
      B, Ravi authored
      The default lockname is set to /var/lock. This limits the
      usage of this application where OS uses different lockfile
      location parameter.
      For example, In case of android, the default lock
      path location is /data.
      Hence by providing the command line option to input lockfile
      path will be useful to reuse the tool across multiple
      operating system.
      
      usage: ./fw_printenv -l <lockfile path>
      Signed-off-by: default avatarRavi Babu <ravibabu@ti.com>
      d40dbfb7
  3. 07 Oct, 2016 4 commits
  4. 20 Aug, 2016 2 commits
  5. 15 Aug, 2016 1 commit
    • Andreas Fenkart's avatar
      tools/env: ensure environment starts at erase block boundary · 183923d3
      Andreas Fenkart authored
      56086921 added support for unaligned environments access.
      U-boot itself does not support this:
      - env_nand.c fails when using an unaligned offset. It produces an
        error in nand_erase_opts{drivers/mtd/nand/nand_util.c}
      - in env_sf/env_flash the unused space at the end is preserved, but
        not in the beginning. block alignment is assumed
      - env_sata/env_mmc aligns offset/length to the block size of the
        underlying device. data is silently redirected to the beginning of
        a block
      
      There is seems no use case for unaligned environment. If there is
      some useful data at the beginning of the the block (e.g. end of u-boot)
      that would be very unsafe. If the redundant environments are hosted by
      the same erase block then that invalidates the idea of double buffering.
      It might be that unaligned access was allowed in the past, and that
      people with legacy u-boot are trapped. But at the time of 56086921
      it wasn't supported and due to reasons above I guess it was never
      introduced.
      I prefer to remove that (unused) feature in favor of simplicity
      Signed-off-by: default avatarAndreas Fenkart <andreas.fenkart@digitalstrom.com>
      Acked-by: default avatarStefan Agner <stefan.agner@toradex.com>
      183923d3
  6. 26 Jul, 2016 1 commit
  7. 22 Jul, 2016 5 commits
  8. 16 Jul, 2016 1 commit
    • Robert P. J. Day's avatar
      Various, unrelated tree-wide typo fixes. · 62a3b7dd
      Robert P. J. Day authored
          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>
      62a3b7dd
  9. 31 May, 2016 1 commit
  10. 27 May, 2016 5 commits
  11. 02 May, 2016 1 commit
  12. 27 Mar, 2016 1 commit
  13. 26 Mar, 2016 4 commits
  14. 22 Mar, 2016 1 commit
  15. 08 Feb, 2016 7 commits
  16. 14 Dec, 2015 1 commit
  17. 18 Nov, 2015 2 commits
    • Stefano Babic's avatar
      Allow fw env tools to be available as library · 2cb11b35
      Stefano Babic authored
      Sometimes it can be useful to link the fw_ tools instead
      of having the fw_setenv/fw_printenv installed.
      Patch exports the tool as library and allowes to link it
      with own programs.
      Signed-off-by: default avatarStefano Babic <sbabic@denx.de>
      CC: Tom Rini <trini@konsulko.com>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      2cb11b35
    • Michael Heimpold's avatar
      tools/env: allow config filename to be passed via command line argument · 9884f44c
      Michael Heimpold authored
      When for example generating/manipulating SD card/eMMC images which
      contain U-Boot and its environment(s), it is handy to use a given
      configuration file instead of the compiled-in default one.
      And since the default configuration file is expected under /etc
      it's hard for an usual linux user account without special permissions
      to use fw_printenv/fw_setenv for this purpose.
      So allow to pass an optional filename via a new '-c' command
      line argument.
      
      Example:
      
      $ ln -s fw_printenv tools/env/fw_setenv
      $ cat fw_env.config
      test.img 0x20000 0x20000
      test.img 0x40000 0x20000
      
      $ tools/env/fw_printenv -c ./fw_env.config fdt_file
      fdt_file=imx28-duckbill.dtb
      
      $ tools/env/fw_setenv -c ./fw_env.config fdt_file imx28-duckbill-spi.dtb
      
      $ tools/env/fw_printenv -c ./fw_env.config fdt_file
      fdt_file=imx28-duckbill-spi.dtb
      Signed-off-by: default avatarMichael Heimpold <mhei@heimpold.de>
      9884f44c
  18. 18 Jun, 2015 1 commit