From: Daniel Mack <zonque@gmail.com>
To: "jovanovic.ljubomir@t-online.de" <jovanovic.ljubomir@t-online.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: US Robotics USB Phone
Date: Mon, 30 Jul 2012 16:20:06 +0200 [thread overview]
Message-ID: <50169816.8030806@gmail.com> (raw)
In-Reply-To: <1Svqhn-2C1hzM0@fwd25.aul.t-online.de>
On 30.07.2012 16:12, jovanovic.ljubomir@t-online.de wrote:
> The file is attached :-)
>
> Phone works (under winxp) without any driver (speaker and
> microphone), but driver is needed for buttons...
The device is missing in this lsusb output. I guess you copied only the
visible part of terminal window, and the important pieces have scrolled
away. Run "lsusb >lsusb.txt" and then send the file "lsusb.txt".
Daniel
next prev parent reply other threads:[~2012-07-30 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 14:12 US Robotics USB Phone jovanovic.ljubomir
2012-07-30 14:20 ` Daniel Mack [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-30 22:07 jovanovic.ljubomir
2012-07-30 10:49 jovanovic.ljubomir
2012-07-30 10:52 ` Daniel Mack
2012-07-30 8:18 jovanovic.ljubomir
2012-07-30 8:21 ` Daniel Mack
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=50169816.8030806@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=jovanovic.ljubomir@t-online.de \
/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;
as well as URLs for NNTP newsgroup(s).