On Fri, Sep 28, 2012 at 05:00:19PM +0200, Jurriaan wrote: > Hi, Hi Jurriaan, > I'm writing you because you're mentioned as the writer of the etxhci > module. This module is included in the firmware of the Qnap TS-119 P II > single-bas NAS. It's a Marvell Kirkwood based device, and the original > kernel includes these messages when booting: I wrote the xhci-hcd driver in the mainline kernel. It seems that Qnap renamed the driver to etxhci in their firmware, and probably renamed all the functions from xhci* to etxhci*. Since you found my copyright information in their driver, I assume they have provided the source code for it? I didn't see a link to the driver anywhere, but I assume it's just a kernel dump, and not anything useful like patches or a git history of their changes. > [ 29.900000] usbhid: USB HID core driver > [ 29.930000] usbcore: registered new interface driver usblp > [ 29.950000] sysinfo: Module loaded. > [ 30.030000] etxhci_hcd_120712 0000:01:01.0: Etron xHCI Host Controller > [ 30.040000] etxhci_hcd_120712 0000:01:01.0: new USB bus registered, > assigned bus number 2 > [ 30.040000] etxhci_hcd_120712 0000:01:01.0: irq 10, io mem 0xe8000000 > [ 30.050000] etxhci_hcd_120712 0000:01:01.0: Failed to enable MSI-X > [ 30.060000] etxhci_hcd_120712 0000:01:01.0: failed to allocate MSI > entry > [ 30.060000] usb usb2: config 1 interface 0 altsetting 0 endpoint 0x81 > has no SuperSpeed companion descriptor > [ 30.120000] xHCI etxhci_add_endpoint called for root hub > [ 30.120000] xHCI etxhci_check_bandwidth called for root hub > [ 30.120000] ethub 2-0:1.0: USB hub found > [ 30.120000] ethub 2-0:1.0: 4 ports detected > > A vanilla kernel, I've tried 3.6.0-rc7, doesn't detect anything about > this USB3 controller at all. I have the device connected via a serial > console, so I'm able to test new kernels and I can recover when a > compiled kernel stops it booting. What I don't have is any clue as to > where to start. They may not have the Etron xHCI host linked as a PCI device. Perhaps their kernel adds it as a platform driver with the recent CONFIG_XHCI_PLATFORM config option? Wait, no, that can't be right, because you're seeing MSI-X and MSI failure messages, so it must be under PCI. But there's got to be some changes to the PCI enumeration code or something else to make that Etron PCI host actually work. Good luck digging that change log out of their custom kernel. > More on the situation can be read here: > > http://forum.qnap.com/viewtopic.php?f=147&t=61716&sid=3bfe2b23783256a0c97c1e2eb71917ff > > Could you perhaps provide some pointers as to where I can start to debug > this? I did read on your blog that the etxhci driver should have been > integrated into 2.6.31, but it's just not found without Qnap's own > kernel. It's really up to Qnap to get their kernel changes committed in mainline. They're just another example of an embedded vendor throwing a custom kernel over the wall, and it's going to be painful for everyone involved to get their board working on the mainline kernel. If you want to try and debug this, I'm happy to accept any patches you (or Qnap) send. But I don't have much hope of getting anything useful out of Qnap. Sarah Sharp -- 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
