* Logitech Alto Cordless
@ 2008-12-01 13:21 Julian Sikorski
2008-12-01 16:36 ` Jiri Kosina
0 siblings, 1 reply; 7+ messages in thread
From: Julian Sikorski @ 2008-12-01 13:21 UTC (permalink / raw)
To: linux-input
Hi,
during a discussion on fedora-devel-list, I was suggested to check if
the said keyboard is compliant with the standards before requesting
xkeyboard-config changes. The problem exists with two keys:
- Fn-F3, has MSIE logo on it, emits XF86HomePage, should emit XF86WWW
- Fn-F4, has a tune on it, emit XF86Tools, should XF86AudioMedia
This is under Fedora 10 x86_64, using evdev driver and evdev-managed
keyboard map.
Regards,
Julian
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Logitech Alto Cordless
2008-12-01 13:21 Logitech Alto Cordless Julian Sikorski
@ 2008-12-01 16:36 ` Jiri Kosina
2008-12-01 16:46 ` Julian Sikorski
2008-12-01 17:54 ` Julian Sikorski
0 siblings, 2 replies; 7+ messages in thread
From: Jiri Kosina @ 2008-12-01 16:36 UTC (permalink / raw)
To: Julian Sikorski; +Cc: linux-input
On Mon, 1 Dec 2008, Julian Sikorski wrote:
> during a discussion on fedora-devel-list, I was suggested to check if
> the said keyboard is compliant with the standards before requesting
> xkeyboard-config changes. The problem exists with two keys:
> - Fn-F3, has MSIE logo on it, emits XF86HomePage, should emit XF86WWW
> - Fn-F4, has a tune on it, emit XF86Tools, should XF86AudioMedia
> This is under Fedora 10 x86_64, using evdev driver and evdev-managed
> keyboard map.
In order to answer this question, we need to know what the keyboard is
acutally sending when these keys are being pressed (and also product ID
would be useful -- this can be obtained from lsusb output).
Assuming that Fedora has the CONFIG_HID_DEBUG kernel option turned on (I
don't know whether this is true or not), could you please
rmmod usbhid
rmmod hid
modprobe hid debug=2
modprobe usbhid
press the keys, and send the dmesg output?
Thanks,
--
Jiri Kosina
SUSE Labs
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Logitech Alto Cordless
2008-12-01 16:36 ` Jiri Kosina
@ 2008-12-01 16:46 ` Julian Sikorski
2008-12-01 17:54 ` Julian Sikorski
1 sibling, 0 replies; 7+ messages in thread
From: Julian Sikorski @ 2008-12-01 16:46 UTC (permalink / raw)
To: linux-input
Jiri Kosina pisze:
> On Mon, 1 Dec 2008, Julian Sikorski wrote:
>
>> during a discussion on fedora-devel-list, I was suggested to check if
>> the said keyboard is compliant with the standards before requesting
>> xkeyboard-config changes. The problem exists with two keys:
>> - Fn-F3, has MSIE logo on it, emits XF86HomePage, should emit XF86WWW
>> - Fn-F4, has a tune on it, emit XF86Tools, should XF86AudioMedia
>> This is under Fedora 10 x86_64, using evdev driver and evdev-managed
>> keyboard map.
>
> In order to answer this question, we need to know what the keyboard is
> acutally sending when these keys are being pressed (and also product ID
> would be useful -- this can be obtained from lsusb output).
>
> Assuming that Fedora has the CONFIG_HID_DEBUG kernel option turned on (I
> don't know whether this is true or not), could you please
>
> rmmod usbhid
> rmmod hid
> modprobe hid debug=2
> modprobe usbhid
>
> press the keys, and send the dmesg output?
>
> Thanks,
>
Hmm, the option is set, but there are no such modules here...
I am running 2.6.27.5-117.fc10.x86_64 kernel. Relevant lsusb output:
Bus 001 Device 014: ID 046d:c527 Logitech, Inc.
Julian
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Logitech Alto Cordless
2008-12-01 16:36 ` Jiri Kosina
2008-12-01 16:46 ` Julian Sikorski
@ 2008-12-01 17:54 ` Julian Sikorski
2008-12-03 8:57 ` Julian Sikorski
1 sibling, 1 reply; 7+ messages in thread
From: Julian Sikorski @ 2008-12-01 17:54 UTC (permalink / raw)
To: linux-input
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
Jiri Kosina pisze:
> On Mon, 1 Dec 2008, Julian Sikorski wrote:
>
>> during a discussion on fedora-devel-list, I was suggested to check if
>> the said keyboard is compliant with the standards before requesting
>> xkeyboard-config changes. The problem exists with two keys:
>> - Fn-F3, has MSIE logo on it, emits XF86HomePage, should emit XF86WWW
>> - Fn-F4, has a tune on it, emit XF86Tools, should XF86AudioMedia
>> This is under Fedora 10 x86_64, using evdev driver and evdev-managed
>> keyboard map.
>
> In order to answer this question, we need to know what the keyboard is
> acutally sending when these keys are being pressed (and also product ID
> would be useful -- this can be obtained from lsusb output).
>
> Assuming that Fedora has the CONFIG_HID_DEBUG kernel option turned on (I
> don't know whether this is true or not), could you please
>
> rmmod usbhid
> rmmod hid
> modprobe hid debug=2
> modprobe usbhid
>
> press the keys, and send the dmesg output?
>
> Thanks,
>
OK, got it. hid is builtin.
[-- Attachment #2: dmesg.txt.zip --]
[-- Type: application/zip, Size: 5455 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Logitech Alto Cordless
2008-12-01 17:54 ` Julian Sikorski
@ 2008-12-03 8:57 ` Julian Sikorski
2008-12-16 18:37 ` Julian Sikorski
0 siblings, 1 reply; 7+ messages in thread
From: Julian Sikorski @ 2008-12-03 8:57 UTC (permalink / raw)
To: linux-input
Julian Sikorski pisze:
> Jiri Kosina pisze:
>> On Mon, 1 Dec 2008, Julian Sikorski wrote:
>>
>>> during a discussion on fedora-devel-list, I was suggested to check if
>>> the said keyboard is compliant with the standards before requesting
>>> xkeyboard-config changes. The problem exists with two keys:
>>> - Fn-F3, has MSIE logo on it, emits XF86HomePage, should emit XF86WWW
>>> - Fn-F4, has a tune on it, emit XF86Tools, should XF86AudioMedia
>>> This is under Fedora 10 x86_64, using evdev driver and evdev-managed
>>> keyboard map.
>> In order to answer this question, we need to know what the keyboard is
>> acutally sending when these keys are being pressed (and also product ID
>> would be useful -- this can be obtained from lsusb output).
>>
>> Assuming that Fedora has the CONFIG_HID_DEBUG kernel option turned on (I
>> don't know whether this is true or not), could you please
>>
>> rmmod usbhid
>> rmmod hid
>> modprobe hid debug=2
>> modprobe usbhid
>>
>> press the keys, and send the dmesg output?
>>
>> Thanks,
>>
> OK, got it. hid is builtin.
Here is what evtest reports:
Event: time 1228294575.277680, type 4 (Misc), code 4 (ScanCode), value c0223
Event: time 1228294575.277708, type 1 (Key), code 172 (HomePage), value 1
Event: time 1228294575.277716, -------------- Report Sync ------------
Event: time 1228294575.437667, type 4 (Misc), code 4 (ScanCode), value c0223
Event: time 1228294575.437692, type 1 (Key), code 172 (HomePage), value 0
Event: time 1228294575.437699, -------------- Report Sync ------------
Event: time 1228294576.165695, type 4 (Misc), code 4 (ScanCode), value c0183
Event: time 1228294576.165724, type 1 (Key), code 171 (Config), value 1
Event: time 1228294576.165732, -------------- Report Sync ------------
Event: time 1228294576.325660, type 4 (Misc), code 4 (ScanCode), value c0183
Event: time 1228294576.325690, type 1 (Key), code 171 (Config), value 0
Event: time 1228294576.325697, -------------- Report Sync ------------
Julian
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Logitech Alto Cordless
2008-12-03 8:57 ` Julian Sikorski
@ 2008-12-16 18:37 ` Julian Sikorski
2008-12-16 20:24 ` Julian Sikorski
0 siblings, 1 reply; 7+ messages in thread
From: Julian Sikorski @ 2008-12-16 18:37 UTC (permalink / raw)
To: linux-input
Julian Sikorski pisze:
> Julian Sikorski pisze:
>> Jiri Kosina pisze:
>>> On Mon, 1 Dec 2008, Julian Sikorski wrote:
>>>
>>>> during a discussion on fedora-devel-list, I was suggested to check if
>>>> the said keyboard is compliant with the standards before requesting
>>>> xkeyboard-config changes. The problem exists with two keys:
>>>> - Fn-F3, has MSIE logo on it, emits XF86HomePage, should emit XF86WWW
>>>> - Fn-F4, has a tune on it, emit XF86Tools, should XF86AudioMedia
>>>> This is under Fedora 10 x86_64, using evdev driver and evdev-managed
>>>> keyboard map.
>>> In order to answer this question, we need to know what the keyboard is
>>> acutally sending when these keys are being pressed (and also product ID
>>> would be useful -- this can be obtained from lsusb output).
>>>
>>> Assuming that Fedora has the CONFIG_HID_DEBUG kernel option turned on (I
>>> don't know whether this is true or not), could you please
>>>
>>> rmmod usbhid
>>> rmmod hid
>>> modprobe hid debug=2
>>> modprobe usbhid
>>>
>>> press the keys, and send the dmesg output?
>>>
>>> Thanks,
>>>
>> OK, got it. hid is builtin.
> Here is what evtest reports:
> Event: time 1228294575.277680, type 4 (Misc), code 4 (ScanCode), value c0223
> Event: time 1228294575.277708, type 1 (Key), code 172 (HomePage), value 1
> Event: time 1228294575.277716, -------------- Report Sync ------------
> Event: time 1228294575.437667, type 4 (Misc), code 4 (ScanCode), value c0223
> Event: time 1228294575.437692, type 1 (Key), code 172 (HomePage), value 0
> Event: time 1228294575.437699, -------------- Report Sync ------------
> Event: time 1228294576.165695, type 4 (Misc), code 4 (ScanCode), value c0183
> Event: time 1228294576.165724, type 1 (Key), code 171 (Config), value 1
> Event: time 1228294576.165732, -------------- Report Sync ------------
> Event: time 1228294576.325660, type 4 (Misc), code 4 (ScanCode), value c0183
> Event: time 1228294576.325690, type 1 (Key), code 171 (Config), value 0
> Event: time 1228294576.325697, -------------- Report Sync ------------
>
> Julian
Could somebody help me in preparation of an appropriate patch? I took a
look into drivers/hid/hid-input-quirks.c, but unfortunately that's
beyond my skills. Thanks in advance!
Regards,
Julian
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Logitech Alto Cordless
2008-12-16 18:37 ` Julian Sikorski
@ 2008-12-16 20:24 ` Julian Sikorski
0 siblings, 0 replies; 7+ messages in thread
From: Julian Sikorski @ 2008-12-16 20:24 UTC (permalink / raw)
To: linux-input
Julian Sikorski pisze:
> Julian Sikorski pisze:
>> Julian Sikorski pisze:
>>> Jiri Kosina pisze:
>>>> On Mon, 1 Dec 2008, Julian Sikorski wrote:
>>>>
>>>>> during a discussion on fedora-devel-list, I was suggested to check if
>>>>> the said keyboard is compliant with the standards before requesting
>>>>> xkeyboard-config changes. The problem exists with two keys:
>>>>> - Fn-F3, has MSIE logo on it, emits XF86HomePage, should emit XF86WWW
>>>>> - Fn-F4, has a tune on it, emit XF86Tools, should XF86AudioMedia
>>>>> This is under Fedora 10 x86_64, using evdev driver and evdev-managed
>>>>> keyboard map.
>>>> In order to answer this question, we need to know what the keyboard is
>>>> acutally sending when these keys are being pressed (and also product ID
>>>> would be useful -- this can be obtained from lsusb output).
>>>>
>>>> Assuming that Fedora has the CONFIG_HID_DEBUG kernel option turned on (I
>>>> don't know whether this is true or not), could you please
>>>>
>>>> rmmod usbhid
>>>> rmmod hid
>>>> modprobe hid debug=2
>>>> modprobe usbhid
>>>>
>>>> press the keys, and send the dmesg output?
>>>>
>>>> Thanks,
>>>>
>>> OK, got it. hid is builtin.
>> Here is what evtest reports:
>> Event: time 1228294575.277680, type 4 (Misc), code 4 (ScanCode), value c0223
>> Event: time 1228294575.277708, type 1 (Key), code 172 (HomePage), value 1
>> Event: time 1228294575.277716, -------------- Report Sync ------------
>> Event: time 1228294575.437667, type 4 (Misc), code 4 (ScanCode), value c0223
>> Event: time 1228294575.437692, type 1 (Key), code 172 (HomePage), value 0
>> Event: time 1228294575.437699, -------------- Report Sync ------------
>> Event: time 1228294576.165695, type 4 (Misc), code 4 (ScanCode), value c0183
>> Event: time 1228294576.165724, type 1 (Key), code 171 (Config), value 1
>> Event: time 1228294576.165732, -------------- Report Sync ------------
>> Event: time 1228294576.325660, type 4 (Misc), code 4 (ScanCode), value c0183
>> Event: time 1228294576.325690, type 1 (Key), code 171 (Config), value 0
>> Event: time 1228294576.325697, -------------- Report Sync ------------
>>
>> Julian
> Could somebody help me in preparation of an appropriate patch? I took a
> look into drivers/hid/hid-input-quirks.c, but unfortunately that's
> beyond my skills. Thanks in advance!
>
> Regards,
> Julian
I opened a bug at kernel bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=12238
Regards,
Julian
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2008-12-16 20:24 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-12-01 13:21 Logitech Alto Cordless Julian Sikorski
2008-12-01 16:36 ` Jiri Kosina
2008-12-01 16:46 ` Julian Sikorski
2008-12-01 17:54 ` Julian Sikorski
2008-12-03 8:57 ` Julian Sikorski
2008-12-16 18:37 ` Julian Sikorski
2008-12-16 20:24 ` Julian Sikorski
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).