05 Nov, 2013

1 commit


24 Jul, 2013

1 commit


12 Mar, 2013

2 commits


01 Sep, 2012

1 commit


07 Jul, 2012

1 commit

  • On at91sam platforms, u-boot grew larger than the allocated size in
    dataflash, the layout was:
    bootstrap 0x00000000
    ubootenv 0x00004200
    uboot 0x00008400
    kernel 0x00042000
    fs 0x00252000

    u-boot with the defconfig doesn't seem to fit in 0x42000 - 0x8400 =
    0x39C00 bytes anymore.

    Now, the layout is:
    bootstrap 0x00000000
    ubootenv 0x00004200
    uboot 0x00008400
    kernel 0x00084000
    fs 0x00294000

    Signed-off-by: Alexandre Belloni
    Signed-off-by: Andreas Bießmann

    Alexandre Belloni
     

21 Jun, 2012

1 commit


29 Nov, 2011

1 commit


03 Aug, 2011

1 commit


30 Oct, 2010

1 commit

  • For ARM systems, before ELF relocation was introduced,
    CONFIG_SKIP_RELOCATE_UBOOT coul be used to prevent *COPYING* the
    U-Boot image from whereever it was loaded to it's link address
    (CONFIG_SYS_TEXT_BASE). The name was badly chosen, as no relocation
    was performed at all, it was just a memcpy().

    With ELF relocation, this does not work like that any more, and
    related boards need to be fixed anyway. So don't keep this relict any
    longer.

    Signed-off-by: Wolfgang Denk
    Tested-by: Heiko Schocher
    Tested-by: Reinhard Meyer

    Wolfgang Denk
     

27 Oct, 2010

1 commit

  • CONFIG_SYS_GBL_DATA_SIZE has always been just a bad workarond for not
    being able to use "sizeof(struct global_data)" in assembler files.
    Recent experience has shown that manual synchronization is not
    reliable enough. This patch renames CONFIG_SYS_GBL_DATA_SIZE into
    GENERATED_GBL_DATA_SIZE which gets automatically generated by the
    asm-offsets tool. In the result, all definitions of this value can be
    deleted from the board config files. We have to make sure that all
    files that reference such data include the new file.

    No other changes have been done yet, but it is obvious that similar
    changes / simplifications can be done for other, related macro
    definitions as well.

    Signed-off-by: Wolfgang Denk
    Acked-by: Kumar Gala

    Wolfgang Denk
     

08 Mar, 2010

1 commit


13 Feb, 2010

2 commits

  • * add a real AT91 GPIO driver instead of header inline code
    * resolve the mixing of port and pins
    * change board config files to use new driver
    * add macros to gpio to realize backward compatibility

    Signed-off-by: Jens Scharsig

    Jens Scharsig
     
  • * add's the new temporary CONFIG_AT91_LEGACY to all board configs
    This will need for backward compatiblity, while change the SoC access
    to c structures. If CONFIG_AT91_LEGACY is defined, the deprecated
    SoC is used.

    Signed-off-by: Jens Scharsig

    Jens Scharsig
     

09 Dec, 2009

1 commit


18 Aug, 2009

1 commit


22 Jul, 2009

1 commit

  • A large number of boards (all AT91 based) duplicated the ROUND()
    macro in their board specific config files. Add the definition to
    include/common.h and clean up the board config files.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

19 Jul, 2009

1 commit


13 Jun, 2009

1 commit


17 Apr, 2009

2 commits


05 Apr, 2009

1 commit


04 Apr, 2009

1 commit

  • According to the doc/feature-removal-schedule.txt, the "autoscr"
    command will be replaced by the "source" command in approximately 6
    months from now.

    This patch prepares this change and starts a 6 month transition
    period as follows:

    - The new "source" command has been added, which implements exactly
    the same functionlaity as the old "autoscr" command before
    - The old "autoscr" command name is kept as an alias for compatibility
    - Command sequences, script files atc. have been adapted to use the
    new "source" command
    - Related environment variables ("autoscript", "autoscript_uname")
    have *not* been adapted yet; these will be renamed resp. removed in
    a separate patch when the support for the "autoscr" command get's
    finally dropped.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

22 Mar, 2009

2 commits


24 Jan, 2009

1 commit

  • This patch renames NAND_MAX_CHIPS to CONFIG_SYS_NAND_MAX_CHIPS and
    changes the default from 8 to 1 for the legacy and the new MTD
    NAND layer. This allows to remove all NAND_MAX_CHIPS definitions
    in the board config files because none of the boards use multi
    chip support (NAND_MAX_CHIPS > 1) so far. The bamboo and the DU440
    define

    #define NAND_MAX_CHIPS CONFIG_SYS_MAX_NAND_DEVICE

    but that's bogus and did not work anyhow.

    Signed-off-by: Wolfgang Grandegger
    Signed-off-by: Scott Wood

    Wolfgang Grandegger
     

06 Dec, 2008

1 commit


21 Nov, 2008

1 commit


19 Oct, 2008

1 commit


11 Sep, 2008

3 commits


10 May, 2008

3 commits