Re: support for Logitech Wave

["Taneli Vähäkangas" <taneli.vahakangas@welho.com>]

Hello!

On Thu, Jan 17, 2008 at 02:07:03PM +0100, Jiri Kosina wrote:
> On Thu, 17 Jan 2008, Taneli Vähäkangas wrote:
> 
> > Thanks for prompt reply Jiri. Now I get some information for extra 
> > function keys at the top row, but still nothing for the "piano" keys. 
> 
> That's strange. Could you please try to snoop the traffic on USB, to see 
> if the keys that don't produce any HID debugging output at all at least 
> produce some USB traffic?
> 
> See Documentation/usb/usbmon.txt for details.

I did that and there are no usbmon messages at all for the "piano" keys,
so this is most likely not linux-input or HID issue.

> > Here's the output for two previously non-functioning keys:
> > Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report (size 4)
> > (numbered)
> > Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report 4 (size 3) =  02 00 00
> > Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 0
> > Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 1
> > Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 0
> > Jan 17 00:27:13 newer last message repeated 13 times
> > Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report (size 4) (numbered)
> > Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report 4 (size 3) =  00 00 00
> > Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 0
> > Jan 17 00:27:13 newer last message repeated 15 times
> 
> Hmm, this looks only like output for on key, is it really for two?

I'll check again later, I was quite confident last night that it was two
keypresses, but I was also quite tired ...

> > BTW, here's a picture of the keyboard in question ... just in case my
> > descriptions don't seem to make sense:
> > http://images.tw.creative.com/images/corporate/artwork/hires_prodikeyspcmidiusb.jpg
> 
> Could it be that the keyboard is a totally separate device? Does alsa 
> report anything, when you connect it, for example?

Unfortunately alsa notices nothing (that was also my first guess, so I
tried that even before reporting the problem here).

Could it be that hid steals the device and that's why alsa doesn't see
it?

Maybe the keyboard expects some kind of trigger from the host side to
enable the missing functionality. It apparently requires a separate
driver in windows and doesn't work in Mac OS X (that's why my sister
borrowed the keyboard to me, it didn't work with a Mac ...)

Thanks a lot for your time and responses Jiri.

Cheers,

	Taneli

-
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html