From: Nikunj A Dadhania <nikunj@linux•vnet.ibm.com>
To: Dinar Valeev <k0da@opensuse•org>
Cc: linuxppc-dev@lists•ozlabs.org, Thomas Huth <thuth@redhat•com>,
Dinar Valeev <dvaleev@suse•com>
Subject: Re: [PATCH] Fix function keys sequence on USB
Date: Tue, 02 Jun 2015 15:59:46 +0530 [thread overview]
Message-ID: <87fv6ajtd1.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CADqALGSZ4-SLEjjLcjC+diw7P0TgctjaqtRtXDOUOPxmvtqVqQ@mail.gmail.com>
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:
>>> @@ -262,7 +258,7 @@ static void check_key_code(uint8_t *buf)
>>> case 0x43:
>>> write_key(0x1b); /* F10 */
>>> write_key(0x5b);
>>> - write_key(0x31);
>>> + write_key(0x32);
>>> write_key(0x31);
>>> write_key(0x7e);
>>> break;
>>
>> Does F10 work for you? doesn't work for me ?
> It does. But then menu entry is expanded to openSUSE, with Linux 4.0.1-1-default
> entering edit mode and pressing f10 finally boots it.
>
> xterm sequence is ^[[21~
I had used following in TCG:
qemu-system-ppc64 -machine pseries -m 2G -serial stdio -cdrom distro.iso \
-vnc :1
>
>
>>
>>> @@ -270,7 +266,7 @@ static void check_key_code(uint8_t *buf)
>>> case 0x44:
>>> write_key(0x1b); /* F11 */
>>> write_key(0x5b);
>>> - write_key(0x31);
>>> + write_key(0x32);
>>> write_key(0x33);
>>> write_key(0x7e);
>>> break;
>>> @@ -278,7 +274,7 @@ static void check_key_code(uint8_t *buf)
>>> case 0x45:
>>> write_key(0x1b); /* F12 */
>>> write_key(0x5b);
>>> - write_key(0x31);
>>> + write_key(0x32);
>>> write_key(0x34);
>>> write_key(0x7e);
>>> break;
>>> @@ -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 ?
>>
>>> break;
>>>
>>> case 0x4b:
>>> write_key(0x1b); /* PgUp */
>>> write_key(0x5b);
>>> - write_key(0x33);
>>> + write_key(0x35);
>>> write_key(0x7e);
>>> break;
>>>
>>> case 0x4c:
>>> write_key(0x1b); /* DEL */
>>> write_key(0x5b);
>>> - write_key(0x34);
>>> + write_key(0x33);
>>
>> Right.
>>
>>> write_key(0x7e);
>>> break;
>>>
>>> case 0x4d:
>>> write_key(0x1b); /* END */
>>> write_key(0x5b);
>>> - write_key(0x35);
>>> - write_key(0x7e);
>>> + write_key(0x46);
>>
>> I tried using: 0x34, but somehow it does not work.
> ^[[F works for me.
>
> All changes are tested in openSUSE's grub2 with -vga std. Note we
> don't have any special patches here..
>
> Tested with -vga none -nographic. Home, End works with patched SLOF
Ok.
Regards
Nikunj
next prev parent reply other threads:[~2015-06-02 10:30 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 [this message]
2015-06-02 10:43 ` Dinar Valeev
2015-06-02 11:12 ` Thomas Huth
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=87fv6ajtd1.fsf@linux.vnet.ibm.com \
--to=nikunj@linux$(echo .)vnet.ibm.com \
--cc=dvaleev@suse$(echo .)com \
--cc=k0da@opensuse$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=thuth@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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