From: David Christen <davidchristen@gmail.com>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Subject: Re: Enable addition function keys
Date: Wed, 25 May 2011 11:48:39 +0200 [thread overview]
Message-ID: <BANLkTikHKZSqxTu3psHWwaBwiAkWKLhY-Q@mail.gmail.com> (raw)
In-Reply-To: <20110524180259.GG2622@nautilus.holoscopio.com>
On Tue, May 24, 2011 at 8:03 PM, Thadeu Lima de Souza Cascardo
<cascardo@holoscopio.com> wrote:
> On Tue, May 24, 2011 at 10:52:38AM -0700, Dmitry Torokhov wrote:
>> On Tue, May 24, 2011 at 07:39:22PM +0200, David Christen wrote:
>> >
>> > Yes, you were right. Please find the corrected file attached.
>> >
>> > But it seems that the behavior is exactly the same.
>> >
>> > The kernel I use is 2.6.33 . It's a debian distro running on a risc processor.
>>
>> I am afraid you need 2.6.38. Or you'll have to backport the following
>> commits:
>>
>> 8613e4c Input: add support for large scancodes
>> ab4e019 Input: define separate EVIOCGKEYCODE_V2/EVIOCSKEYCODE_V2
>> de391d1 Input: fix typo in keycode validation supporting large scancodes
>> a0bf0ea Input: hid-input - switch to using new keycode interface
>> f5854fa Input: hid-input - allow mapping unknown usages
>>
>> --
>> Dmitry
>
> Perhaps, he could try using hidraw interface. Would it be OK for you,
> David? Since you said you are only getting these key events and sending
> them through a serial interface, and I'd say your device portability
> does not include non-HID devices right now, this should solve the
> problem without the need for a kernel upgrade.
>
> Regards,
> Cascardo.
>
Dear Cascardo and Dmitry,
Thank you for the hint with the hidraw. I was briefly looking at this
in the beginning of the project, but I found it was a bit too raw for
my purpose. Well, I was wrong...
Based on the example in the Documentation
(http://ns3.spinics.net/lists/linux-input/msg14216.html), together
with the patch for HIDIOCSFEATURE
(http://choon.net/forum/read.php?21,19545) and the same for
HIDIOCGRAWNAME I was able to first write a small test program and
later last night to actually build it into my software project.
Thank you very much the effort in helping me with this.
Take care,
David
prev parent reply other threads:[~2011-05-25 9:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 19:54 Enable addition function keys David Christen
2011-05-24 6:22 ` Dmitry Torokhov
2011-05-24 11:30 ` David Christen
2011-05-24 16:27 ` David Christen
2011-05-24 16:49 ` Dmitry Torokhov
2011-05-24 17:39 ` David Christen
2011-05-24 17:52 ` Dmitry Torokhov
2011-05-24 18:03 ` Thadeu Lima de Souza Cascardo
2011-05-25 9:48 ` David Christen [this message]
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=BANLkTikHKZSqxTu3psHWwaBwiAkWKLhY-Q@mail.gmail.com \
--to=davidchristen@gmail.com \
--cc=cascardo@holoscopio.com \
--cc=dmitry.torokhov@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).