07 Dec, 2011

1 commit


26 Jul, 2011

1 commit


28 Mar, 2011

1 commit


28 Oct, 2010

1 commit


20 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 Jul, 2010

1 commit

  • This patch adds support for the Voipac PXA270 board. The support includes:
    - Ethernet
    - USB
    - MMC
    - NOR Booting
    - OneNAND Booting
    - LCD
    - HDD

    Signed-off-by: Marek Vasut
    Acked-by: Scott Wood

    Marek Vasut
     

13 Apr, 2010

1 commit

  • The CPUDIR variable points to the location of a target's CPU directory.
    Currently, it is set to cpu/$CPU. However, using $CPUDIR will allow for
    more flexibility in the future. It lays the groundwork for reorganizing
    U-Boot's directory structure to support a layout such as:

    arch/$ARCH/cpu/$CPU/* (architecture with multiple CPU types)
    arch/$ARCH/cpu/* (architecture with one CPU type)

    Signed-off-by: Peter Tyser

    Peter Tyser
     

29 Sep, 2009

1 commit

  • Refactoring the OneNAND IPL code

    and some minor fixed:
    - Remove unnecessary header file
    - Fix wrong access at read interrupt
    - The recent OneNAND has 4KiB pagesize

    Also Board can override OneNAND IPL image

    Signed-off-by: Kyungmin Park

    Kyungmin Park
     

22 Aug, 2009

1 commit

  • Commit f62fb99941c6 fixed handling of all rodata sections by using a
    wildcard combined with calls to ld's builtin functions SORT_BY_ALIGNMENT()
    and SORT_BY_NAME(). Unfortunately these functions were only
    introduced with biunutils version 2.16, so the modification broke
    building with all tool chains using older binutils.

    This patch makes it work again. This is done by omitting the use of
    these functions for such old tool chains. This will result in
    slightly larger target binaries, as the rodata sections are no longer
    in optimal order alignment-wise which reauls in unused gaps, but the
    effect was found to be insignificant - especially compared to the fact
    that you cannot build U-Boot at all in the current state.

    As ld seems to have no support for conditionals we run the linker
    script through the C preprocessor which can be easily used to remove
    the unwanted function calls.

    Note that the C preprocessor must be run with the "-ansi" (or a
    "-std=") option to make sure all the system-specific predefined
    macros outside the reserved namespace are suppressed. Otherise, cpp
    might for example substitute "powerpc" to "1", thus corrupting for
    example "OUTPUT_ARCH(powerpc)" etc.

    Signed-off-by: Wolfgang Denk
    Cc: Mike Frysinger

    Wolfgang Denk
     

21 Jun, 2009

1 commit


10 Jun, 2009

1 commit


04 Apr, 2009

1 commit

  • Currently OneNAND initial program loader (ipl) reads only block 0 ie 128KB.
    However, u-boot image for apollon board is 195KB making the board
    unbootable with OneNAND.

    Fix ipl to read CONFIG_SYS_MONITOR_LEN.
    CONFIG_SYS_MONITOR_LEN macro holds the U-Boot image size.

    Signed-off-by: Rohit Hagargundgi
    Signed-off-by: Gangheyamoorthy
    Signed-off-by: Scott Wood

    apgmoorthy
     

24 Mar, 2009

1 commit

  • OneNAND IPL has common codes for RAM init, load data, and jump to 2nd
    bootloader, but it's common code used about 300~400 bytes. So board
    specific codes, such as lowlevel_init, can't has enough code. It make
    a difficult to implement OneNAND IPL.

    his patch make this common code as small as possible. and give
    lowlevel_init can have more codes.

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

    Kyungmin Park
     

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


06 Aug, 2008

1 commit


26 Mar, 2008

1 commit

  • Flex-OneNAND is a monolithic integrated circuit with a NAND Flash array
    using a NOR Flash interface. This on-chip integration enables system designers
    to reduce external system logic and use high-density NAND Flash
    in applications that would otherwise have to use more NOR components.

    Flex-OneNAND enables users to configure to partition it into SLC and MLC areas
    in more flexible way. While MLC area of Flex-OneNAND can be used to store data
    that require low reliability and high density, SLC area of Flex-OneNAND
    to store data that need high reliability and high performance. Flex-OneNAND
    can let users take advantage of storing these two different types of data
    into one chip, which is making Flex-OneNAND more cost- and space-effective.

    Signed-off-by: Kyungmin Park

    Kyungmin Park
     

15 Feb, 2008

2 commits

  • Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     
  • This patch enables the OneNAND boot within U-Boot.
    Before this work, we used another OneNAND IPL called X-Loader based
    on open source. With this work, we can build the oneboot.bin image
    without other program.

    The build sequence is simple.
    First, it compiles the u-boot.bin
    Second, it compiles OneNAND IPL
    Finally, it becomes the oneboot.bin from OneNAND IPL and u-boot.bin
    The mechanism is similar with NAND boot except it boots from itself.

    Another thing is that you can only use the OneNAND IPL only to work
    other bootloader such as RedBoot and so on.

    Signed-off-by: Kyungmin Park

    Kyungmin Park