9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: FJ Ballesteros <nemo@gsyc.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kbd.c
Date: Sat, 30 Mar 2002 22:05:07 +0100	[thread overview]
Message-ID: <3CA62883.43F9B212@gsyc.escet.urjc.es> (raw)
In-Reply-To: <Pine.LNX.4.30.0203231453360.878-400000@donkey.bronnikov.mccme.ru>


My students have just implemented a change to the distributed
kbd to let it use different tables. It does not need a different
device like kbmap, but instead lets the user select the table
to be used by using the config file. They are changing this
further to let the driver accept a "kbmap us" string into /dev/consctl
to change the tables at run time.

They plan to select a good implementation of this change and send the
contribution. Perhaps it would be better to unify this all to get just
one driver capable of adapting to most of our keyboards.


George Bronnikov ha escrito:
> 
> Hello,
> 
> Attached are:
> 
> 1. A diff to Boyd's/Forsyth's keyboard driver (/sys/src/9/pc/kbd.c) that
> lets it have separate tables for capslock and shift+capslock (tables 4 and 5).
> 2. Russian keyboard table using this diff (capslock serves to switch
> between cyrillic and latin modes).
> 3. An awk script to feed the table into /dev/kbmap.
> 
>         goga
> 
>   ------------------------------------------------------------------------
>                 Name: kbmap.awk
>    kbmap.awk    Type: Plain Text (TEXT/PLAIN)
>             Encoding: BASE64
> 
>                 Name: kbmap.cyr
>    kbmap.cyr    Type: Plain Text (TEXT/PLAIN)
>             Encoding: BASE64
> 
>                  Name: kbd.c.diff
>    kbd.c.diff    Type: Plain Text (TEXT/PLAIN)
>              Encoding: BASE64


  reply	other threads:[~2002-03-30 21:05 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-23 12:01 George Bronnikov
2002-03-30 21:05 ` FJ Ballesteros [this message]
2002-03-31 12:45   ` Boyd Roberts
2002-03-30 21:08 rob pike, esq.
2002-03-31 18:58 ` FJ Ballesteros
2002-04-01  0:36   ` Boyd Roberts
2002-04-01  0:42   ` Boyd Roberts
2002-03-30 21:10 rob pike, esq.
2002-03-30 21:20 Geoff Collyer
2002-04-08 12:47 ` Matthew C Weigel
2002-03-30 21:28 rob pike, esq.
2002-03-30 22:41 ` Richard
2002-03-30 22:47 ` Digby Tarvin
2002-03-31 11:26   ` kazumi iwane
2002-03-31 12:21     ` kazumi iwane
2002-03-31  2:47 ` kazumi iwane
2002-03-31 18:32 ` George Bronnikov
2002-04-01  0:47   ` Boyd Roberts
2002-04-01  6:50     ` George Bronnikov
2002-04-01  7:22       ` Lucio De Re
2002-04-01 11:35         ` Boyd Roberts
2002-04-01 16:27         ` kazumi iwane
2002-04-01 16:33           ` Lucio De Re
2002-04-01 11:34       ` Boyd Roberts
2002-03-30 23:13 Russ Cox
2002-03-31  5:40 rob pike, esq.
2002-03-31 10:24 forsyth
2002-03-31 14:48 bwc
2002-03-31 15:13 ` Boyd Roberts
2002-03-31 17:06 ` Digby Tarvin
2002-03-31 19:35 andrey mirtchovski
2002-04-01  1:40 okamoto
2002-04-01  1:54 okamoto
2002-04-01 14:01 rob pike, esq.
2002-04-02  1:58 okamoto
2002-04-02  5:04 plan9
2002-04-02  8:17 Fco.J.Ballesteros
2002-04-02  8:28 Fco.J.Ballesteros
2002-04-02  9:31 forsyth
2002-04-02  9:44 ` Boyd Roberts
2002-04-02 10:42 forsyth
2002-04-08 12:54 ` Andries Brouwer
2002-04-02 10:48 forsyth
2002-04-02 10:56 ` Lucio De Re

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=3CA62883.43F9B212@gsyc.escet.urjc.es \
    --to=nemo@gsyc.escet.urjc.es \
    --cc=9fans@cse.psu.edu \
    /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).