From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: "P. Christeas" <p_christ@hol.gr>,
Vojtech Pavlik <vojtech@suse.cz>,
lkml <linux-kernel@vger.kernel.org>,
omnibook@zurich.csail.mit.edu
Subject: Re: [OmniBook] Re: Solved: atkbd w 2.6.2rc1 : HowTo for extra (inet) keys ?
Date: Tue, 27 Jan 2004 08:29:09 +1300 [thread overview]
Message-ID: <1075145349.1992.18.camel@laptop-linux> (raw)
In-Reply-To: <20040124193708.A4005@pclin040.win.tue.nl>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
There is an Omnibook module on Sourceforge that contains all the key
information for a variety of models. Furthermore, utilities such as
hotkeys will let you use the keys from within X with very little
configuration. No hacking required there either.
Regards,
Nigel
On Sun, 2004-01-25 at 07:37, Andries Brouwer wrote:
> On Sat, Jan 24, 2004 at 04:28:30AM +0200, P. Christeas wrote:
>
> > Download and hack the 'console-tools' package (from sourceforge, project
> > "lct") so that 'setkeycodes' does accept keycodes >127.
>
> It sounds as if you think that the kbd setkeycodes does not handle keycodes
> above 127, but it does. No hacking required.
>
> _______________________________________________
> OmniBook mailing list
> OmniBook@zurich.csail.mit.edu
> http://zurich.csail.mit.edu/mailman/listinfo/omnibook
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-26 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 20:04 atkbd w 2.6.2rc1 : HowTo for extra (inet) keys ? P. Christeas
2004-01-23 21:09 ` Vojtech Pavlik
2004-01-24 2:28 ` Solved: " P. Christeas
2004-01-24 8:39 ` Vojtech Pavlik
2004-01-24 18:37 ` Andries Brouwer
2004-01-26 19:29 ` Nigel Cunningham [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=1075145349.1992.18.camel@laptop-linux \
--to=ncunningham@users.sourceforge.net \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=omnibook@zurich.csail.mit.edu \
--cc=p_christ@hol.gr \
--cc=vojtech@suse.cz \
/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