On Wed, Jan 12, 2005 at 01:25:46PM +0100, Radoslaw Warowny wrote:
>
>---- Wiadomo?? Oryginalna ----
>Od: David Dawes <[EMAIL PROTECTED]>
>Do: [email protected]
>Data: Thu, 6 Jan 2005 12:57:06 -0500
>Temat: Re: Tracer TRK 21 MTS mm kbd - patches
>
>> On Thu, Dec 30, 2004 at 03:00:19PM +0100, Radoslaw Warowny wrote:
>> >Hello again !
>> >
>> >After some development I made few patches for xfree86 source code to
>> >allow succesfull use of the Tracer TRK 21 MTS multimedia keyboard.
>> >My environment is Athlon x86 PC, linux Debian sarge - xfree86 4.3.0.
>> >The first two patches modify keyboard handling of XFree86 server.
>> >This makes the additional 0xe2 codes sent by the keyboard to be
>ignored.
>> 
>> That code is currently (4.4.0 and later) passed up to the DDX, and
>there
>> seems to be at least one keyboard mapping that makes use of it. 
>Filtering
>> it out like this would be a problem for that case.  Is there perhaps a
>> more context-specific way that you could handle this?
>> 
>> David
>> _______________________________________________
>> Devel mailing list
>> [email protected]
>> http://XFree86.Org/mailman/listinfo/devel
>>
>
>My patch should filter only the first E2 scancode (not prefixed with
>E0 or other). The workaroud provided by this should be safe at least

4.4.0 passes an unprefixed E2 up as <K62> (keycode 189), and as I said,
at least one keyboard mapping makes use of <K62>.

>I don't know if it is right for naming the E2 scancode "Prefix" till
>I really don't know function of this code. I have read a little
>about keyboard protocol specifications and didn't find anything
>about E2 scancode. It would be good if somebody would provide some
>information about this. It would help for writting support for such
>kind of keyboard. The xf86PostKbdEvent function seems to be good
>place to add support for the keyboard, but maybe there is other -
>better one ? I am not too familiar with xfree86 source code, so any

If some special handling is required at the scancode level, then that
is probably the best place to do it.

>suggestions welcome. I will provide additional information when I
>test the keyboard with XFree 4.4.0.

Hopefully that will help in finding a good solution to this.

David
_______________________________________________
Devel mailing list
[email protected]
http://XFree86.Org/mailman/listinfo/devel

Reply via email to