From: Clemens Ladisch <clemens@ladisch.de>
To: alsa-devel@alsa-project.org
Cc: alsa-devel@vger.kernel.org
Subject: Re: [alsa-devel] Tascam US-122L - Corrupt USB descriptor
Date: Wed, 13 Apr 2016 11:01:20 +0200 [thread overview]
Message-ID: <570E0AE0.3020507@ladisch.de> (raw)
In-Reply-To: <3d5a5368f3a43ffc0114daf09c306d7e.squirrel@mungewell.org>
Simon Wood wrote:
> I have been struggling for the past few days to get a Tascam US-122L (USB
> sound-card/midi interface) working, despite reading numerous forum
> postings I have only been able to get the midi portion working.
Does it show up with "aplay -l"?
> I note that the USB descriptor seems to be corrupt. It declares 2
> interfaces, but then describes 3 separate with the same interface number
> for the last 2.
The descriptors describe two alternate settings for the same interface.
This is a feature, which is required for audio devices.
> iManufacturer 1 (error) <------ Here be Errors!
> iProduct 2 (error)
> iSerial 3 (error)
It's possible that lsusb does not have the permissions needed to send
the messages to ask for the strings. Try running it as root.
Regards,
Clemens
--
To unsubscribe from this list: send the line "unsubscribe alsa-devel" in
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2016-04-13 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 6:38 [alsa-devel] Tascam US-122L - Corrupt USB descriptor Simon Wood
2016-04-13 9:01 ` Clemens Ladisch
2016-04-13 9:01 ` Clemens Ladisch [this message]
2016-04-13 14:08 ` Simon Wood
2016-04-13 14:08 ` [alsa-devel] " Simon Wood
2016-04-14 7:35 ` Clemens Ladisch
2016-04-14 16:20 ` Simon Wood
2016-04-14 17:10 ` Clemens Ladisch
2016-04-14 17:10 ` Clemens Ladisch
2016-04-14 16:20 ` Simon Wood
2016-04-14 7:35 ` Clemens Ladisch
2016-04-13 9:02 ` Ricard Wanderlof
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=570E0AE0.3020507@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.