29 Nov, 2010
6 commits
-
Signed-off-by: Wolfgang Denk
-
commit ec50a8e389863ac35bfd9d9a2e8b30187318e59e
"cfi_flash: handle 'chip size exceeds address window' situation"
added 3rd argument to flash_get_size() but didn't fix all the
function calls from the board specific code. Many boards have
their own flash_get_size() definitions in the board code and
use them there, but some boards (e.g. tqm834x, tqm85xx, pdm360ng)
use flash_get_size() from the cfi_flash.c driver.The bug shows up if the value of the "max_size" argument (which
is not defined when calling the function with two arguments)
happens to be less than "info->size". In this case on the
affected boards we end up with a bank of reduced size and
in the worst case might even be not able to update U-Boot or
to boot the kernel from flash:=> fli
Bank # 1: CFI conformant FLASH (32 x 16) Size: 0 kB in 1 Sectors
AMD Standard command set, Manufacturer ID: 0x01, Device ID: 0x227E
Erase timeout: 4096 ms, write timeout: 1 ms
Buffer write timeout: 3 ms, buffer size: 64 bytesSector Start Addresses:
F0000000 ROBank # 2: CFI conformant FLASH (32 x 16) Size: 128 MB in 512 Sectors
AMD Standard command set, Manufacturer ID: 0x01, Device ID: 0x227E
Erase timeout: 4096 ms, write timeout: 1 ms
Buffer write timeout: 3 ms, buffer size: 64 bytesSector Start Addresses:
F8000000 F8040000 F8080000 F80C0000 F8100000
F8140000 F8180000 F81C0000 F8200000 F8240000
...E.g., updating U-Boot is not possible now:
=> protect off ${u-boot_addr} +${u-boot_size}
Error: end address (0xf007ffff) not in flash!
Bad address format
=> era ${u-boot_addr} +${u-boot_size}
Error: end address (0xf007ffff) not in flash!
Bad address formatThis patch removes the 3rd argument of flash_get_size() again
and sets "max_size" in the function itself instead of passing
it as a function argument.Signed-off-by: Anatolij Gustschin
-
Fix for ARM Relocation support
Signed-off-by: Sandeep Paulraj
-
Fix for ARM Relocation support
Signed-off-by: Sandeep Paulraj
-
Fix for ARM Relocation support
Signed-off-by: Sandeep Paulraj
28 Nov, 2010
26 commits
-
Fix compiler warning
fdt_support.c: In function 'of_bus_default_count_cells':
fdt_support.c:957: warning: passing argument 1 of '__swab32p' discards qualifiers from pointer target type
fdt_support.c:965: warning: passing argument 1 of '__swab32p' discards qualifiers from pointer target typebe32_to_cpup() expects an 'u32 *' while prop is 'const u32 *'.
Signed-off-by: Dirk Behme
-
This patch fixes the issue by defining and using
CONFIG_SYS_INIT_RAM_SIZE and CONFIG_SYS_INIT_RAM_ADDR.This patch adopts the
commit 31bfcf1c5776df3d90286aa15104c45096d53dc6
from Steve Sakoman and Sandeep Paulraj on Devkit8000.Signed-off-by: Thomas Weber
-
When the cache is enabled in SDRAM we need to flush not only the global
data area but also the bd_info struct in relocate_code. This patch now
flushed the complete dcache (all dcache lines) via flush_dcache() instead
of adding a flush_dcache_range() call for bd_info since this is faster.Signed-off-by: Stefan Roese
-
This patch fixes a problem in the Denali (440EPx) SDRAM ECC POST test.
When cache is enabled in the SDRAM area, the values written to SDRAM
need to be flushed from cache to SDRAM using the dcfb instruction.Without this patch the POST ECC test failed. Now its working again on
platforms with cache enabled in SDRAM.Signed-off-by: Stefan Roese
-
Signed-off-by: Wolfgang Denk
-
Use the return value of cmd_usage instead of ignoring this
and returning a 1.Signed-off-by: Thomas Weber
Acked-by: Mike Frysinger -
Use the return value of cmd_usage instead of ignoring this
and returning a 1.Signed-off-by: Thomas Weber
Acked-by: Mike Frysinger -
Use the return value of cmd_usage instead of ignoring this
and returning a 1.Signed-off-by: Thomas Weber
Acked-by: Mike Frysinger -
Guard strchr/strlen from being called with NULL pointer.
This line is crashing when command "env" is called without subcommand.The cmd is NULL in this case because the calling function "do_env"
decremented the argc without checking if there are still arguments available.Signed-off-by: Thomas Weber
-
The env command needs one subcommand. If this is not available
print the usage help.Signed-off-by: Thomas Weber
-
update suggested sort command in comment to produce desired order
suggest use of "column -t" to reformatSigned-off-by: Eric Cooper
-
* Fix memory initialization. This fixes the problem
with kernel oopses during heavy load.* Cleanup pinsetup, which for reference is among
other things needed for proper flash erasing.Signed-off-by: Kristoffer Ericson
-
Signed-off-by: Wolfgang Denk
Acked-by: Stefan Roese -
Signed-off-by: Wolfgang Denk
Acked-by: Stefan Roese -
Signed-off-by: Wolfgang Denk
Acked-by: Stefan Roese -
Signed-off-by: Wolfgang Denk
Acked-by: Stefan Roese -
Signed-off-by: Wolfgang Denk
Acked-by: Stefan Roese -
Signed-off-by: Wolfgang Denk
Cc: Anatolij Gustschin
Cc: Timur Tabi
Acked-by: Stefan Roese -
Signed-off-by: Wolfgang Denk
Acked-by: Stefan Roese -
Signed-off-by: Wolfgang Denk
Acked-by: Stefan Roese -
Signed-off-by: Wolfgang Denk
Cc: Kumar Gala
Acked-by: Stefan Roese -
Signed-off-by: Wolfgang Denk
Cc: Kim Phillips
Cc: Haiying Wang -
This is needed for the canyonlands_nand build target. Without it
the resulting image won't fit into 4k.Signed-off-by: Stefan Roese
Cc: Scott Wood
Acked-by: Scott Wood
Acked-by: Stefan Roese -
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 -
The switch from archive libraries to partial linking has introduced a
number of problems, that are non-trivial to solve. For example, it is
no longer possible to include individual object files in the linker
script as we did before for example in the case of boards with
embedded environment to fill up the gap caused by the need to align
the environment on flash erase block boundaries.The best (but unfortunately not easiest) approach to address this
problem is to enable -ffunction-sections (and -fdata-sections) so
we can again (and even in much finer granularity) place certain code
where we want it. When doing this step, it seems only consequent to
also add --gc-sections which has the added benefit of reducing the
memory footprint of the U-Boot image (both in flash and in RAM).Unfortunately, this requires changes to a lot of linker scripts.
Signed-off-by: Wolfgang Denk
Cc: Stefan Roese
Cc: Kim Phillips
Cc: Andy Fleming
Cc: Kumar Gala
Acked-by: Stefan Roese -
Apply the same fix for 83xx as was done for 85xx in commit
96196a1f7546904563994d2d041804a816d7c139.Without this, NAND SPLs are built with the text base intended for the main
image, resulting in a broken, very large u-boot-nand.bin.The block of defines for NAND boot is moved closer to where
CONFIG_SYS_TEXT_BASE is defined. We can't directly use
CONFIG_SYS_NAND_U_BOOT_DST in the definition of CONFIG_SYS_TEXT_BASE because
autoconf.mk will include the literal text "CONFIG_SYS_NAND_U_BOOT_DST",
but at least keep them close and point out that they're supposed to be
the same.Signed-off-by: Scott Wood
27 Nov, 2010
8 commits
-
This change is needed to compile the PPC4xx NAND booting targets
equipped with the IBM DDR2 SDRAM controller.Signed-off-by: Stefan Roese
Cc: Wolfgang Denk
Acked-by: Stefan Roese -
These boards use an embedded environment, which is not supported by the
generic arch/powerpc/cpu/ppc4xx/u-boot.lds script.The breakage was introduced by commit 2cd95a2 "ppc4xx: Remove board
specific linker scripts from most PPC4xx boards"Signed-off-by: Wolfgang Denk
Cc: Stefan Roese
Cc: Andrea Marson
Acked-by: Stefan Roese -
As we try to get rid of board specific config.mk files we must
provide a way for board specific settings of the LDSCRIPT variable
(path to the linker script) where needed.We now implement the following hierarchy:
- Highest priority has a "#define CONFIG_SYS_LDCONFIG" in the board
config file.
- If CONFIG_SYS_LDCONFIG is not set, and the system is booting from
NAND (CONFIG_NAND_SPL is set), then a board specific linker
script board/$(BOARDDIR)/u-boot-nand.lds gets used.
- If we are not booting from NAND, we test if a processor specific
linker script arch/powerpc/cpu/$(CPU)/u-boot.lds exists; if so we
use that.
- As default, arch/powerpc/config.mk gets used.Signed-off-by: Wolfgang Denk
Cc: Stefan Roese
Cc: Kim Phillips
Cc: Kumar Gala
Cc: Andy Fleming
Acked-by: Stefan Roese -
Signed-off-by: Wolfgang Denk
Cc: Stefan Roese
Acked-by: Stefan Roese -
Some boards use an embedded environment, where env_embedded.o has to
be linked at a special position in the U-Boot image; to make this
possible, we do not include it into libcommon.o for such boards.Signed-off-by: Mike Frysinger
Signed-off-by: Wolfgang Denk
Acked-by: Stefan Roese -
Fix warnings:
cam5200_flash.c: In function 'write_word_32':
cam5200_flash.c:443: warning: dereferencing type-punned pointer will break strict-aliasing rules
cam5200_flash.c: In function 'write_word_16':
cam5200_flash.c:684: warning: dereferencing type-punned pointer will break strict-aliasing rulesSigned-off-by: Wolfgang Denk
Acked-by: Stefan Roese -
So far, only the BAB7xx board would call the initialise_w83c553f()
function for the WINBOND 83C553 chip, even though some other boards
(HIDDEN_DRAGON, Sandpoint8240, Sandpoint8245) enabled it in their
board configuration. These boards were also missing other config
settings needed for that, which resulted in build errors like this:drivers/pci/libpci.o:(.got2+0x84): undefined reference to `ide_bus_offset'
Switch arch/powerpc/lib/board.c to call initialise_w83c553f() not on a
per-board base, but when a WINBOND_83C553 in enabled in a
configuration (like BAB7xx), and disable it in the boards that had
this set so far.Signed-off-by: Wolfgang Denk
Cc: Yusdi Santoso
Cc: Jim Thompson
Acked-by: Stefan Roese -
The IDS8247 board is configured to use the CFI flash driver, so drop
the now redundant custom flash.c file.Signed-off-by: Wolfgang Denk
Acked-by: Stefan Roese