> It sounds like these devices have some device-specific register where > BAR 0 is supposed to be? Setting IORESOURCE_PCI_FIXED doesn't seem > like the right solution to me. Even if we set that, the core still There is no actually functional register on these locations that has any side effects. > believes this resource corresponds to some address space consumed by > the device. I think we will still try to size the BAR and decode its > type. I think it will still show up via lspci. That's all > meaningless. But would actually anything use it? > How do you deal with this on Windows? > > I think you need to replace the config accessor with a special one > that knows that this register is not a BAR, and they can return zero. > Or maybe the accessor should hide these devices completely, i.e., > return 0xffffffff for the vendor/device ID. Or maybe you even have a > switch the BIOS can use to hide them from the OS. In some cases we need the devices. -Andi -- 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