summaryrefslogtreecommitdiffstats
path: root/init/Kconfig
diff options
context:
space:
mode:
authorMark A. Greer <mgreer@mvista.com>2007-05-12 10:54:05 +1000
committerPaul Mackerras <paulus@samba.org>2007-05-12 11:32:49 +1000
commit0f81b11d2a14adaa9b2c944f104e13d72fedc769 (patch)
tree027a2753d7e98a131091b2699888b53eea8d6e6d /init/Kconfig
parent916066d5913c37a6b3907eb6695cc9ecaaa4d8ca (diff)
downloadlinux-0f81b11d2a14adaa9b2c944f104e13d72fedc769.tar.gz
linux-0f81b11d2a14adaa9b2c944f104e13d72fedc769.tar.bz2
linux-0f81b11d2a14adaa9b2c944f104e13d72fedc769.zip
[POWERPC] Add bootwrapper support for Marvell/mv64x60 hostbridge
The mv64x60 host bridge has many windows between its various components (cpu, system memory, ethernet ctlr, MPSC, DMA ctlr, PCI MEM, PCI I/O). Unfortunately, the firmware on some of mv64x60-based platforms do not properly or completely configure those windows (e.g., MPSC->system memory windows not configured or CPU->PCI MEM space not configured). So, the missing configuration needs to be done in either the bootwrapper or in the kernel. To keep the kernel as clean as possible, it is done in the bootwrapper. Note that I/O controller configuration is NOT being done, its only the windows to allow the I/O controllers and other components to access memory, etc. that is being done--drivers assume that their controllers can already access system memory). Table of routines and the windows they configure: mv64x60_config_ctlr_windows() ENET->System Memory MPSC->System Memory IDMA->System Memory mv64x60_config_pci_windows() PCI MEM->System Memory PCI I/O->Bridge's Registers mv64x60_config_cpu2pci_window() CPU->PCI MEM CPU->PCI I/O Signed-off-by: Mark A. Greer <mgreer@mvista.com> Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'init/Kconfig')
0 files changed, 0 insertions, 0 deletions