On Thu, Jul 28, 2011 at 07:28:31PM +0800, Deng-Cheng Zhu wrote: > In resolving a network driver issue with the MIPS Malta platform, the root > cause was traced into pci_claim_resource(): > > MIPS System Controller's PCI I/O resources stay in 0x1000-0xffffff. When > PCI quirks start claiming resources using request_resource_conflict(), > collisions happen and -EBUSY is returned, thereby rendering the onboard AMD > PCnet32 NIC unaware of quirks' region and preventing the NIC from functioning. > For PCI quirks, PIIX4 ACPI is expected to claim 0x1000-0x103f, and PIIX4 SMB to > claim 0x1100-0x110f, both of which fall into the MSC I/O range. Certainly, we > can increase the start point of this range in arch/mips/mti-malta/malta-pci.c to > avoid the collisions. But a fix in here looks more justified, though it seems to > have a wider impact. Using insert_xxx as opposed to request_xxx will register > PCI quirks' resources as children of MSC I/O and return OK, instead of seeing > collisions which are actually resolvable. This used to work in the past; do you know which commit broke the resource handling for the NIC? Ralf -- 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
