From: Thomas Reitmayr <thomas@devbase.at>
To: Shaun Jackman <sjackman@gmail.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: USB: driver for CM109 chipset
Date: Sun, 26 Aug 2007 13:53:10 +0200 [thread overview]
Message-ID: <46D169A6.4080209@devbase.at> (raw)
In-Reply-To: <7f45d9390708252128p48c30b38we59ca2b6496997dd@mail.gmail.com>
Hi Shaun,
the CM109 VID and PID are probably not included in the kernel's
blacklisted device list (see static array hid_blacklist in hid-core.c).
Just for your tests you can write a little tool to detach the usbhid
driver and then load the cm109 module manually using modprobe or insmod.
An example for this tool (not using libusb) can be found at
http://www.devbase.at/svn/view.cgi/yealink-tools/trunk/detach-yealink.c?revision=1&root=experimental&view=markup
or inside the EEPROM tool below.
BTW, there is still the issue with varying key mappings among different
models. The EEPROM contents might give a hint for distinguishing the
models, it would be interesting if you could read the EEPROM and tell us
what you see. The tool for this task can be found at
http://www.devbase.at/svn/view.cgi/cm109-tools/trunk/?root=experimental
Regards,
-Thomas
Shaun Jackman wrote:
> I am testing your cm109 driver with my Genius G-Talk USB phone. It
> identifies itself as a cm109 device (0d8c:000e C-Media Electronics,
> Inc.). I compiled and loaded the cm109 module. However when I plug the
> phone in the, the usbhid driver grabs the device rather than the cm109
> driver. The following snippet is from /proc/bus/usb/devices and shows
> the Class/Subclass/Protocol 3/0/0 device is nabbed by the usbhid
> driver. Why isn't the cm109 driver grabbing the device?
>
> Thanks for writing the driver, and I hope I can get it to work!
> Shaun
>
> T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 7 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=0d8c ProdID=000e Rev= 1.00
> S: Product=Generic USB Audio Device
> C:* #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA
> I:* If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio
> I:* If#= 1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
> I: If#= 1 Alt= 1 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
> E: Ad=01(O) Atr=09(Isoc) MxPS= 200 Ivl=1ms
> I:* If#= 2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
> I: If#= 2 Alt= 1 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
> E: Ad=82(I) Atr=05(Isoc) MxPS= 100 Ivl=1ms
> I:* If#= 3 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
> E: Ad=83(I) Atr=03(Int.) MxPS= 4 Ivl=32ms
>
>
>
next prev parent reply other threads:[~2007-08-26 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 4:28 USB: driver for CM109 chipset Shaun Jackman
2007-08-26 11:53 ` Thomas Reitmayr [this message]
2007-08-26 16:43 ` Shaun Jackman
2007-08-26 18:51 ` Alfred E. Heggestad
2007-08-27 5:57 ` Shaun Jackman
2007-08-27 9:46 ` Jiri Kosina
[not found] ` <7f45d9390708282238w7174d105i351e81cd19037d14@mail.gmail.com>
2007-08-29 8:31 ` Jiri Kosina
2007-08-29 9:59 ` Alfred E. Heggestad
2007-08-29 10:21 ` Jiri Kosina
2007-08-29 19:37 ` Shaun Jackman
2007-08-29 23:07 ` Jiri Kosina
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=46D169A6.4080209@devbase.at \
--to=thomas@devbase.at \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=sjackman@gmail.com \
/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).