summaryrefslogtreecommitdiffstats
path: root/drivers/pci/access.c
diff options
context:
space:
mode:
authorYinghai Lu <yinghai@kernel.org>2011-05-12 17:11:37 -0700
committerJesse Barnes <jbarnes@virtuousgeek.org>2011-05-21 12:17:11 -0700
commitda7822e5ad71ec9b745b412639f1e5e0ba795a20 (patch)
tree605722e2c2b32fd6450bc91718ac7b4240fcba6c /drivers/pci/access.c
parentf8fcfd775523347afe460dc3a0f45d0479e784a2 (diff)
downloadblackbird-op-linux-da7822e5ad71ec9b745b412639f1e5e0ba795a20.tar.gz
blackbird-op-linux-da7822e5ad71ec9b745b412639f1e5e0ba795a20.zip
PCI: update bridge resources to get more big ranges when allocating space (again)
With Ram's fixes, this should be safe to do again. So let's give it another try. BIOS separates IO ranges between several IOHs, and on some slots, BIOS assigns resources to a bridge, but stops assigning resources to the device under that bridge, because the device needs a big resource. So: 1. allocate resources and record the failed device resources 2. clear the BIOS assigned resources of the parent bridge of failing device 3. go back and call pci assign unassigned 4. if it still fails, go up the tree, clear more bridges. and try again Now Ram's allocate requested resource already got into mainline. could put this one again. Reviewed-by: Ram Pai <linuxram@us.ibm.com> Signed-off-by: Yinghai Lu <yinghai@kernel.org> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'drivers/pci/access.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud