summaryrefslogtreecommitdiff
path: root/cpu/mpc85xx/start.S
diff options
context:
space:
mode:
authorKumar Gala <galak@kernel.crashing.org>2007-10-11 00:29:18 -0500
committerAndrew Fleming-AFLEMING <afleming@freescale.com>2007-10-19 11:25:01 -0500
commit7600d47b8f6a10019e537dc9a62aa1498df58d25 (patch)
treedec36ca966862046717914f9b5c0319eaa5e4b51 /cpu/mpc85xx/start.S
parenta3063eec775719b7e91023bbec3f64b3118791df (diff)
downloadu-boot-imx-7600d47b8f6a10019e537dc9a62aa1498df58d25.zip
u-boot-imx-7600d47b8f6a10019e537dc9a62aa1498df58d25.tar.gz
u-boot-imx-7600d47b8f6a10019e537dc9a62aa1498df58d25.tar.bz2
Improve handling of PCI interrupt device tree fixup on MPC85xx CDS
On the MPC85xx CDS we have two issues: 1. The device tree fixup code did not check to see if the property we are trying to update is actually found. Its possible that it would update random memory starting at 0. 2. Newer Linux kernel's have moved the location of the PCI nodes to be sibilings of the soc node and not children. The explicit PATH to the PCI node would not be found for these device trees. Add the ability to handle both paths. In the future we shouldn't handle such fixups by explicit path. Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'cpu/mpc85xx/start.S')
0 files changed, 0 insertions, 0 deletions