On Mon, Apr 04, 2011 at 08:58:11AM -0600, Bjorn Helgaas wrote: > I think your ExpressCard contains two devices: the Express-to-PCI bridge and > the 1394 controller itself, which is behind the bridge. When you plug it in, > we discover the devices: > > [ 501.714858] pci 0000:02:00.0: PCI bridge to [bus 03-ff] > [ 501.714942] pci 0000:02:00.0: bridge window [io > 0x0000-0x0000] (disabled) > [ 501.715065] pci 0000:02:00.0: bridge window [mem > 0x00000000-0x000fffff] (disabled) > [ 501.715176] pci 0000:02:00.0: bridge window [mem > 0x00000000-0x000fffff pref] (disabled) > [ 501.713371] pci 0000:03:00.0: reg 10: [mem 0x00000000-0x000007ff] > [ 501.713473] pci 0000:03:00.0: reg 14: [mem 0x00000000-0x00003fff] > > Then we attempt to assign resources to them. The Express-to-PCI bridge is on > bus 02, so we need space there, but the BIOS didn't assign anything for bus 02: > > [ 0.137841] pci 0000:00:05.0: PCI bridge to [bus 02-04] > [ 0.137934] pci 0000:00:05.0: bridge window [io > 0x0000-0x0000] (disabled) > [ 0.137939] pci 0000:00:05.0: bridge window [mem > 0x00000000-0x000fffff] (disabled) > [ 0.137944] pci 0000:00:05.0: bridge window [mem > 0xfff00000-0x000fffff pref] (disabled) > > Theoretically, we could reassign the 00:05.0 windows to make space on bus 02, > then open a 02:00.0 window, then assign the 03:00.0 resources. But I don't > think Linux is smart enough to do this yet. > > Ram Pai and Yinghai Lu have been working on this, but we don't have a clean > solution yet. Bjorn, You see issues with Yinghai's patch reworked and sent last month ? http://marc.info/?l=linux-pci&m=129963301009100&w=2 RP -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
