All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Dinar Valeev <k0da@opensuse.org>
Cc: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
	Dinar Valeev <dvaleev@suse.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Fix function keys sequence on USB
Date: Tue, 2 Jun 2015 13:12:27 +0200	[thread overview]
Message-ID: <20150602131227.3054b8a3@thh440s> (raw)
In-Reply-To: <CADqALGRXOQnsd0x9pWfdnUphS+PafxAF-X3bNS9HVYdx4dP0qA@mail.gmail.com>

On Tue, 2 Jun 2015 12:43:16 +0200
Dinar Valeev <k0da@opensuse.org> wrote:

> On Tue, Jun 2, 2015 at 12:29 PM, Nikunj A Dadhania
> <nikunj@linux.vnet.ibm.com> wrote:
> > Dinar Valeev <k0da@opensuse.org> writes:
> >
> >> On Tue, Jun 2, 2015 at 11:47 AM, Nikunj A Dadhania
> >> <nikunj@linux.vnet.ibm.com> wrote:
> >>> Dinar valeev <k0da@opensuse.org> writes:
...
> >>>> @@ -290,36 +286,34 @@ static void check_key_code(uint8_t *buf)
> >>>>                               case 0x49:
> >>>>                                       write_key(0x1b);               /* INS */
> >>>>                                       write_key(0x5b);
> >>>> -                                     write_key(0x31);
> >>>> +                                     write_key(0x32);
> >>>>                                       write_key(0x7e);
> >>>>                                       break;
> >>>>
> >>>>                               case 0x4a:
> >>>>                                       write_key(0x1b);              /* HOME */
> >>>>                                       write_key(0x5b);
> >>>> -                                     write_key(0x32);
> >>>> -                                     write_key(0x7e);
> >>>> +                                     write_key(0x48);
> >>>
> >>> Looking at accept.fs - handle-ESC-5b ...
> >>>
> >>> : handle-ESC-5b
> >>>    key
> >>>    dup 31 = IF \ HOME
> >>>       key drop ( drops closing 7e ) handle-^A
> >>>    ELSE
> >>>       dup 33 = IF \ DEL
> >>>          key drop handle-^D
> >>>       ELSE
> >>>          dup 34 = IF \ END
> >>>             key drop handle-^E
> >>>          ELSE
> >>>             dup 1f and handle-CSI
> >>>          THEN
> >>>       THEN
> >>>    THEN drop
> >>> ;
> >>>
> >>>
> >>> ... following change is sufficient:
> >>> -                                       write_key(0x32);
> >>> +                                       write_key(0x31);
> >>>
> >> Home sequence for me is: ^[[H
> >
> > Can you check the above change in your setup ?
> That works as well.

Not sure, but IIRC some of these key codes depend on the keyboard
layout that you are using. What keyboard layout (i.e. language) do
you use?

 Thomas

  reply	other threads:[~2015-06-02 11:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 13:30 [PATCH] Fix function keys sequence on USB Dinar valeev
2015-05-30  9:59 ` [PATCH slof] " Alexey Kardashevskiy
2015-05-30 19:21   ` Dinar Valeev
2015-06-02  9:47 ` [PATCH] " Nikunj A Dadhania
2015-06-02 10:05   ` Dinar Valeev
2015-06-02 10:29     ` Nikunj A Dadhania
2015-06-02 10:43       ` Dinar Valeev
2015-06-02 11:12         ` Thomas Huth [this message]
2015-06-02 11:17           ` Dinar Valeev
2015-07-06  7:58 ` Nikunj A Dadhania
2015-09-01 14:13 ` Thomas Huth
2015-09-01 14:48   ` Dinar Valeev
2015-09-01 15:08     ` Thomas Huth

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=20150602131227.3054b8a3@thh440s \
    --to=thuth@redhat.com \
    --cc=dvaleev@suse.com \
    --cc=k0da@opensuse.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nikunj@linux.vnet.ibm.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.