On Tue, Dec 1, 2015 at 1:23 PM, Khalid Aziz <khalid.a...@oracle.com> wrote: > The device does work with this patch.
Good. > Doesn't this warning mean BAR6 > resources could not be reserved which means the device driver may not be > able to get the BAR6 resource at some point if another device grabs the > unreserved resource? Current sparc pci only have checking, does not have assign unassigned bar from firmware. because firmware does not assign resource to that BAR6, the driver may not need that bar at all. > > David M had pointed out an issue with how OF driver uses the same address > range for all ROMs enabling them only one at a time. That seems to be in > play here in the issue I am seeing. Does this patch series need to address > this? That trick may have problem when we have devices under bridge. as bridge window need to be setup at first. If the driver really need to use that trick, it should borrow from BAR0 (MEM) instead. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
