From: "Song Sam" <samlinuxppc@yahoo.com.cn>
To: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Any hints on custom keyboard driver?
Date: Thu, 15 Apr 2004 23:24:53 +0800 (CST) [thread overview]
Message-ID: <20040415152453.85184.qmail@web15202.mail.bjs.yahoo.com> (raw)
In-Reply-To: <407B6736.9090607@nortelnetworks.com>
Hi,
I am in a trouble of coding a custom keyboard driver
under 2.4.18.
My custom keyboard scheme is as following:
MPC823 IP_B0 IP_B1 IP_B2 IP_B3 IP_B4-7
Parallel Port
PD0 1 q a z ...
PD1 2 w s x ...
PD2 3 e d c ...
PD3 4 r f v ...
PD4 ... ... ... ... ...
...
My Puzzles:
1. Should I use input.o as interactive interface to
communicate with kernel & user space for convenience?
Otherwise,I need to code it as a normal char device
drvier.I have finished to make PCMCIA and Parallel
port create a character by now.
2. Is there any clue on how to code a standard input
driver?Or any reference in this aspect?
Thanks a million in advance for any input!!!
Sam
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2004-04-15 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <407B6736.9090607@nortelnetworks.com>
2004-04-15 15:24 ` Song Sam [this message]
2004-04-15 16:36 ` Any hints on custom keyboard driver? Brad Boyer
2004-04-16 6:18 ` Song Sam
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=20040415152453.85184.qmail@web15202.mail.bjs.yahoo.com \
--to=samlinuxppc@yahoo.com.cn \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).