summaryrefslogtreecommitdiff
path: root/cpu/arm920t/ks8695
diff options
context:
space:
mode:
authorAnton Vorontsov <avorontsov@ru.mvista.com>2009-02-19 18:20:42 +0300
committerKim Phillips <kim.phillips@freescale.com>2009-02-23 15:51:35 -0600
commite2d72ba543c7b6924b5b5d393dcd80b2b9c3a022 (patch)
treebf9d46b39325671535f40bbedd89f466621b9a62 /cpu/arm920t/ks8695
parentcc2a8c7751ddbae3116660064f446888538b93e9 (diff)
downloadu-boot-imx-e2d72ba543c7b6924b5b5d393dcd80b2b9c3a022.zip
u-boot-imx-e2d72ba543c7b6924b5b5d393dcd80b2b9c3a022.tar.gz
u-boot-imx-e2d72ba543c7b6924b5b5d393dcd80b2b9c3a022.tar.bz2
mpc83xx: PCIe: Don't start bus enumeration at 0
Currently we assign first_busno = 0 for the first PCIe hose, but this scheme won't work if we have ordinary PCI hose already registered (its first_busno value is 0 too). The old code worked fine only because we have PCI disabled on MPC837XEMDS boards in stand-alone mode (see commit 00f7bbae92e3b13f2b3 "mpc83xx: fix PCI scan hang on the standalone MPC837xE-MDS boards"). But on MPC837XERDB boards we have PCI and PCIe, so the bug actually triggers. So, to fix the issue, we should use pci_last_busno() + 1 for the first_busno (i.e. last available busno). Reported-by: Huang Changming <Chang-Ming.Huang@freescale.com> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com> Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
Diffstat (limited to 'cpu/arm920t/ks8695')
0 files changed, 0 insertions, 0 deletions