Eric Lee / smarc-uboot

24 Jul, 2013

1 commit

01 Jun, 2013

1 commit

  • dfe64e2c8   mtd: resync with Linux-3.7.1 ... Browse Code »
    32

    This patch is essentially an update of u-boot MTD subsystem to
    the state of Linux-3.7.1 with exclusion of some bits:

    - the update is concentrated on NAND, no onenand or CFI/NOR/SPI
    flashes interfaces are updated EXCEPT for API changes.

    - new large NAND chips support is there, though some updates
    have got in Linux-3.8.-rc1, (which will follow on top of this patch).

    To produce this update I used tag v3.7.1 of linux-stable repository.

    The update was made using application of relevant patches,
    with changes relevant to U-Boot-only stuff sticked together
    to keep bisectability. Then all changes were grouped together
    to this patch.

    Signed-off-by: Sergey Lapin
    [scottwood@freescale.com: some eccstrength and build fixes]
    Signed-off-by: Scott Wood

    Sergey Lapin
     

06 Apr, 2013

1 commit

03 Apr, 2013

1 commit

14 Dec, 2012

1 commit

  • be11235ab   env: Hide '.' variables in env print by default ... Browse Code »

    When printing all variables with env print, don't print variables that
    begin with '.'. If env print is called with a '-a' switch, then
    include variables that begin with '.' (just like the ls command).

    Variables printed explicitly will be printed even without the -a.

    Signed-off-by: Joe Hershberger

    Joe Hershberger
     

06 Aug, 2012

1 commit

30 Apr, 2012

1 commit

05 Jan, 2012

1 commit

22 Nov, 2011

3 commits

08 Nov, 2011

1 commit

  • 37f2fe747   env: allow to export only selected variables ... Browse Code »

    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: Wolfgang Denk

    Wolfgang Denk
     

18 Dec, 2010

1 commit

  • 2eb1573f0   hashtable: drop all non-reentrant versions ... Browse Code »

    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: Mike Frysinger

    Mike Frysinger
     

20 Sep, 2010

1 commit

  • ea882baf9   New implementation for internal handling of environment variables. ... Browse Code »

    Motivation:

    * Old environment code used a pessimizing implementation:
    - variable lookup used linear search => slow
    - changed/added variables were added at the end, i. e. most
    frequently used variables had the slowest access times => slow
    - each setenv() would calculate the CRC32 checksum over the whole
    environment block => slow
    * "redundant" envrionment was locked down to two copies
    * No easy way to implement features like "reset to factory defaults",
    or to select one out of several pre-defined (previously saved) sets
    of environment settings ("profiles")
    * No easy way to import or export environment settings

    ======================================================================

    API Changes:

    - Variable names starting with '#' are no longer allowed

    I didn't find any such variable names being used; it is highly
    recommended to follow standard conventions and start variable names
    with an alphanumeric character

    - "printenv" will now print a backslash at the end of all but the last
    lines of a multi-line variable value.

    Multi-line variables have never been formally defined, allthough
    there is no reason not to use them. Now we define rules how to deal
    with them, allowing for import and export.

    - Function forceenv() and the related code in saveenv() was removed.
    At the moment this is causing build problems for the only user of
    this code (schmoogie - which has no entry in MAINTAINERS); may be
    fixed later by implementing the "env set -f" feature.

    Inconsistencies:

    - "printenv" will '\\'-escape the '\n' in multi-line variables, while
    "printenv var" will not do that.

    ======================================================================

    Advantages:

    - "printenv" output much better readable (sorted)
    - faster!
    - extendable (additional variable properties can be added)
    - new, powerful features like "factory reset" or easy switching
    between several different environment settings ("profiles")

    Disadvantages:

    - Image size grows by typically 5...7 KiB (might shrink a bit again on
    systems with redundant environment with a following patch series)

    ======================================================================

    Implemented:

    - env command with subcommands:

    - env print [arg ...]

    same as "printenv": print environment

    - env set [-f] name [arg ...]

    same as "setenv": set (and delete) environment variables

    ["-f" - force setting even for read-only variables - not
    implemented yet.]

    - end delete [-f] name

    not implemented yet

    ["-f" - force delete even for read-only variables]

    - env save

    same as "saveenv": save environment

    - env export [-t | -b | -c] addr [size]

    export internal representation (hash table) in formats usable for
    persistent storage or processing:

    -t: export as text format; if size is given, data will be
    padded with '\0' bytes; if not, one terminating '\0'
    will be added (which is included in the "filesize"
    setting so you can for exmple copy this to flash and
    keep the termination).
    -b: export as binary format (name=value pairs separated by
    '\0', list end marked by double "\0\0")
    -c: export as checksum protected environment format as
    used for example by "saveenv" command
    addr: memory address where environment gets stored
    size: size of output buffer

    With "-c" and size is NOT given, then the export command will
    format the data as currently used for the persistent storage,
    i. e. it will use CONFIG_ENV_SECT_SIZE as output block size and
    prepend a valid CRC32 checksum and, in case of resundant
    environment, a "current" redundancy flag. If size is given, this
    value will be used instead of CONFIG_ENV_SECT_SIZE; again, CRC32
    checksum and redundancy flag will be inserted.

    With "-b" and "-t", always only the real data (including a
    terminating '\0' byte) will be written; here the optional size
    argument will be used to make sure not to overflow the user
    provided buffer; the command will abort if the size is not
    sufficient. Any remainign space will be '\0' padded.

    On successful return, the variable "filesize" will be set.
    Note that filesize includes the trailing/terminating '\0'
    byte(s).

    Usage szenario: create a text snapshot/backup of the current
    settings:

    => env export -t 100000
    => era ${backup_addr} +${filesize}
    => cp.b 100000 ${backup_addr} ${filesize}

    Re-import this snapshot, deleting all other settings:

    => env import -d -t ${backup_addr}

    - env import [-d] [-t | -b | -c] addr [size]

    import external format (text or binary) into hash table,
    optionally deleting existing values:

    -d: delete existing environment before importing;
    otherwise overwrite / append to existion definitions
    -t: assume text format; either "size" must be given or the
    text data must be '\0' terminated
    -b: assume binary format ('\0' separated, "\0\0" terminated)
    -c: assume checksum protected environment format
    addr: memory address to read from
    size: length of input data; if missing, proper '\0'
    termination is mandatory

    - env default -f

    reset default environment: drop all environment settings and load
    default environment

    - env ask name [message] [size]

    same as "askenv": ask for environment variable

    - env edit name

    same as "editenv": edit environment variable

    - env run

    same as "run": run commands in an environment variable

    ======================================================================

    TODO:

    - drop default env as implemented now; provide a text file based
    initialization instead (eventually using several text files to
    incrementally build it from common blocks) and a tool to convert it
    into a binary blob / object file.

    - It would be nice if we could add wildcard support for environment
    variables; this is needed for variable name auto-completion,
    but it would also be nice to be able to say "printenv ip*" or
    "printenv *addr*"

    - Some boards don't link any more due to the grown code size:
    DU405, canyonlands, sequoia, socrates.

    => cc: Matthias Fuchs ,
    Stefan Roese ,
    Heiko Schocher

    - Dropping forceenv() causes build problems on schmoogie

    => cc: Sergey Kubushyn

    - Build tested on PPC and ARM only; runtime tested with NOR and NAND
    flash only => needs testing!!

    Signed-off-by: Wolfgang Denk
    Cc: Matthias Fuchs ,
    Cc: Stefan Roese ,
    Cc: Heiko Schocher
    Cc: Sergey Kubushyn

    Wolfgang Denk
     

07 Jan, 2010

1 commit

  • b821cead7   onenand: Fix compile errors due to FlexOneNAND ... Browse Code »

    This patch fixes the compile error while trying to
    compile for omap3evm.

    env_onenand.c: In function 'env_relocate_spec':
    env_onenand.c:70: error: 'CONFIG_ENV_ADDR_FLEX' undeclared
    (first use in this function)
    env_onenand.c:70: error: (Each undeclared identifier is re
    ported only once
    env_onenand.c:70: error: for each function it appears in.)
    env_onenand.c: In function 'saveenv':
    env_onenand.c:106: error: 'CONFIG_ENV_ADDR_FLEX' undeclare
    d (first use in this function)
    env_onenand.c:107: error: 'CONFIG_ENV_SIZE_FLEX' undeclare
    d (first use in this function)

    Signed-off-by: Sanjeev Premi
    Acked-by: Tom Rix

    Sanjeev Premi
     

14 Nov, 2009

1 commit

27 Jul, 2009

1 commit

17 Jul, 2009

1 commit

08 Jul, 2009

1 commit

13 Jun, 2009

1 commit

03 Dec, 2008

1 commit

11 Sep, 2008

3 commits

14 Aug, 2008

1 commit

  • d438d5084   Fix OneNAND build break ... Browse Code »

    Since page size field is changed from oobblock to writesize. But OneNAND is not updated.
    - fix bufferram management at erase operation
    This patch includes the NAND/OneNAND state filed too.

    Signed-off-by: Kyungmin Park
    Signed-off-by: Scott Wood

    Kyungmin Park
     

11 Aug, 2008

1 commit

  • aa5ffa16d   OneNAND: Remove base address offset usage ... Browse Code »

    While locally preparing some U-Boot patches for ARM based OMAP3 boards, some
    using OneNAND and some using NAND, we found some differences in OneNAND and
    NAND command address handling.

    As this might confuse users (it already confused us), we like to align OneNAND
    and NAND address handling.

    The issue is that cmd_onenand.c subtracts the onenand base address from the
    addresses you type into the u-boot command line so, unlike nand, you can't
    use addresses relative to the start of the onenand part e.g. this won't work:

    onenand read 82000000 280000 400000

    you have to use:

    onenand read 82000000 20280000 400000

    Looking at recent git, the only board currently using OneNAND is Apollon, and
    for this the OneNAND base address is 0 (apollon.h)

    #define CFG_ONENAND_BASE 0x00000000

    so patch below won't break any existing boards and will align OneNAND and NAND
    handling on boards where OneNAND base address is != 0.

    Signed-off-by: Steve Sakoman
    Signed-off-by: Manikandan Pillai
    Signed-off-by: Dirk Behme

    dirk.behme@googlemail.com
     

13 Jul, 2008

1 commit

14 Apr, 2008

1 commit

15 Nov, 2007

1 commit

17 Sep, 2007

1 commit