toshiba-tablet team mailing list archive

["Justin Dugger" <jldugger@xxxxxxxxx>]

On Sun, Jun 8, 2008 at 5:14 AM, Vincenzo Ciancia <ciancia@xxxxxxxxxxx> wrote:
> Il giorno sab, 07/06/2008 alle 22.04 -0500, Justin Dugger ha scritto:
>>
>> This seems to be the sort of thing this group was made to fix up
>> nicely. Thoughts?
>
> The idea is that we fix everything we know how to fix, and provide fixes
> trough PPA, but of course we have to report fixes to "main" ubuntu as
> quick as possible and get feedback from developers. So you're more than
> welcome to modify the source, test it and post a patch. All members can
> upload to the PPA.

With the spirit of patches in mind, I wrote a quick fdi rule for my
hardware, simply trying to bind the lock screen command to pressing in
on the crosspad.  Before adding the rule, it output 5.  Afterwords,
nothing's changed (sorry, no diff at this instant):

    <match key="system.hardware.vendor" prefix="TOSHIBA">
      <match key="system.hardware.version" contains="PTM71U-0GT01C">
        <prepend key="input.keymap.data"
type="strlist">ffec:lock</append> <!-- tablet crosspad enter? -->
        <prepend key="info.capabilities" type="strlist">input.keymap</append>
      </match>
    </match>

Looking back at the xev stuff, it's pretty clear that this tablet puts
out two keycodes for each button, (Super_R and $button):

KeyPress event, serial 33, synthetic NO, window 0x2400001,
    root 0x1a6, subw 0x0, time 19086910, (58,-8), root:(63,53),
    state 0x10, keycode 116 (keysym 0xffec, Super_R), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 33, synthetic NO, window 0x2400001,
    root 0x1a6, subw 0x0, time 19086911, (58,-8), root:(63,53),
    state 0x50, keycode 14 (keysym 0x35, 5), same_screen YES,
    XLookupString gives 1 bytes: (35) "5"
    XmbLookupString gives 1 bytes: (35) "5"
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x2400001,
    root 0x1a6, subw 0x0, time 19086914, (58,-8), root:(63,53),
    state 0x50, keycode 14 (keysym 0x35, 5), same_screen YES,
    XLookupString gives 1 bytes: (35) "5"
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x2400001,
    root 0x1a6, subw 0x0, time 19086920, (58,-8), root:(63,53),
    state 0x50, keycode 116 (keysym 0xffec, Super_R), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Anyone know how to write HAL quirks for modifiers like Super_R? The
doc didn't seem very clear on this and I haven't seen any examples
yet.

Justin