Eric Lee / smarc-uboot

01 Nov, 2013

1 commit

15 Oct, 2013

1 commit

24 Jul, 2013

1 commit

02 Dec, 2011

1 commit

16 Oct, 2011

1 commit

  • 464c79207   punt unused clean/distclean targets ... Browse Code »

    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
     

28 Nov, 2010

1 commit

  • ee8028b7f   ppc4xx: Cleanup for partial linking and --gc-sections ... Browse Code »

    This commit adapts 4xx boards for partial linking with --gc-sections.

    Signed-off-by: Stefan Roese
    Signed-off-by: Wolfgang Denk
    Cc: Stefan Roese
    Cc: Tirumala Marri
    Cc: David Updegraff
    Cc: Matthias Fuchs
    Cc: Dirk Eibach
    Cc: Larry Johnson
    Cc: Peter De Schrijver
    Cc: Niklaus Giger
    Cc: Daniel Poirot
    Acked-by: Stefan Roese

    Wolfgang Denk
     

18 Nov, 2010

1 commit

  • 6d8962e81   Switch from archive libraries to partial linking ... Browse Code »

    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
     

19 Oct, 2010

2 commits

  • 2ae182419   Makefile: move all Power Architecture boards into boards.cfg ... Browse Code »

    Clean up Makefile, and drop a lot of the config.mk files on the way.

    We now also automatically pick all boards that are listed in
    boards.cfg (and with all configurations), so we can drop the redundant
    entries from MAKEALL to avoid building these twice.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     
  • 14d0a02a1   Rename TEXT_BASE into CONFIG_SYS_TEXT_BASE ... Browse Code »

    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
     

04 Aug, 2010

1 commit

  • cdb749778   Rename getenv_r() into getenv_f() ... Browse Code »

    While running from flash, i. e. before relocation, we have only a
    limited C runtime environment without writable data segment. In this
    phase, some configurations (for example with environment in EEPROM)
    must not use the normal getenv(), but a special function. This
    function had been called getenv_r(), with the idea that the "_r"
    suffix would mean the same as in the _r_eentrant versions of some of
    the C library functions (for example getdate vs. getdate_r, getgrent
    vs. getgrent_r, etc.).

    Unfortunately this was a misleading name, as in U-Boot the "_r"
    generally means "running from RAM", i. e. _after_ relocation.

    To avoid confusion, rename into getenv_f() [as "running from flash"]

    Signed-off-by: Wolfgang Denk
    Acked-by: Detlev Zundel

    Wolfgang Denk
     

02 Nov, 2009

1 commit

03 Oct, 2009

1 commit

  • 858290178   ppc: Enable full relocation to RAM ... Browse Code »

    The following changes allow U-Boot to fully relocate from flash to
    RAM:
    - Remove linker scripts' .fixup sections from the .text section
    - Add -mrelocatable to PLATFORM_RELFLAGS for all boards
    - Define CONFIG_RELOC_FIXUP_WORKS for all boards

    Previously, U-Boot would partially relocate, but statically initialized
    pointers needed to be manually relocated.

    Signed-off-by: Peter Tyser

    Peter Tyser
     

28 Sep, 2009

1 commit

11 Sep, 2009

1 commit

  • d1c3b2752   ppc4xx: Big cleanup of PPC4xx defines ... Browse Code »

    This patch cleans up multiple issues of the 4xx register (mostly
    DCR, SDR, CPR, etc) definitions:

    - Change lower case defines to upper case (plb4_acr -> PLB4_ACR)
    - Change the defines to better match the names from the
    user's manuals (e.g. cprpllc -> CPR0_PLLC)
    - Removal of some unused defines

    Please test this patch intensive on your PPC4xx platform. Even though
    I tried not to break anything and tested successfully on multiple
    4xx AMCC platforms, testing on custom platforms is recommended.

    Signed-off-by: Stefan Roese

    Stefan Roese
     

21 Mar, 2009

1 commit

  • f62fb9994   Fix all linker script to handle all rodata sections ... Browse Code »

    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

  • 9b827cf17   Align end of bss by 4 bytes ... Browse Code »

    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
     

10 Nov, 2008

1 commit

19 Oct, 2008

1 commit

11 Sep, 2008

1 commit

03 Jul, 2008

1 commit

12 Jun, 2008

1 commit

  • 9973e3c61   Change initdram() return type to phys_size_t ... Browse Code »

    This patch changes the return type of initdram() from long int to phys_size_t.
    This is required for a couple of reasons: long int limits the amount of dram
    to 2GB, and u-boot in general is moving over to phys_size_t to represent the
    size of physical memory. phys_size_t is defined as an unsigned long on almost
    all current platforms.

    This patch *only* changes the return type of the initdram function (in
    include/common.h, as well as in each board's implementation of initdram). It
    does not actually modify the code inside the function on any of the platforms;
    platforms which wish to support more than 2GB of DRAM will need to modify
    their initdram() function code.

    Build tested with MAKEALL for ppc, arm, mips, mips-el. Booted on powerpc
    MPC8641HPCN.

    Signed-off-by: Becky Bruce

    Becky Bruce
     

21 May, 2008

1 commit

  • 53677ef18   Big white-space cleanup. ... Browse Code »

    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
     

18 Apr, 2008

1 commit

13 Jan, 2008

1 commit

  • 64134f011   Fix linker scripts: add NOLOAD atribute to .bss/.sbss sections ... Browse Code »
    20

    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
     

01 Nov, 2007

1 commit

  • 882ae4127   ppc4xx: Rework of 4xx serial driver (2) ... Browse Code »

    Change all linker scripts to reference the changed driver name 4xx_uart.o.

    Note: In most cased all these explicit referencing of these object files
    in the linker scripts is not neccessary. Only for manually embedded
    environment into the U-Boot image, which is not done is most cases.

    Signed-off-by: Stefan Roese

    Stefan Roese
     

09 Oct, 2006

1 commit

02 Sep, 2006

1 commit

  • f93286397   Add support for a saving build objects in a separate directory. ... Browse Code »

    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

12 Dec, 2005

1 commit

13 Oct, 2005

1 commit

31 Aug, 2005

1 commit

17 Aug, 2005

1 commit

10 Jan, 2005

1 commit