From: "K.A." <deb.lists@gmail.com>
To: alsa-devel@lists.sourceforge.net
Subject: Snd-usb-audio and usb-phones.
Date: Fri, 20 Oct 2006 11:36:57 +0300 [thread overview]
Message-ID: <20061020083657.GA8792@localhost> (raw)
On Fri, Oct 20, 2006 at 10:08:59AM +0300, akbara wrote:
On Tue, Oct 17, 2006 at 09:57:33AM +0300, akbara wrote:
Hello, Takashi!
I bought a noname usb ip-phone. So when plugging it in, your driver
snd-usb-audio is used. So I decided to ask whether you know if drivers
for such devices exist.
The problem is that the phone is found as an audio device, it uses
the hiddev96 driver, but I can't hear any sound when trying to call to
my Skype contact -- only noise, and crack, and flicks while the call is
processing.
So, my question is: do any drivers for such devices exist? And -- what
can I look for?
Distro -- Debian Etch, 2.6.18 (vanilla).
After plugging in the phone:
-----------------------------------------------------------------
dmesg:
usb 2-2: new full speed USB device using uhci_hcd and address 2
usb 2-2: configuration #1 chosen from 1 choice
2:1:1: cannot get freq at ep 0x2
2:2:1: cannot get freq at ep 0x82
usbcore: registered new driver snd-usb-audio
usbcore: registered new driver hiddev
hiddev96: USB HID v2.01 Device [BUILDWIN SKYPE PHONE] on usb-0000:00:1d.0-2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
usb 2-2: USB disconnect, address 2
usb 2-2: new full speed USB device using uhci_hcd and address 3
usb 2-2: configuration #1 chosen from 1 choice
3:1:1: cannot get freq at ep 0x2
3:2:1: cannot get freq at ep 0x82
hiddev96: USB HID v2.01 Device [BUILDWIN SKYPE PHONE] on usb-0000:00:1d.0-2
---------------------------------------------------------------------------
lsmod | grep usb
usbhid 41856 0
snd_usb_audio 78000 0
snd_usb_lib 17944 1 snd_usb_audio
snd_rawmidi 26016 1 snd_usb_lib
snd_pcm 82860 5 snd_usb_audio,snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss
usbcore 137420 6 usbhid,snd_usb_audio,snd_usb_lib,uhci_hcd,ehci_hcd
------------------------------------------------------------------------------------
lsusb:
Bus 003 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 003: ID 1908:1389
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
-------------------------------------------------------------------------
Is the problem only in special drivers from the vendor?
--
К.А.,
enfant terrible.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next reply other threads:[~2006-10-20 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 8:36 K.A. [this message]
2006-10-20 9:36 ` Snd-usb-audio and usb-phones Markus Rechberger
2006-10-21 14:28 ` K.A.
2006-10-20 9:53 ` Clemens Ladisch
2006-10-20 10:52 ` Markus Rechberger
2006-10-20 12:59 ` Takashi Iwai
2006-10-21 14:29 ` K.A.
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=20061020083657.GA8792@localhost \
--to=deb.lists@gmail.com \
--cc=alsa-devel@lists.sourceforge.net \
/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