summaryrefslogtreecommitdiff
path: root/board/atmel
Commit message (Collapse)AuthorAgeLines
...
* Merge branch '080202_at91rm9200dk' of git://linux-arm.org/u-boot-armdevPeter Pearse2008-02-15-0/+869
|\
| * Move AT91RM9200DK board support under board/atmelHaavard Skinnemoen2008-02-14-0/+869
| | | | | | | | | | | | We already have a vendor subdir for Atmel, so we should use it. Signed-off-by: Haavard Skinnemoen <hskinnemoen <at> atmel.com>
* | Merge branch '080116_at91cap9' of git://linux-arm.org/u-boot-armdevPeter Pearse2008-02-15-0/+542
|\ \
| * | AT91CAP9 support : move board files to Atmel vendor directory.Stelian Pop2008-02-14-0/+542
| |/ | | | | | | | | | | AT91CAP9 support : move at91cap9adk board files to Atmel vendor directory. Signed-off-by: Stelian Pop <stelian@popies.net>
* | AVR32: Make SDRAM refresh rate configurableHaavard Skinnemoen2008-02-05-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The existing code assumes the SDRAM row refresh period should always be 15.6 us. This is not always true, and indeed on the ATNGW100, the refresh rate should really be 7.81 us. Add a refresh_period member to struct sdram_info and initialize it properly for both ATSTK1000 and ATNGW100. Out-of-tree boards will panic() until the refresh_period member is updated properly. Big thanks to Gerhard Berghofer for pointing out this issue. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
* | ATSTK1000: Fix potential flash programming bugHaavard Skinnemoen2008-02-05-9/+22
|/ | | | | | | | | The (now obsolete) atngw100 flash programming code was having problems programming the onboard at49bv642 chip. The atstk1000 flash programming code may have the same bug, so import fix for this problem from the AVR32 Linux BSP. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
* AVR32: ATNGW100 board supportHaavard Skinnemoen2008-01-18-0/+232
| | | | | | | Add support for the ATNGW100 Network Gateway reference design, including flash, ethernet and MMC support. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
* Fix linker scripts: add NOLOAD atribute to .bss/.sbss sectionsWolfgang Denk2008-01-12-1/+1
| | | | | | | | | | | | | | | | | | | 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 <wd@denx.de>
* AVR32: Initialize bi_flash* in board_init_rHaavard Skinnemoen2007-10-06-4/+0
| | | | | | | | | | | The ATSTK1000-specific flash driver intializes bi_flashstart, bi_flashsize and bi_flashoffset, but other flash drivers, like the CFI driver, don't. Initialize these in board_init_r instead so that things will still be set up correctly when we switch to the CFI driver. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
* board/[A-Za-c]*: Remove obsolete references to CONFIG_COMMANDSJon Loeliger2007-07-09-1/+1
| | | | Signed-off-by: Jon Loeliger <jdl@freescale.com>
* board/[Ma-i]*: Augment CONFIG_COMMANDS tests with defined(CONFIG_CMD_*).Jon Loeliger2007-07-04-1/+1
| | | | | | | | | | | | | | This is a compatibility step that allows both the older form and the new form to co-exist for a while until the older can be removed entirely. All transformations are of the form: Before: #if (CONFIG_COMMANDS & CFG_CMD_AUTOSCRIPT) After: #if (CONFIG_COMMANDS & CFG_CMD_AUTOSCRIPT) || defined(CONFIG_CMD_AUTOSCRIPT) Signed-off-by: Jon Loeliger <jdl@freescale.com>
* AVR32: Enable MMC supportHaavard Skinnemoen2007-04-14-0/+3
| | | | | | | Set up the portmux for the MMC interface and enable the MMC driver along with support for DOS partitions, ext2 and FAT filesystems. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
* AVR32: Enable networkingHaavard Skinnemoen2007-04-14-1/+43
| | | | | | | Implement MACB initialization for AVR32 and ATSTK1000, and turn everything on, including the MACB driver. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
* AVR32: Use initdram() instead of board_init_memories()Haavard Skinnemoen2007-04-14-2/+2
| | | | | | | | Conform to the "standard" interface and use initdram() instead of board_init_memories() on AVR32. This enables us to get rid of the sdram_size member of the global_data struct as well. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
* AVR32: Relocate u-boot to SDRAMHaavard Skinnemoen2007-04-14-10/+13
| | | | | | | Relocate the u-boot image into SDRAM like everyone else does. This means that we can handle much larger .data and .bss than we used to. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
* AVR32: Resource management rewriteHaavard Skinnemoen2007-04-14-0/+13
| | | | | | | | | | | | | Rewrite the resource management code (i.e. I/O memory, clock gating, gpio) so it doesn't depend on any global state. This is necessary because this code is heavily used before relocation to RAM, so we can't write to any global variables. As an added bonus, this makes u-boot's memory footprint a bit smaller, although some functionality has been left out; all clocks are enabled all the time, and there's no checking for gpio line conflicts. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
* Fix "ar" flags in some Makefiles to allow for silent "make -s"Wolfgang Denk2006-10-27-1/+1
|
* Finish up support for the ATSTK1000/ATSTK1002 boardsHaavard Skinnemoen2006-10-25-6/+4
| | | | | | | | | | | | Add atstk1002_config target to Makefile and move the AVR32 section down below Blackfin so that it doesn't end up in the middle of MIPS. Drop the autogenerated linker script thing for now. Will have to revisit how to handle chips with different flash and RAM layout later. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
* Move atstk1000 files into vendor specific directory.Wolfgang Denk2006-10-24-0/+402
Patch by Haavard Skinnemoen, 12 Sep 2006