- Dec 22, 2010
-
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
- Dec 21, 2010
-
-
John Rigby authored
It can be optimised out by the compiler otherwise resulting in obscure errors like a board not booting. This has been documented in README since 2006 when these were first fixed up for GCC 4.x. Signed-off-by:
John Rigby <john.rigby@linaro.org> Fix some additional places. Signed-off-by:
Wolfgang Denk <wd@denx.de> Acked-By:
Albert ARIBAUD <albert.aribaud@free.fr>
-
- Dec 18, 2010
-
-
Wolfgang Denk authored
-
Dirk Behme authored
Convert the variable omap3_evm_version to u32 to work around some broken linkers from older tool chains. E.g. CodeSourcery's 2009q1-203 ld 2.19.51.20090205. Without this, these linkers stop linking 'omap3_evm' or at least issue a warning. Like arm-none-linux-gnueabi-ld: section .bss [8003f5e0 -> 8007e337] overlaps section .rel.dyn [8003f5e0 -> 80044e57] arm-none-linux-gnueabi-ld: section .dynsym [80044e58 -> 80044ef7] overlaps section.bss [8003f5e0 -> 8007e337] arm-none-linux-gnueabi-ld: u-boot: section .bss vma 0x8003f5e0 overlaps previous sections CC: Sanjeev Premi <premi@ti.com> Signed-off-by:
Dirk Behme <dirk.behme@googlemail.com>
-
Li Yang authored
The current code use all the voltage range support by the host controller to do the validation. This will cause problem when the host supports Low Voltage Range. Change the validation voltage to be based on board setup. Signed-off-by:
Li Yang <leoli@freescale.com> Tested-by:
Stefano Babic <sbabic@denx.de> Signed-off-by:
Kumar Gala <galak@kernel.crashing.org>
-
Jerry Huang authored
The max clock of MMC is 52MHz Signed-off-by:
Jerry Huang <Changm-Ming.Huang@freescale.com> Tested-by:
Stefano Babic <sbabic@denx.de> Signed-off-by:
Kumar Gala <galak@kernel.crashing.org>
-
Jerry Huang authored
After booting the u-boot, and first using some SD card (such as Sandisk 2G SD card), because the field 'clock' of struct mmc is zero, this will cause the read transfer is always active and SDHC DATA line is always active, therefore, driver can't handle the next command. Therefore, we use mmc_set_clock to setup both the data structure and HW to the initial clock speed of 400000Hz. Signed-off-by:
Jerry Huang <Chang-Ming.Huang@freescale.com> Tested-by:
Stefano Babic <sbabic@denx.de> Signed-off-by:
Kumar Gala <galak@kernel.crashing.org>
-
Li Yang authored
The current code use all the voltage range support by the host controller to do the validation. This will cause problem when the host supports Low Voltage Range. Change the validation voltage to be based on board setup. Signed-off-by:
Li Yang <leoli@freescale.com> Tested-by:
Stefano Babic <sbabic@denx.de> Signed-off-by:
Kumar Gala <galak@kernel.crashing.org>
-
Jerry Huang authored
The max clock of MMC is 52MHz Signed-off-by:
Jerry Huang <Changm-Ming.Huang@freescale.com> Tested-by:
Stefano Babic <sbabic@denx.de> Signed-off-by:
Kumar Gala <galak@kernel.crashing.org>
-
Jerry Huang authored
After booting the u-boot, and first using some SD card (such as Sandisk 2G SD card), because the field 'clock' of struct mmc is zero, this will cause the read transfer is always active and SDHC DATA line is always active, therefore, driver can't handle the next command. Therefore, we use mmc_set_clock to setup both the data structure and HW to the initial clock speed of 400000Hz. Signed-off-by:
Jerry Huang <Chang-Ming.Huang@freescale.com> Tested-by:
Stefano Babic <sbabic@denx.de> Signed-off-by:
Kumar Gala <galak@kernel.crashing.org>
-
- Dec 17, 2010
-
-
Stefano Babic authored
Fix clock divider for COM57H5M10XRC display. The previous setting caused flicker. Tested on Qong (EVBLite with COM57H5M10XRC). Signed-off-by:
Stefano Babic <sbabic@denx.de> Acked-by:
Wolfgang Denk <wd@denx.de> Acked-by:
Anatolij Gustschin <agust@denx.de>
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Sandeep Paulraj authored
Add ARM Relocation Support Signed-off-by:
Sandeep Paulraj <s-paulraj@ti.com>
-
Sandeep Paulraj authored
Add ARM Relocation Support Signed-off-by:
Sandeep Paulraj <s-paulraj@ti.com>
-
Sandeep Paulraj authored
Add ARM Relocation Support Signed-off-by:
Sandeep Paulraj <s-paulraj@ti.com>
-
Sandeep Paulraj authored
Add ARM Relocation Support Signed-off-by:
Sandeep Paulraj <s-paulraj@ti.com>
-
Sandeep Paulraj authored
Some DaVinci boards are using flags that are no longer valid So remove them. Signed-off-by:
Sandeep Paulraj <s-paulraj@ti.com>
-
clagix@gmail.com authored
Signed-off-by:
Guido Classen <clagix@gmail.com> Signed-off-by:
Reinhard Meyer <u-boot@emk-elektronik.de>
-
Reinhard Meyer authored
Signed-off-by:
Reinhard Meyer <u-boot@emk-elektronik.de>
-
- Dec 16, 2010
-
-
Asen Dimov authored
Signed-off-by:
Asen Dimov <dimov@ronetix.at>
-
Asen Dimov authored
Signed-off-by:
Asen Dimov <dimov@ronetix.at>
-
Asen Dimov authored
Signed-off-by:
Asen Dimov <dimov@ronetix.at>
-
Asen Dimov authored
Signed-off-by:
Asen Dimov <dimov@ronetix.at>
-
Asen Dimov authored
Signed-off-by:
Asen Dimov <dimov@ronetix.at>
-
Asen Dimov authored
Signed-off-by:
Asen Dimov <dimov@ronetix.at>
-
Scott Wood authored
Recent GCC (4.4+) performs out-of-line epilogues in some cases, when optimizing for size. It causes a link error for _restgpr_30_x (and similar) if libgcc is not linked. It actually increases size with very small binaries, due to the fixed size of the out-of-line code, and not having any functions that actually need to restore more than 2 or 3 registers. But I don't see a way to turn it off, other than asking GCC to optimize for speed -- which may also increase size for some boards. Signed-off-by:
Scott Wood <scottwood@freescale.com> Acked-by:
Kim Phillips <kim.phillips@freescale.com> Acked-by:
Wolfgang Denk <wd@denx.de>
- Dec 15, 2010
-
-
Stefan Roese authored
This patch fixes the acadia_nand and kilauea_nand linker scripts which have been missing in commit ee8028b7 [ppc4xx: Cleanup for partial linking and --gc-sections] Signed-off-by:
Stefan Roese <sr@denx.de> Cc: Bernhard Weirich <Bernhard.Weirich@riedel.net>
-
- Dec 13, 2010
-
-
Wolfgang Denk authored
Make code build with older tool chains. Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Baidu Boy authored
This patch fix a problem for the pcie enumeration for mpc83xx cpus. Without this we will not get correct value in hose->regions[...]. The pointer *reg in function mpc83xx_pcie_init_bus() shall not be changed. Because we will use this pointer as a parameter to call function mpc83xx_pcie_register_hose(). Signed-off-by:
Baidu Boy <liucai.lfn@gmail.com> Signed-off-by:
Kim Phillips <kim.phillips@freescale.com>
-
Timur Tabi authored
On the P1022, the pins which drive the video display (DIU) are muxed with the local bus controller (LBC), so if the DIU is active, the pins need to be temporarily muxed to LBC whenever accessing NOR flash. The code which handled this transition is checking and changing the wrong bits in PMUXCR. Also add a follow-up read after a write to NOR flash if we're going to mux back to DIU after the write, as described in the P1022 RM. Signed-off-by:
Timur Tabi <timur@freescale.com> Signed-off-by:
Kumar Gala <galak@kernel.crashing.org>
-
P.V.Suresh authored
eSDHC host controller reset results in clearing of snoop bit also. This patch sets the SNOOP bit after the completion of host controller reset. Without this patch mmc reads are not consistent. Signed-off-by:
P.V.Suresh <pala@freescale.com> Signed-off-by:
Kumar Gala <galak@kernel.crashing.org>
-
John Schmoller authored
According to Freescale reference manuals (eg section "13.4.4.2 Programming the UPMs" of the P4080 Reference Manual): "Since the result of any update to the MxMR/MDR register must be in effect before the dummy read or write to the UPM region, a write to MxMR/MDR should be followed immediately by a read of MxMR/MDR." The UPM on a custom P4080-based board did not work without performing a read of MxMR/MDR after a write. Signed-off-by:
John Schmoller <jschmoller@xes-inc.com> Signed-off-by:
Peter Tyser <ptyser@xes-inc.com> Acked-by:
Scott Wood <scottwood@freescale.com> Signed-off-by:
Kumar Gala <galak@kernel.crashing.org>