linux-kernel - USB3 ports on Qnap TS-119 P II (arm, kirkwood, feroceon)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 1 Oct 2012 15:11:31 +0200
From:	jurriaan_lkml@...ierenland.xs4all.nl
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: USB3 ports on Qnap TS-119 P II (arm, kirkwood, feroceon)

I have a newer revision of Qnap's TS-119 P II single-bay nas. It runs an
armv5te Feroceon cpu. The older revision runs on linux 3.6-rc7 just
fine. The newer revision has usb3 ports at the back instead of usb2, and
these are not detected. lspci and lsusb detect nothing.
/sys/bus/pci/devices is empty.

Qnap provides sources for their kernel - 2.6.33.2 with lots of patches.
The usb3 ports are detected by an etxhci driver. The author of this
file, Sarah Sharp, points at pci initialization code as the likely
culprit.

The fact that Qnap's 2.6.33.2 kernel has 8800 Kb of drivers under
arch/arm/plat-feroceon that don't exist in vanilla linux agrees with
this.

Now I'm at a loss as to how to proceed. Transplanting this entire tree
under the new kernel and getting it to compile might be possible, but
vanilla linux cares about more hardware than just Qnap, and I have not
enough knowledge to determine if different Feroceon platforms are
different enough to need different drivers. I could also start upgrading
the Qnap tree with 2.6.34, 2.6.35 etc. taking small steps. 

It might also be that judicious tweaking of some PCI things (signatures?
locations?) might be enough to support these USB3 ports. 

Some more information is posted at

http://forum.qnap.com/viewtopic.php?f=147&t=61716&p=290123

including dmesg output etc.

I would really like someone experienced in either arm or pci or both to
point me at what to do next.

Thanks,
Jurriaan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/