On Tue, Jun 30, 2009 at 10:05:20PM +0100, David Howells wrote: > Matthew Wilcox <willy@xxxxxxxxxxxxxxx> (by way of Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>) wrote: > > > Subject: [PATCH 2/3] mn10300: Use pci_claim_resource > > > > Instead of open-coding pci_find_parent_resource and request_resource, > > just call pci_claim_resource. > > Hmmm... That doesn't work. > > Without the patch, I see: > > bash-2.04# cat /proc/iomem > b8000000-bbffffff : PCI mem > b8000000-bbffffff : 0000:00:00.0 > 00000000-000fffff : 0000:00:02.0 > b8000000-b800001f : 0000:00:02.0 Ummm ... what's going on with that 00000000-000fffff nested inside b8000000-bbffffff? > bc000000-bdffffff : PCI SRAM > be040000-be0400ff : AMPCI bridge > bffffff4-bfffffff : PCI ampci > d4002010-d400201f : ttySM1 > bash-2.04# cat /proc/ioports > be000000-be03ffff : PCI IO > be030000-be03001f : 0000:00:02.0 > be030000-be03001f : pcnet32_probe_pci > d8600000-d8600007 : rtc > > With the patch, I see: > > bash-2.04# cat /proc/iomem > b8000000-bbffffff : PCI mem > b8000000-bbffffff : 0000:00:00.0 > b8000000-b80fffff : 0000:00:02.0 > b8000000-b80fffff : 0000:00:02.0 > b8000000-b80fffff : 0000:00:02.0 That really looks like the resource tree got corrupted. Nasty. -- 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
