The SnapStream Firefly Mini
(http://www.snapstream.com/products/fireflymini/) is an infrared remote
control, really a composite USB HID Keyboard/Consumer device,
vendor:device => 1233:e007.
The HID Keyboard portion works flawlessly however a couple of the events
from the USB Consumer page are missing from hid-input.c. The patch to
2.6.19.2 below makes all the buttons work.
Best Regards,
Simon
--- a/drivers/usb/input/hid-input.c 2006-09-19 20:42:06.000000000 -0700
+++ b/drivers/usb/input/hid-input.c 2006-12-31 14:26:00.000000000 -0800
@@ -403,9 +403,12 @@ static void hidinput_configure_usage(str
case 0x000: goto ignore;
case 0x034:
map_key_clear(KEY_SLEEP); break;
case 0x036:
map_key_clear(BTN_MISC); break;
+ case 0x040:
map_key_clear(KEY_MENU); break;
case 0x045:
map_key_clear(KEY_RADIO); break;
case 0x08a:
map_key_clear(KEY_WWW); break;
+ case 0x083:
map_key_clear(KEY_LAST); break;
case 0x08d:
map_key_clear(KEY_PROGRAM); break;
+ case 0x09a:
map_key_clear(KEY_PVR); break;
case 0x095:
map_key_clear(KEY_HELP); break;
case 0x09c:
map_key_clear(KEY_CHANNELUP); break;
case 0x09d:
map_key_clear(KEY_CHANNELDOWN); break;
@@ -426,10 +429,12 @@ static void hidinput_configure_usage(str
case 0x0ea:
map_key_clear(KEY_VOLUMEDOWN); break;
case 0x183:
map_key_clear(KEY_CONFIG); break;
case 0x18a:
map_key_clear(KEY_MAIL); break;
+ case 0x18e:
map_key_clear(KEY_CALENDAR); break;
case 0x192:
map_key_clear(KEY_CALC); break;
case 0x194:
map_key_clear(KEY_FILE); break;
case 0x1a7:
map_key_clear(KEY_DOCUMENTS); break;
case 0x201:
map_key_clear(KEY_NEW); break;
+ case 0x203:
map_key_clear(KEY_CLOSE); break;
case 0x207:
map_key_clear(KEY_SAVE); break;
case 0x208:
map_key_clear(KEY_PRINT); break;
case 0x209:
map_key_clear(KEY_PROPS); break;
[EMAIL PROTECTED] wrote:
>Send linux-usb-devel mailing list submissions to
> linux-usb-devel@lists.sourceforge.net
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
>or, via email, send a message with subject or body 'help' to
> [EMAIL PROTECTED]
>
>You can reach the person managing the list at
> [EMAIL PROTECTED]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of linux-usb-devel digest..."
>
>
>Today's Topics:
>
> 1. Re: Fw: usb error messages (Vasudevan S)
> 2. Re: [PATCH 0/3] race fixes for usb-serial (Pete Zaitcev)
> 3. Re: Fw: usb error messages (Alan Stern)
> 4. Re: Fw: usb error messages (Jon Smirl)
> 5. Re: Fw: usb error messages (David Brownell)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri, 12 Jan 2007 10:43:21 -0800
>From: "Vasudevan S" <[EMAIL PROTECTED]>
>Subject: Re: [linux-usb-devel] Fw: usb error messages
>To: "Alan Stern" <[EMAIL PROTECTED]>
>Cc: Andrew Morton <[EMAIL PROTECTED]>, USB development list
> <linux-usb-devel@lists.sourceforge.net>
>Message-ID:
> <[EMAIL PROTECTED]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Hello Alan,
>
>
>
>>Possibly this error is caused by your initrd. It should load ehci-hcd
>>before uhci-hcd, not after.
>>
>>
>
>Yes, it is the problem. After I reversed the order in initrd, the
>"device not accepting"
>error no longer appears (when I shutdown the box and then reboot).
>
>Thanks much.
>
>
>
>>>If I just restart the machine instead of shutdown, I see one more usb error:
>>> usb 5-1.2: device descriptor read/64, error -32
>>>
>>>which would appear like some reset/close operation wasn't done in the
>>>restart.
>>>
>>>
>>Again, if the message appears only once then you can ignore it. Restart
>>does re-initialize all USB devices.
>>
>>
>
>Restart still shows this 'device descriptor' error, though.
>
>
>
>>The 'suspend-to-disk' (using 'swsusp'/'software suspend 2') are not
>>
>>
>>>working on this laptop and I am thinking these errors might be
>>>contributing to the problem.
>>>
>>>
>>I doubt that very much. But if you want anybody to help solve the swsusp
>>problem then you have to post a dmesg log showing what goes wrong when you
>>try to do it.
>>
>>
>
>Ok, you may be right here as well.
>
>When I start the hibernation using 'swsusp', I see the following
>messages on the console:
>[ I cannot paste the contents to a file when this happens, so sending
>excerpts..]
>
>[I have also enabled the PM debug messages in the config]
>"
>Shrinking memory
>swsusp: Need to copy 108345 pages
>swsusp: critical region/: done (108345 pages copied)
>swsusp: Restoring Highmem
>
>PCI: Enabling device 0000:00:1d.7 (0000 -> 0002)
>usb usb1: root hub lost power or was reset
> usbdev1.2_ep00: PM: resume from 0, parent 1-1 still 1
>
>[followed by the similar usb messages, but for different hubs]
>"
>
>Today, I decided to wait for some time after seeing these messages.
>Then the console started spitting the following messages:
>"
> sd 0:0:0:0: timing out command, waited 360s
>end_request: I/O error, dev sda, sector 152121693
>Read-error on swap-device (253:1:24)
>"
>
>So, it may not really be the 'usb' problem, but rather something to do
>with this 'sd' driver or even the sata driver.?
>
>Also, when I try to power down the box when this happens, I also see
>an ACPI error:
>
>ACPI error (evevent-0314): No installed handler for fixed event
>[00000002] [20060707]
>
>Perhaps, I should forward all this to the 'linux-kernel' list?
>
>Thanks,
>--Vasu
>
>
>
>------------------------------
>
>Message: 2
>Date: Fri, 12 Jan 2007 10:48:31 -0800
>From: Pete Zaitcev <[EMAIL PROTECTED]>
>Subject: Re: [linux-usb-devel] [PATCH 0/3] race fixes for usb-serial
>To: Oliver Neukum <[EMAIL PROTECTED]>
>Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
> linux-usb-devel@lists.sourceforge.net, [EMAIL PROTECTED]
>Message-ID: <[EMAIL PROTECTED]>
>Content-Type: text/plain; charset=US-ASCII
>
>On Fri, 12 Jan 2007 15:58:04 +0100 (MET), Oliver Neukum <[EMAIL PROTECTED]>
>wrote:
>
>
>
>>"J" and I discovered some races in usb-serial, this series fixes some of
>>them. "J" has made additional patches that fix some more races.
>>I haven't tested this due to lack of hardware. I consider this material
>>for 2.4.21. []
>>
>>
>
>I mean to look this over but between this and that there's no time.
>I hope to get to it when I'm back from Australia.
>
>The patches seem to be for 2.6 series and not 2.4. BTW, I wrestled with
>much the same issues in 2.4, so it has a substantial fork now. Oh well.
>
>You what will really throw wrench into your works? Try to configure
>getty on the ttyUSB0. This is how you get ->write method called on a
>real interrupt context when low latency is set. Even PPP bounces interrupts
>to a softirq, so you can't test for lock recursion without getty.
>
>Later,
>-- Pete
>
>
>
>------------------------------
>
>Message: 3
>Date: Fri, 12 Jan 2007 14:11:27 -0500 (EST)
>From: Alan Stern <[EMAIL PROTECTED]>
>Subject: Re: [linux-usb-devel] Fw: usb error messages
>To: Vasudevan S <[EMAIL PROTECTED]>
>Cc: Andrew Morton <[EMAIL PROTECTED]>, USB development list
> <linux-usb-devel@lists.sourceforge.net>
>Message-ID:
> <[EMAIL PROTECTED]>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>On Fri, 12 Jan 2007, Vasudevan S wrote:
>
>
>
>>>>If I just restart the machine instead of shutdown, I see one more usb error:
>>>> usb 5-1.2: device descriptor read/64, error -32
>>>>
>>>>which would appear like some reset/close operation wasn't done in the
>>>>restart.
>>>>
>>>>
>>>Again, if the message appears only once then you can ignore it. Restart
>>>does re-initialize all USB devices.
>>>
>>>
>>Restart still shows this 'device descriptor' error, though.
>>
>>
>
>It appears that the device itself is failing to initialize correctly.
>It's hard to say anything more definite since you haven't provided any
>more log messages.
>
>
>
>>>The 'suspend-to-disk' (using 'swsusp'/'software suspend 2') are not
>>>
>>>
>>>>working on this laptop and I am thinking these errors might be
>>>>contributing to the problem.
>>>>
>>>>
>>>I doubt that very much. But if you want anybody to help solve the swsusp
>>>problem then you have to post a dmesg log showing what goes wrong when you
>>>try to do it.
>>>
>>>
>>Ok, you may be right here as well.
>>
>>When I start the hibernation using 'swsusp', I see the following
>>messages on the console:
>>[ I cannot paste the contents to a file when this happens, so sending
>>excerpts..]
>>
>>[I have also enabled the PM debug messages in the config]
>>"
>>Shrinking memory
>>swsusp: Need to copy 108345 pages
>>swsusp: critical region/: done (108345 pages copied)
>>swsusp: Restoring Highmem
>>
>>PCI: Enabling device 0000:00:1d.7 (0000 -> 0002)
>>usb usb1: root hub lost power or was reset
>> usbdev1.2_ep00: PM: resume from 0, parent 1-1 still 1
>>
>>[followed by the similar usb messages, but for different hubs]
>>"
>>
>>
>
>Those messages are normal. They indicate that the USB controllers weren't
>powered while the machine was shut off.
>
>
>
>>Today, I decided to wait for some time after seeing these messages.
>>Then the console started spitting the following messages:
>>"
>> sd 0:0:0:0: timing out command, waited 360s
>>end_request: I/O error, dev sda, sector 152121693
>>Read-error on swap-device (253:1:24)
>>"
>>
>>So, it may not really be the 'usb' problem, but rather something to do
>>with this 'sd' driver or even the sata driver.?
>>
>>
>
>I would assume it has something to do with SATA, which is a lot newer than
>sd.
>
>
>
>>Also, when I try to power down the box when this happens, I also see
>>an ACPI error:
>>
>>ACPI error (evevent-0314): No installed handler for fixed event
>>[00000002] [20060707]
>>
>>Perhaps, I should forward all this to the 'linux-kernel' list?
>>
>>
>
>Since none of your problems appear to be related to the USB stack, that
>seems like a good idea.
>
>Alan Stern
>
>
>
>
>------------------------------
>
>Message: 4
>Date: Fri, 12 Jan 2007 14:37:00 -0500
>From: "Jon Smirl" <[EMAIL PROTECTED]>
>Subject: Re: [linux-usb-devel] Fw: usb error messages
>To: "Alan Stern" <[EMAIL PROTECTED]>
>Cc: Andrew Morton <[EMAIL PROTECTED]>, USB development list
> <linux-usb-devel@lists.sourceforge.net>
>Message-ID:
> <[EMAIL PROTECTED]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>I am seeing these exact same errors on my system too, a Dell PE400SC
>alias a Dimension 8300.
>
>The PE400SC motherboard has front panel USB ports on some models. My
>machine does not have the front panel option so who knows where the
>wires from that controller are routed to. I had associated this error
>with that controller: usb 1-1: device not accepting address 2, error
>-71.
>
>I sometimes see this same error on ports that have a USB cable plugged
>in but nothing is attached to it.
>
>I had thought the read/64 errors were specific problems with the
>zd1211 device I was working on.
> [ 25.275324] usb 5-1.4: device descriptor read/64, error -110 ...: 1
> Time(s)
> [ 40.426420] usb 5-1.4: device descriptor read/64, error -110
>...: 1 Time(s)
> [ 43.669162] usb 5-1.4: device descriptor read/64, error -110
>...: 1 Time(s)
> [ 58.820261] usb 5-1.4: device descriptor read/64, error -110
>...: 1 Time(s)
> [ 69.386774] usb 5-1.4: device not accepting address 9, error
>-110 ...: 1 Time(s)
> [ 79.849569] usb 5-1.4: device not accepting address 10, error
>-110 ...: 1 Time(s)
> [ 128.717464] usb 5-1.4: rx_urb_complete() urb f7a89f40 error -71
>...: 1 Time(s)
> [ 218.524636] usb 5-1.4: rx_urb_complete() urb f7a896c0 error -71
>...: 1 Time(s)
> [ 296.118197] usb 5-1.4: device descriptor read/64, error -110
>...: 1 Time(s)
> [ 308.446584] usb 5-1.4: rx_urb_complete() urb f7a896c0 error -71
>...: 1 Time(s)
> [ 311.269423] usb 5-1.4: device descriptor read/64, error -110
>...: 1 Time(s)
> [ 314.512041] usb 5-1.4: device descriptor read/64, error -110
>...: 1 Time(s)
> [ 329.663142] usb 5-1.4: device descriptor read/64, error -110
>...: 1 Time(s)
>
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
