From: Roman <muzungu@gmx.net>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: video4linux-list@redhat.com
Subject: Re: Asus PC-39 IR Control: dead keys
Date: Fri, 21 Nov 2008 20:04:43 +0100 [thread overview]
Message-ID: <4927064B.5010900@gmx.net> (raw)
In-Reply-To: <1227234459.4318.14.camel@pc10.localdom.local>
Hi Hermann
I did not know about those tool written by Gerd.
I think they will do. I downloaded and compiled. The tools are working well.
Until the day X might also accept keycodes above 255 I can now map them
to some keycode within 0 -255.
Thanks for the hint and thanks to Gerd for writing them.
Greets
Roman
hermann pitton schrieb:
> Hi Roman,
>
> Am Donnerstag, den 20.11.2008, 22:19 +0100 schrieb Roman:
>
>> Hi all
>>
>> The keys defined with numbers bigger than 255 in the IR_KEYTAB_TYPE
>> ir_codes_asus_pc39[IR_KEYTAB_SIZE] do not get recognized by X11 nor the
>> console.
>>
>> - showkey shows the keycode but no scancode
>> - xev does not react at all on those keys
>> - neither does the console
>> - lineak, as far as I can see, just reacts on keycodes below 256 too, or
>> in other word on what xev does react.
>>
>> How to solve this? How do I get the keys such as KEY_DVD or KEY_ZOOM
>> (>255) get to work with an (X) app?
>>
>> The only solution I can see by now, as long as X11 and the kernel
>> (right?) do not react on key above 255 is
>> - to find me some unused keys below 256,
>> - fill IR_KEYTAB_TYPE ir_codes_asus_pc39[IR_KEYTAB_SIZE] wiht the best
>> fitting,
>> - and recompile the driver module saa7134 with the new key definitions.
>>
>> This is probably NOT the way to go.
>>
>> Any suggestions?
>>
>
> Gerd coded the v4l input layer support when 2.6.x was firstly released
> and lirc did not even compile for a long time after that.
>
> You might remember, that on my P7131 Dual replacement card the IR
> receiver is broken and I don't like to molest others with your report,
> until we have something more clear.
>
> First, preload ir-common with debug=1.
> Any unknown keys now? Should not ever happen.
>
> The <= 256 X limitation is known, but input.h should still be valid for
> a multimedia keyboard.
>
> You can try with Gerd's input utils too.
>
> http://dl.bytesex.org/cvs-snapshots
>
> You should be able to dump the keymap of your keyboard and remote > to
> files.
>
> You then can modify the keymap of the remote with valid keys your
> keyboard provides and load it on the fly with something like
> ./ir-kbd -f my-new-keymap-file.
>
> Cheers,
> Hermann
>
>
>
>
>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
prev parent reply other threads:[~2008-11-21 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 21:19 Asus PC-39 IR Control: dead keys Roman
2008-11-21 2:27 ` hermann pitton
2008-11-21 19:04 ` Roman [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=4927064B.5010900@gmx.net \
--to=muzungu@gmx.net \
--cc=hermann-pitton@arcor.de \
--cc=video4linux-list@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.