- 29 10月, 2008 5 次提交
-
-
由 Scott Wood 提交于
This brings the core NAND code up to date with the Linux kernel. Since there were several drivers in Linux as of the last update that are not in u-boot, I'm not bringing over new drivers that have been added since in the absence of an interested party. I did not update OneNAND since it was recently synced by Kyungmin Park, and I'm not sure exactly what the common ancestor is. Signed-off-by: NScott Wood <scottwood@freescale.com>
-
由 Kumar Gala 提交于
Added the ability to config out bootm support for Linux, NetBSD, RTEMS Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
-
由 Kumar Gala 提交于
Add support for 'bdt', 'cmdline', 'prep' to the linux PPC bootm. Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
-
由 Kumar Gala 提交于
Add the ability to break the steps of the bootm command into several subcommands: start, loados, ramdisk, fdt, bdt, cmdline, prep, go. This allows us to do things like manipulate device trees before they are passed to a booting kernel or setup memory for a secondary core in multicore situations. Not all OS types support all subcommands (currently only start, loados, ramdisk, fdt, and go are supported). Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
-
由 Kumar Gala 提交于
This removes a bit of code and makes it easier for the upcoming sub bootm command support to call into the proper OS specific handler. Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NWolfgang Denk <wd@denx.de>
-
- 28 10月, 2008 7 次提交
-
-
-
由 Graeme Russ 提交于
Renamed show_boot_progress in assembler init phase to show_boot_progress_asm to avoid link conflicts with C version Signed-off-by: NGraeme Russ <graeme.russ@gmail.com>
-
由 Andy Fleming 提交于
-
由 Peter Tyser 提交于
The MPC8572 has a 4-bit wide PORDEVSR IO_SEL field. Other MPC85xx processors have a 3-bit wide IO_SEL field but have the most significant bit is wired to 0 so this change should not affect them. Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>
-
-
由 Becky Bruce 提交于
The existing code has a few errors that need to be fixed in order to support large RAM sizes. Fix those, and add a comment to make it clearer. Signed-off-by: NBecky Bruce <becky.bruce@freescale.com> Acked-by: NKumar Gala <galak@kernel.crashing.org>
-
由 Kumar Gala 提交于
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
-
- 27 10月, 2008 1 次提交
-
-
由 Haavard Skinnemoen 提交于
The information displayed when CONFIG_LCD_INFO is set is inherently board-specific, so it should be done by the board code. The current code dealing with this only handles two cases, and is already a horrible mess of #ifdeffery. Yes, this duplicates some code, but it also allows boards to print more board-specific information; this used to be very difficult. Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com> Signed-off-by: NAnatolij Gustschin <agust@denx.de>
-
- 26 10月, 2008 4 次提交
-
-
由 Haavard Skinnemoen 提交于
This allows the logo/info rendering routines to use the regular lcd_putc/lcd_puts/lcd_printf calls. Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com> Signed-off-by: NAnatolij Gustschin <agust@denx.de>
-
由 Haavard Skinnemoen 提交于
lcd_printf() has a prototype in include/lcd.h but no implementation. Fix this by borrowing the lcd_printf() implementation from the cogent board code (which appears to use its own LCD framework.) Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com> Signed-off-by: NAnatolij Gustschin <agust@denx.de>
-
由 Haavard Skinnemoen 提交于
If the board _didn't_ request INVLINE_INVERTED, we set INVLINE_INVERTED, otherwise we don't. WTF? Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com> Signed-off-by: NAnatolij Gustschin <agust@denx.de>
-
由 Haavard Skinnemoen 提交于
atmel_lcdfb doesn't actually need anything from asm/arch/hardware.h. It includes a file that does, asm/arch/gpio.h, but this file doesn't include <asm/arch/hardware.h> like it's supposed to. Add the missing include to asm/arch/gpio.h and remove the workaround from the atmel_lcdfb driver. This makes the driver compile on avr32. Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com> Signed-off-by: NAnatolij Gustschin <agust@denx.de>
-
- 25 10月, 2008 14 次提交
-
-
由 Kumar Gala 提交于
Converted MPC8610HCPD, MPC8641HPCN, and SBC8641D to use fsl_pci_setup_inbound_windows() and ft_fsl_pci_setup(). With these changes the board code is a bit smaller and we get dma-ranges set in the device tree for these boards. Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NAndrew Fleming-AFLEMING <afleming@freescale.com> Acked-by: NJon Loeliger <jdl@freescale.com>
-
由 Kumar Gala 提交于
Converted ATUM8548, MPC8536DS, MPC8544DS, MPC8548CDS, MPC8568MDS, MPC8572DS, TQM85xx, and SBC8548 to use fsl_pci_setup_inbound_windows() and ft_fsl_pci_setup(). With these changes the board code is a bit smaller and we get dma-ranges set in the device tree for these boards. Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NAndrew Fleming-AFLEMING <afleming@freescale.com>
-
由 Kumar Gala 提交于
Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NAndrew Fleming-AFLEMING <afleming@freescale.com>
-
由 Kumar Gala 提交于
Add a common setup function that determines the pci_region(s) based on how much memory we have in the system. Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NAndrew Fleming-AFLEMING <afleming@freescale.com>
-
由 Kumar Gala 提交于
* PCI Inbound window was setup incorrectly. The PCI address and system address were swapped. The PCI address should be setting piwar/piwbear and the system address should be setting pitar. * Removed masking of addresses to allow for system address to support system address & PCI address >32-bits * Set PIWBEAR & POTEAR to allow for full 64-bit PCI addresses * Respect the PCI_REGION_PREFETCH for inbound windows Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NAndrew Fleming-AFLEMING <afleming@freescale.com>
-
由 Kumar Gala 提交于
Added fdt_pci_dma_ranges() that parses the pci_region info from the struct pci_controller and populates the dma-ranges based on it. The max # of windws/dma-ranges we support is 3 since on embedded PowerPC based systems this is the max number of windows. Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NAndrew Fleming-AFLEMING <afleming@freescale.com>
-
由 Kumar Gala 提交于
Add helper functions to return find a node and return it's property or a default value. Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NAndrew Fleming-AFLEMING <afleming@freescale.com> Acked-by: NGerald Van Baren <vanbaren@cideas.com>
-
由 Kumar Gala 提交于
Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NAndrew Fleming-AFLEMING <afleming@freescale.com>
-
由 Kumar Gala 提交于
Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NAndrew Fleming-AFLEMING <afleming@freescale.com>
-
由 Kumar Gala 提交于
PCI bus is inherently 64-bit. While not all system require access to the full 64-bit PCI address range some do. This allows those systems to enable the full PCI address width via CONFIG_SYS_PCI_64BIT. Signed-off-by: NKumar Gala <galak@kernel.crashing.org> Signed-off-by: NAndrew Fleming-AFLEMING <afleming@freescale.com> Acked-by: NWolfgang Denk <wd@denx.de>
-
由 Dave Liu 提交于
The 8572 DDR erratum1: DDR controller may enter an illegal state when operating in 32-bit bus mode with 4-beat bursts. Description: When operating with a 32-bit bus, it is recommended that DDR_SDRAM_CFG[8_BE] is cleared when DDR2 memories are used. This forces the DDR controller to use 4-beat bursts when communicating to the DRAMs. However, an issue exists that could lead to data corruption when the DDR controller is in 32-bit bus mode while using 4-beat bursts. Projected Impact: If the DDR controller is operating in 32-bit bus mode with 4-beat bursts, then the controller may enter into a bad state. All subsequent reads from memory is corrupted. Four-beat bursts with a 32-bit bus only is used with DDR2 memories. Therefore, this erratum does not affect DDR3 mode. Work Arounds: To work around this issue, software must set DEBUG_1[31] in DDR memory mapped space (CCSRBAR offset + 0x2f00 for DDR_1 and CCSRBAR offset + 0x6f00 for DDR_2). Currenlty, the code is using incorrect register DDR_SDRAM_CFG_2 as condition, but it should be DDR_SDRAM_CFG register. Signed-off-by: NDave Liu <daveliu@freescale.com>
-
由 Dave Liu 提交于
Signed-off-by: NDave Liu <daveliu@freescale.com>
-
由 Kumar Gala 提交于
Introduce CONFIG_E500MC to deal with the minor differences between e500v2 and e500mc. * Certain fields of HID0/1 don't exist anymore on e500mc * Cache line size is 64-bytes on e500mc * reset value of PIR is different Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
-
由 Kumar Gala 提交于
Using CONFIG_SYS_CACHELINE_SIZE instead of 31 means we can handle e500mc's 64-byte cacheline properly when it gets added. Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
-
- 24 10月, 2008 3 次提交
-
-
由 Georg Schardt 提交于
This patch adds support for the avnet fx12 minimodul. It needs the "ppc4xx: Generic architecture for xilinx ppc405" patch from Ricardo. Signed-off-by: NGeorg Schardt <schardt@team-ctech.de> Signed-off-by: NRicardo Ribalda Delgado <ricardo.ribalda@uam.es> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Ricardo Ribalda Delgado 提交于
As "ppc44x: Unification of virtex5 pp440 boards" did for the xilinx ppc440 boards, this patch presents a common architecture for all the xilinx ppc405 boards. Any custom xilinx ppc405 board can be added very easily with no code duplicity. This patch also adds a simple generic board, that can be used on almost any design with xilinx ppc405 replacing the file ppc405-generic/xparameters.h This patch is prepared to work with the latest version of EDK (10.1) Signed-off-by: NRicardo Ribalda Delgado <ricardo.ribalda@uam.es> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Stefan Roese 提交于
Since the new autocalibration still has some problems on some Kilauea boards with 200MHz DDR2 frequency we disable the autocalibration and use the hardcoded values as done before. This seems to work reliably on all known DDR2 frequencies. After the autocalibration issue is fixed we will enable it again. Signed-off-by: NStefan Roese <sr@denx.de>
-
- 22 10月, 2008 6 次提交
-
-
由 Wolfgang Denk 提交于
Signed-off-by: NWolfgang Denk <wd@denx.de>
-
由 Richard Retanubun 提交于
This is done to allow other 83XX based platforms which also have UPM (e.g. 8360) to configure and use their UPM in u-boot. Signed-off-by: NRichard Retanubun <RichardRetanubun@RuggedCom.com> Signed-off-by: NKim Phillips <kim.phillips@freescale.com>
-
由 Anton Vorontsov 提交于
With this patch u-boot can fixup the dr_mode and phy_type properties for the Dual-Role USB controller. While at it, also remove #ifdefs around includes, they are not needed. Signed-off-by: NAnton Vorontsov <avorontsov@ru.mvista.com> Signed-off-by: NKim Phillips <kim.phillips@freescale.com>
-
由 Anton Vorontsov 提交于
Though NAND chip is replaceable on the MPC837XE-MDS boards, the current settings don't work with the default chip on the board. Nevertheless Freescale's U-Boot sets the option register correctly, so I just dumped the register from the working u-boot. My guess is that the old settings were applicable for some pilot boards, not found in the production. This patch also enables FSL ELBC driver so that we could access the NAND storage in the u-boot. The NAND support costs about 45KB, so the u-boot no longer fits into two 128KB NOR flash sectors, thus we also have to adjust environment location: add another 128KB to the monitor length. Signed-off-by: NAnton Vorontsov <avorontsov@ru.mvista.com> It is due to hardware design and logic defect, that is the I/O[0:7] of NAND chip is connected to LAD[7:0], so when the NAND chip connected to nLCS3, you have to set up the OR3[BCTLD] = '1' for normal operation, otherwise it will have bus contention due to the pin 48/25 of U60 is enabled. Setup the OR3[BCTLD] = '1' , that meaning the LBCTL is not asserted upon access to the NAND chip, keep the default state. Acked-by: NDave Liu <daveliu@freescale.com> Signed-off-by: NKim Phillips <kim.phillips@freescale.com>
-
由 Anton Vorontsov 提交于
The MPC837xE-MDS board's CPLD can auto-detect if the board is on the PIB, standalone or acting as a PCI agent. User's Guide says: - When the CPLD recognizes its location on the PIB it automatically configures RCW to the PCI Host. - If the CPLD fails to recognize its location then it is automatically configured as an Agent and the PCI is configured to an external arbiter. This sounds good. Though in the standalone setup the CPLD sets PCI_HOST flag (it's ok, we can't act as PCI agents since we receive CLKIN, not PCICLK), but the CPLD doesn't set the ARBITER_ENABLE flag, and without any arbiter bad things will happen (here the board hangs during any config space reads). In this situation we must disable the PCI. And in case of anybody really want to use an external arbiter, we provide "pci_external_aribter" environment variable. Signed-off-by: NAnton Vorontsov <avorontsov@ru.mvista.com> Signed-off-by: NKim Phillips <kim.phillips@freescale.com>
-
由 Anton Vorontsov 提交于
This involves configuring the SerDes and fixing up the flags and PHY addresses for the TSECs. For Linux we also fix up the device tree. Signed-off-by: NAnton Vorontsov <avorontsov@ru.mvista.com> Signed-off-by: NKim Phillips <kim.phillips@freescale.com>
-