From: jurriaan_lkml@rivierenland.xs4all.nl
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: USB3 ports on Qnap TS-119 P II (arm, kirkwood, feroceon)
Date: Mon, 1 Oct 2012 15:11:31 +0200 [thread overview]
Message-ID: <20121001131131.GA3006@qnap.fritz.box> (raw)
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
reply other threads:[~2012-10-01 13:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121001131131.GA3006@qnap.fritz.box \
--to=jurriaan_lkml@rivierenland.xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®