From: Julian Sikorski <belegdol@gmail.com>
To: linux-input@vger.kernel.org
Subject: Re: Logitech Alto Cordless
Date: Mon, 01 Dec 2008 17:46:49 +0100 [thread overview]
Message-ID: <493414F9.2050309@gmail.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0812011734130.28179@twin.jikos.cz>
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
next prev parent reply other threads:[~2008-12-01 16:46 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 [this message]
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
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=493414F9.2050309@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).