1. 21 May, 2015 1 commit
  2. 22 Jul, 2014 1 commit
  3. 24 Jul, 2013 1 commit
  4. 01 May, 2013 3 commits
    • Wolfgang Denk's avatar
      "env grep" - add support for regular expression matches · be29df6a
      Wolfgang Denk authored
      When CONFIG_REGEX is enabled, the new option "-e" becomes available
      which causes regular expression matches to be used.  This allows for
      example things like these:
      - print all MAC addresses:
      	=> env grep -e eth.*addr
      - print all variables that have at least 2 colons in their value:
      	=> env grep -v -e :.*:
      	addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off
      	ver=U-Boot 2013.04-rc1-00289-g497746b-dirty (Mar 22 2013 - 12:50:25)
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
    • Wolfgang Denk's avatar
      "env grep" - reimplement command using hexport_r() · 5a31ea04
      Wolfgang Denk authored
      Also drop hstrstr_r() which is not needed any more.
      The new code is way more flexible.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
    • Wolfgang Denk's avatar
      hashtable: preparations to use hexport_r() for "env grep" · ea009d47
      Wolfgang Denk authored
      The output of "env grep" is unsorted, and printing is done by a
      private implementation to parse the hash table.  We have all the
      needed code in place in hexport_r() alsready, so let's use this
      instead.  Here we prepare the code for this, without any functional
      changes yet.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
  5. 13 Dec, 2012 5 commits
  6. 18 Sep, 2012 4 commits
  7. 08 Nov, 2011 1 commit
    • Wolfgang Denk's avatar
      env: allow to export only selected variables · 37f2fe74
      Wolfgang Denk authored
      New syntax:
      	env export [-t | -b | -c] [-s size] addr [var ...]
      With this change it is possible to provide a list of variables names
      that shall be exported.  Whenno arguments are given, the whole
      environment gets exported.
      NOTE: The new handling of the "size" argument means a change to the
      user API.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
  8. 29 Jul, 2011 1 commit
  9. 27 Apr, 2011 1 commit
    • Kim Phillips's avatar
      common: add a grepenv command · a000b795
      Kim Phillips authored
      u-boot environments, esp. when boards are shared across multiple
      users, can get pretty large and time consuming to visually parse.
      The grepenv command this patch adds can be used in lieu of printenv
      to facilitate searching.  grepenv works like printenv but limits
      its output only to environment strings (variable name and value
      pairs) that match the user specified substring.
      the following examples are on a board with a 5313 byte environment
      that spans multiple screen pages:
      Example 1:  summarize ethernet configuration:
      => grepenv eth TSEC
      uprcw=setenv ethact $eth;setenv filename p4080ds/R_PPSXX_0xe/rcw_0xe_2sgmii_rev2_high.bin;setenv start 0xe8000000;protect off all;run upimage;protect on all
      upuboot=setenv ethact $eth;setenv filename u-boot.bin;setenv start eff80000;protect off all;run upimage;protect on all
      upucode=setenv ethact $eth;setenv filename fsl_fman_ucode_P4080_101_6.bin;setenv start 0xef000000;protect off all;run upimage;protect on all
      usdboot=setenv ethact $eth;tftp 1000000 $dir/$bootfile;tftp 2000000 $dir/initramfs.cpio.gz.uboot;tftp c00000 $dir/p4080ds-usdpaa.dtb;setenv bootargs root=/dev/ram rw console=ttyS0,115200 $othbootargs;bootm 1000000 2000000 c00000;
      Example 2: detect unused env vars:
      => grepenv etact
      Example 3: reveal hardcoded variables; e.g., for fdtaddr:
      => grepenv fdtaddr
      nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
      ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr
      => grep $fdtaddr
      my_boot=bootm 0x40000000 0x41000000 0x00c00000
      my_dtb=tftp 0x00c00000 $prefix/p4080ds.dtb
      nohvboot=tftp 1000000 $dir/$bootfile;tftp 2000000 $dir/$ramdiskfile;tftp c00000 $dir/$fdtfile;setenv bootargs root=/dev/ram rw ramdisk_size=0x10000000 console=ttyS0,115200;bootm 1000000 2000000 c00000;
      This patch also enables the grepenv command by default on
      corenet_ds based boards (and repositions the DHCP command
      entry to keep the list sorted).
      Signed-off-by: default avatarKim Phillips <kim.phillips@freescale.com>
      Cc: Kumar Gala <kumar.gala@freescale.com>
      Cc: Andy Fleming <afleming@freescale.com>
  10. 09 Jan, 2011 1 commit
  11. 17 Dec, 2010 1 commit
    • Mike Frysinger's avatar
      hashtable: drop all non-reentrant versions · 2eb1573f
      Mike Frysinger authored
      The non-reentrant versions of the hashtable functions operate on a single
      shared hashtable.  So if two different people try using these funcs for
      two different purposes, they'll cause problems for the other.
      Avoid this by converting all existing hashtable consumers over to the
      reentrant versions and then punting the non-reentrant ones.
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
  12. 19 Sep, 2010 1 commit
    • Wolfgang Denk's avatar
      Add hash table support as base for new environment code · a6826fbc
      Wolfgang Denk authored
      This implementation is based on code from uClibc- but was
      modified and extended for use within U-Boot.
      Major modifications and extensions:
      * hsearch() [modified / extended]:
        - While the standard version does not make any assumptions about
          the type of the stored data objects at all, this implementation
          works with NUL terminated strings only.
        - Instead of storing just pointers to the original objects, we
          create local copies so the caller does not need to care about the
          data any more.
        - The standard implementation does not provide a way to update an
          existing entry.  This version will create a new entry or update an
          existing one when both "action == ENTER" and "item.data != NULL".
        - hsearch_r(): Instead of returning 1 on success, we return the
          index into the internal hash table, which is also guaranteed to be
          positive.  This allows us direct access to the found hash table
          slot for example for functions like hdelete().
      * hdelete() [added]:
        - The standard implementation of hsearch(3) does not provide any way
          to delete any entries from the hash table.  We extend the code to
          do that.
      * hexport() [added]:
        - Export the data stored in the hash table in linearized form:
          Entries are exported as "name=value" strings, separated by an
          arbitrary (non-NUL, of course) separator character. This allows to
          use this function both when formatting the U-Boot environment for
          external storage (using '\0' as separator), but also when using it
          for the "printenv" command to print all variables, simply by using
          as '\n" as separator. This can also be used for new features like
          exporting the environment data as text file, including the option
          for later re-import.
        - The entries in the result list will be sorted by ascending key
      * himport() [added]:
        - Import linearized data into hash table.  This is the inverse
          function to hexport(): it takes a linear list of "name=value"
          pairs and creates hash table entries from it.
        - Entries without "value", i. e. consisting of only "name" or
          "name=", will cause this entry to be deleted from the hash table.
        - The "flag" argument can be used to control the behaviour: when
          the H_NOCLEAR bit is set, then an existing hash table will kept,
          i. e. new data will be added to an existing hash table;
          otherwise, old data will be discarded and a new hash table will
          be created.
        - The separator character for the "name=value" pairs can be
          selected, so we both support importing from externally stored
          environment data (separated by NUL characters) and from plain text
          files (entries separated by newline characters).
        - To allow for nicely formatted text input, leading white space
          (sequences of SPACE and TAB chars) is ignored, and entries
          starting (after removal of any leading white space) with a '#'
          character are considered comments and ignored.
        - NOTE: this means that a variable name cannot start with a '#'
        - When using a non-NUL separator character, backslash is used as
          escape character in the value part, allowing for example fo
          multi-line values.
        - In theory, arbitrary separator characters can be used, but only
          '\0' and '\n' have really been tested.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>