Hi Willy, Willy Tarreau <w@xxxxxx> writes: >> > I don't know if it should have included FL1009, it was just a guess, >> > based on the fact that the 0x1000 and 0x1400 devices did need MSI >> > disabled. I can attempt to ask the Fresco Logic folks I know, but I'm >> > not sure if/when I'll get a response back. >> > >> > That still doesn't necessarily rule out MSI issues in the Marvell PCI >> > host controller code. Can you attach another PCI device with MSI >> > support under the host and see if it works? >> >> The various Armada-based devices I have are NAS which do not have PCIe >> slots to plug additional devices (everything is soldered). I don't know >> which device Thomas used for its tests. Just in case, I also added Willy >> in CC: who have various boards and may also have done more test with >> additional PCIe devices and CONFIG_PCI_MSI enabled on 3.13 kernel. > > I've been running an intel i350 dual-port NIC (igb driver) supporting > MSI on the mirabox, and it used to work in 3.10+many of the patches > coming from the Free-electrons team. Some recent changes to the PCI > code introduced a regression preventing this driver from correctly > registering an MSI interrupt, and I did not have enough time to > investigate it deep enough to fix it. That said, I know how to hack > it to work again, so if it can be of any use, I can run a test on > the mirabox (armada370) and on the XPGP board (armadaXP). Thanks for the proposal, Willy. I guess Thomas can tell better than me what kind of tests would help ruling out a problem in MSI support and put the blame on FL chip ;-) Thomas, if you need me to test something on some of my platforms, do not hesitate. Cheers, a+ -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
