9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] devkbmap.c
Date: Wed, 17 Mar 2004 08:18:39 +0100	[thread overview]
Message-ID: <733e4618bd40c06765b233dc3c0a42b4@plan9.escet.urjc.es> (raw)
In-Reply-To: <f993aa36145be471e49a0bd23ca0a3a7@plan9.bell-labs.com>

[-- Attachment #1: Type: text/plain, Size: 123 bytes --]

Thanks a lot!

Yet another local diff we can get rid of ☺

I'll change usbhid to work with this for usb
keyboards.

[-- Attachment #2: Type: message/rfc822, Size: 2409 bytes --]

From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: [9fans] devkbmap.c
Date: Tue, 16 Mar 2004 15:19:04 -0500
Message-ID: <f993aa36145be471e49a0bd23ca0a3a7@plan9.bell-labs.com>

I included the boyd/forsyth keyboard map stuff in the
kernel.  man kbmap for details.

In general you can

	bind -a'#κ' /dev
	cat /dev/kbmap > /tmp/xxx
	edit /tmp/xxx
	cat /tmp/xxx > /dev/kbmap

I also changed /sys/src/9/boot/boot.c to automaticly
load a map if specified in plan9.ini as
	kbmap=<file>

In this case <file> has to be something you can get
at before there's a file system so you'll have to
make sure its in /boot/.  The reason it gets done
so early is that factotum starts before you have an
fs and it would be nice if your keyboard had the
right mapping when you type in your login name
ans password.

No idea of the boot change works yet.  Haven't tested
it...

As usual, my apologies to the japanese/chinese/etc.

I'll put any mapping files I get into /sys/lib/kbmap
on sources.

      parent reply	other threads:[~2004-03-17  7:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 20:19 David Presotto
2004-03-16 20:51 ` boyd, rounin
2004-03-17  7:18 ` Fco.J.Ballesteros [this message]

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=733e4618bd40c06765b233dc3c0a42b4@plan9.escet.urjc.es \
    --to=nemo@lsub.org \
    --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).