08 Nov, 2013

1 commit


01 Nov, 2013

1 commit


24 Jul, 2013

1 commit


22 Oct, 2012

1 commit


20 Dec, 2011

1 commit


07 Dec, 2011

2 commits


23 Nov, 2011

1 commit

  • Fix:
    flash.c: In function 'flash_erase':
    flash.c:223:6: warning: variable 'flag' set but not used [-Wunused-but-set-variable]
    flash.c: In function 'write_data':
    flash.c:392:6: warning: variable 'flag' set but not used [-Wunused-but-set-variable]

    Signed-off-by: Anatolij Gustschin

    Anatolij Gustschin
     

16 Oct, 2011

1 commit

  • The top level Makefile does not do any recursion into subdirs when
    cleaning, so these clean/distclean targets in random arch/board dirs
    never get used. Punt them all.

    MAKEALL didn't report any errors related to this that I could see.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     

04 Sep, 2011

1 commit


16 Jul, 2011

1 commit


18 Nov, 2010

1 commit

  • Before this commit, weak symbols were not overridden by non-weak symbols
    found in archive libraries when linking with recent versions of
    binutils. As stated in the System V ABI, "the link editor does not
    extract archive members to resolve undefined weak symbols".

    This commit changes all Makefiles to use partial linking (ld -r) instead
    of creating library archives, which forces all symbols to participate in
    linking, allowing non-weak symbols to override weak symbols as intended.
    This approach is also used by Linux, from which the gmake function
    cmd_link_o_target (defined in config.mk and used in all Makefiles) is
    inspired.

    The name of each former library archive is preserved except for
    extensions which change from ".a" to ".o". This commit updates
    references accordingly where needed, in particular in some linker
    scripts.

    This commit reveals board configurations that exclude some features but
    include source files that depend these disabled features in the build,
    resulting in undefined symbols. Known such cases include:
    - disabling CMD_NET but not CMD_NFS;
    - enabling CONFIG_OF_LIBFDT but not CONFIG_QE.

    Signed-off-by: Sebastien Carlier

    Sebastien Carlier
     

22 Oct, 2010

1 commit


19 Oct, 2010

1 commit

  • The change is currently needed to be able to remove the board
    configuration scripting from the top level Makefile and replace it by
    a simple, table driven script.

    Moving this configuration setting into the "CONFIG_*" name space is
    also desirable because it is needed if we ever should move forward to
    a Kconfig driven configuration system.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

15 Dec, 2009

1 commit


13 Jun, 2009

1 commit


21 Mar, 2009

1 commit

  • A recent gcc added a new unaligned rodata section called '.rodata.str1.1',
    which needs to be added the the linker script. Instead of just adding this
    one section, we use a wildcard ".rodata*" to get all rodata linker section
    gcc has now and might add in the future.

    However, '*(.rodata*)' by itself will result in sub-optimal section
    ordering. The sections will be sorted by object file, which causes extra
    padding between the unaligned rodata.str.1.1 of one object file and the
    aligned rodata of the next object file. This is easy to fix by using the
    SORT_BY_ALIGNMENT command.

    This patch has not be tested one most of the boards modified. Some boards
    have a linker script that looks something like this:

    *(.text)
    . = ALIGN(16);
    *(.rodata)
    *(.rodata.str1.4)
    *(.eh_frame)

    I change this to:

    *(.text)
    . = ALIGN(16);
    *(.eh_frame)
    *(SORT_BY_ALIGNMENT(SORT_BY_NAME(.rodata*)))

    This means the start of rodata will no longer be 16 bytes aligned.
    However, the boundary between text and rodata/eh_frame is still aligned to
    16 bytes, which is what I think the real purpose of the ALIGN call is.

    Signed-off-by: Trent Piepho

    Trent Piepho
     

19 Nov, 2008

1 commit

  • Most of the bss initialization loop increments 4 bytes
    at a time. And the loop end is checked for an 'equal'
    condition. Make the bss end address aligned by 4, so
    that the loop will end as expected.

    Signed-off-by: Selvamuthukumar
    Signed-off-by: Wolfgang Denk

    Selvamuthukumar
     

19 Oct, 2008

1 commit


11 Sep, 2008

1 commit


03 Jul, 2008

1 commit


21 May, 2008

1 commit

  • This commit gets rid of a huge amount of silly white-space issues.
    Especially, all sequences of SPACEs followed by TAB characters get
    removed (unless they appear in print statements).

    Also remove all embedded "vim:" and "vi:" statements which hide
    indentation problems.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

13 Jan, 2008

1 commit

  • With recent toolchain versions, some boards would not build because
    or errors like this one (here for ocotea board when building with
    ELDK 4.2 beta):
    ppc_4xx-ld: section .bootpg [fffff000 -> fffff23b] overlaps section .bss [fffee900 -> fffff8ab]

    For many boards, the .bss section is big enough that it wraps around
    at the end of the address space (0xFFFFFFFF), so the problem will not
    be visible unless you use a 64 bit tool chain for development. On
    some boards however, changes to the code size (due to different
    optimizations) we bail out with section overlaps like above.

    The fix is to add the NOLOAD attribute to the .bss and .sbss
    sections, telling the linker that .bss does not consume any space in
    the image.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

09 Oct, 2006

1 commit


02 Sep, 2006

1 commit

  • Modifications are based on the linux kernel approach and
    support two use cases:

    1) Add O= to the make command line
    'make O=/tmp/build all'

    2) Set environement variable BUILD_DIR to point to the desired location
    'export BUILD_DIR=/tmp/build'
    'make'

    The second approach can also be used with a MAKEALL script
    'export BUILD_DIR=/tmp/build'
    './MAKEALL'

    Command line 'O=' setting overrides BUILD_DIR environent variable.

    When none of the above methods is used the local build is performed and
    the object files are placed in the source directory.

    Marian Balakowicz
     

01 Apr, 2006

1 commit


31 Aug, 2005

1 commit


03 Apr, 2005

1 commit


11 Oct, 2004

1 commit


09 Feb, 2004

1 commit

  • ARM memory layout fixes: the abort-stack is now set up in the
    correct RAM area, and the BSS is zeroed out as it should be.

    Furthermore, the magic variables 'armboot_end' and 'armboot_end_data'
    of the linker scripts are replaced by '__bss_start' and '_end',
    resp., which is a further step to eliminate unnecessary differences
    between the implementation of the CPU architectures.

    wdenk
     

21 Jan, 2004

1 commit


18 Sep, 2003

1 commit

  • - fix spelling errors
    - set GD_FLG_DEVINIT flag only after device function pointers
    are valid
    - Allow CFG_ALT_MEMTEST on systems where address zero isn't
    writeable
    - enable 3.rd UART (ST-UART) on PXA(XScale) CPUs
    - trigger watchdog while waiting in serial driver

    wdenk
     

28 Jun, 2003

1 commit

  • - remove trailing white space, trailing empty lines, C++ comments, etc.
    - split cmd_boot.c (separate cmd_bdinfo.c and cmd_load.c)

    * Patches by Kenneth Johansson, 25 Jun 2003:
    - major rework of command structure
    (work done mostly by Michal Cendrowski and Joakim Kristiansen)

    wdenk
     

16 Jun, 2003

1 commit

  • * Patches by Kyle Harris, 13 Mar 2003:
    - Add FAT partition support
    - Add command support for FAT
    - Add command support for MMC
    ----
    - Add Intel PXA support for video
    - Add Intel PXA support for MMC
    ----
    - Enable MMC and FAT for lubbock board
    - Other misc changes for lubbock board

    wdenk
     

30 May, 2003

1 commit


23 May, 2003

1 commit


15 Mar, 2003

1 commit

  • the HSYNC/VSYNC. Requires new CPLD code (Version 101 for Rev. 100
    boards, version 153 for Rev. 200 boards).

    * Patch by Vladimir Gurevich, 12 Mar 2003:
    Fix relocation problem of statically initialized string pointers
    in common/cmd_pci.c

    * Patch by Kai-Uwe Blöm, 12 Mar 2003:
    Cleanup & bug fixes for JFFS2 code:
    - the memory mangement was broken. It caused havoc on malloc by
    writing beyond the block boundaries.
    - the length calculation for files was wrong, sometimes resulting
    in short file reads.
    - data copying now optionally takes fragment version numbers into
    account, to avoid copying from older data.
    See doc/README.JFFS2 for details.

    wdenk
     

06 Mar, 2003

2 commits

  • - fix bug in BOOTP code (must use NetCopyIP)
    - update of CSB226 port
    - clear BSS segment on XScale
    - added support for i2c_init_board() function
    - update to the Innokom plattform

    * Extend support for redundand environments for configurations where
    environment size < sector size

    wdenk
     
  • Add support for Motorola MPC8266ADS board

    * Patch by Kyle Harris, 19 Feb 2003:
    patches for the Intel lubbock board:
    memsetup.S - general cleanup (based on Robert's csb226 code)
    flash.c - overhaul, actually works now
    lubbock.c - fix init funcs to return proper value

    * Patch by Kenneth Johansson, 26 Feb 2003:
    - Fixed off by one in RFTA calculation.
    - No need to abort when LDF is lower than we can program it's only
    minimum timing so clamp it to what we can do.
    - Takes function pointer to function for reading the spd_nvram. Usefull
    for faking data or hardcode a module without the nvram.
    - fix other user for above change
    - fix some comments.

    * Patches by Brian Waite, 26 Feb 2003:
    - fix port for evb64260 board
    - fix PCI for evb64260 board
    - fix PCI scan

    * Patch by Reinhard Meyer, 1 Mar 2003:
    Add support for EMK TOP860 Module

    * Patch by Yuli Barcohen, 02 Mar 2003:
    Add SPD EEPROM support for MPC8260ADS board

    wdenk
     

03 Nov, 2002

1 commit