linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julian Sikorski <belegdol@gmail.com>
To: linux-input@vger.kernel.org
Subject: Re: Logitech Alto Cordless
Date: Wed, 03 Dec 2008 09:57:21 +0100	[thread overview]
Message-ID: <493649F1.8090001@gmail.com> (raw)
In-Reply-To: <493424C7.30209@gmail.com>

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

  reply	other threads:[~2008-12-03  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2008-12-16 18:37       ` Julian Sikorski
2008-12-16 20:24         ` Julian Sikorski

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=493649F1.8090001@gmail.com \
    --to=belegdol@gmail.com \
    --cc=linux-input@vger.kernel.org \
    /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).