aboutsummaryrefslogtreecommitdiff
path: root/slof
diff options
context:
space:
mode:
authorNikunj A Dadhania <nikunj@linux.vnet.ibm.com>2014-05-14 15:39:24 +0530
committerNikunj A Dadhania <nikunj@linux.vnet.ibm.com>2014-05-14 15:39:24 +0530
commit7cc0b6c5ce87549ba7bc396bfca1018c076a7351 (patch)
tree0d8415e0756767cf53788cf7bd609c6bf346e2d8 /slof
parent37808183708d32f69461f0bf6a2bf2118f756413 (diff)
downloadSLOF-7cc0b6c5ce87549ba7bc396bfca1018c076a7351.zip
SLOF-7cc0b6c5ce87549ba7bc396bfca1018c076a7351.tar.gz
SLOF-7cc0b6c5ce87549ba7bc396bfca1018c076a7351.tar.bz2
pci-bridge: Fix ranges when no device beyond the bridge
Before starting pci-bridge probing the ranges property is set to the max limit, and then pci bridge is probed. Once the probe is over we would update the ranges property. In case when there is no device beyond the bridge, ranges will be null and the code moves ahead. The actual problem here is that before probing the bridge the ranges property was set to max limit. That stays and cause overlapping ranges for sibling devices. So empty the ranges property for this bridge when there is no device present. Signed-off-by: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Diffstat (limited to 'slof')
-rw-r--r--slof/fs/pci-properties.fs1
1 files changed, 1 insertions, 0 deletions
diff --git a/slof/fs/pci-properties.fs b/slof/fs/pci-properties.fs
index f88a571..da1d4fc 100644
--- a/slof/fs/pci-properties.fs
+++ b/slof/fs/pci-properties.fs
@@ -410,6 +410,7 @@
dup IF \ IF any space present (propsize>0)
s" ranges" property \ | write it into the device tree
ELSE \ ELSE
+ s" " s" ranges" property
2drop \ | forget the properties
THEN \ FI
drop \ forget the address