From: Andre Bonin <kernel@bonin.ca>
To: linux-kernel@vger.kernel.org
Cc: bonin@bonin.ca
Subject: Support for keyboards with special scancodes
Date: Mon, 03 Jun 2002 13:52:08 -0400 [thread overview]
Message-ID: <3CFBACC8.6010002@bonin.ca> (raw)
I have an Logitech Internet Navigator keyboard that has nice little
'play', 'pause', 'e-mail' buttons of all kinds (As many of us do, i
believe). I couldn't find any specialised keyboard drivers in the
kernel. Only different locales.
I'me wondering if it was possible to write a driver that would overlay
the existing keyboard driver and pitch non-standardized scancodes codes
in a /dev file (in a standard format). One could then create a daemon
that would poll this file for changes to this file and perform the
resulting action.
We could create some sort of standardized protocol for many types of
'special' keyboards. For example, a logitech keyboards sends a '0x0e'
as a special scancode.
A simplified example;
The driver reads the scancode and recognizes it as 'Internet Browser'.
The driver therefore writes a 'IBrowserButton' command in the dev file,
which would be polled by a daemon/applet and would launch the
appropriate action relative to this scancode.
Does something like this already exist?
Can I get your comments on my idea?
Thanks!
***********************************
Andre Bonin
Computer Engineering Technologist
Webmotion, Inc.
Ottawa, Ontario
Canada
***********************************
next reply other threads:[~2002-06-03 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 17:52 Andre Bonin [this message]
2002-06-03 18:11 ` Support for keyboards with special scancodes Xavier Bestel
2002-06-03 19:32 ` Thunder from the hill
2002-06-03 19:44 ` Andre Bonin
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 19:39 Andries.Brouwer
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=3CFBACC8.6010002@bonin.ca \
--to=kernel@bonin.ca \
--cc=bonin@bonin.ca \
--cc=linux-kernel@vger.kernel.org \
/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