9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Jens K. Loewe" <jens.k.loewe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Trying to make 9front work on QWERTZ
Date: Sat, 27 Jul 2019 21:18:38 +0200	[thread overview]
Message-ID: <CALwYwbZFxW73Cas-BQpE0ZE7OAjjrqkRtva3hZ3p7cBkQ=L53A@mail.gmail.com> (raw)
In-Reply-To: <C006D76DF48B6F05893F446AF0CD7566@felloff.net>

> maybe your keyboard produces a different scancode?

The internal T60 keyboard, a native USB keyboard and a DIN-to-USB
converted keyboard all produce the wrong scancodes on different
hardware? That sounds unreasonable.

But I'll try to test that next week ... thank you.

Am Sa., 27. Juli 2019 um 11:22 Uhr schrieb <cinap_lenrek@felloff.net>:
>
> on my t23, which has physical german keyboard layout, the scancode
> for the [<>|] key left to the [Y] key is 0x56 (86 decimal), which
> is not mapped with us layout.
>
> tho this is mapped in german keyboard layout:
>
> term% grep '    86' /sys/lib/kbmap/de
> 0       86      '<
> 1       86      '>
> 2       86      0
> 3       86      '|
> 4       86      0
>
> running the following on my t23 maps it.
>
> term% echo '0 0x56 ''<' > /dev/kbmap
> term% echo '1 0x56 ''>' > /dev/kbmap
> term% echo '3 0x56 ''|' > /dev/kbmap
>
> maybe your keyboard produces a different scancode?
>
> you can attach ratrace to kbdfs [scanproc] pid and look what
> it reads back from /dev/scancode for a ps2 keyboard.
> usb keyboards work differently.
>
> you can bring back that scancode debug thing with F11/F12
> with the following patch which should work for both ps2 and usb
> keyboards.
>
> --- a/sys/src/cmd/aux/kbdfs/kbdfs.c     Thu Jul 25 17:44:47 2019 +0200
> +++ b/sys/src/cmd/aux/kbdfs/kbdfs.c     Sat Jul 27 11:12:20 2019 +0200
> @@ -43,6 +43,7 @@
>         int     alt;
>         int     altgr;
>         int     leds;
> +       int     debug;
>  };
>
>  struct Qtab {
> @@ -337,6 +338,9 @@
>  {
>         Key key;
>
> +       if(scan->debug)
> +               fprint(2, "kbdputsc %#p sc %x esc1 %d esc2 %d\n", scan, c, scan->esc1, scan->esc2);
> +
>         /*
>          *  e0's is the first of a 2 character sequence, e1 and e2 the first
>          *  of a 3 character sequence (on the safari)
> @@ -390,6 +394,13 @@
>         if(scan->ctl && scan->alt && key.r == Kdel)
>                 reboot();
>
> +       if(key.down){
> +               if(key.b == (KF|11))
> +                       scan->debug = 1;
> +               if(key.b == (KF|12))
> +                       scan->debug = 0;
> +       }
> +
>         if(key.b)
>                 send(keychan, &key);
>
> after applying that change, run mk install in /sys/src/cmd/aux/kbdfs
> and then rebuild the kernel (as kbdfs gets included into the kernel image).
>
> --
> cinap
>



  reply	other threads:[~2019-07-27 19:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27  9:21 cinap_lenrek
2019-07-27 19:18 ` Jens K. Loewe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-26 19:54 Jonas Amoson
2019-07-24 19:01 Jens K. Loewe
2019-07-24 21:04 ` Ole-Hjalmar Kristensen
2019-07-25  7:17   ` Rodrigo G. López
2019-07-25 11:40     ` Jens K. Loewe
2019-07-26  5:59       ` Lucio De Re
2019-07-26 16:10         ` Jens K. Loewe

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='CALwYwbZFxW73Cas-BQpE0ZE7OAjjrqkRtva3hZ3p7cBkQ=L53A@mail.gmail.com' \
    --to=jens.k.loewe@gmail.com \
    --cc=9fans@9fans.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).