From: "Song Sam" <samlinuxppc@yahoo.com.cn>
To: Brad Boyer <flar@allandria.com>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Any hints on custom keyboard driver?
Date: Fri, 16 Apr 2004 14:18:53 +0800 (CST) [thread overview]
Message-ID: <20040416061853.85230.qmail@web15207.mail.bjs.yahoo.com> (raw)
In-Reply-To: <20040415163601.GA19251@pants.nu>
Brad Boyer <flar@allandria.com> wrote:
> > 1. Should I use input.o as interactive interface to communicate with
> > kernel & user space for convenience?
> If you want to use this keyboard for your console, then the easiest
> way would be to create an input layer driver.
Thanks for your hints.So,the data flow related my
custom keyboard driver module could be like this:
My_custom_keyboard device -> mykeyboard.o -> input.o
-> keybdev.o -> LINUX kernel
> I think USB and ADB are the only keyboard drivers using the input
> layer in 2.4, but just about everything is using it in 2.6.
That's also a puzzle for me.Use input layer for my
custom keyboard in 2.4 or not and how?Could I take 2.6
PC keyboard driver as a reference for my custom
keyboard driver?
> > 2. Is there any clue on how to code a standard input driver?Or any
> > reference in this aspect?
> There is some documentation in the kernel source. Take a look at the
> stuff in Documentation/input/.
I have studied some stuff in Documentation/input
several days but still have some troubles for these
simplified demo.Also,I searched "linux keyboard
driver" in google but no luck.Anyway,this is my first
time to code a custom driver.I hope this one isn't
hard more than I can chew.
Thanks a lot for your nice advice!
Sam
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-04-16 6:18 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 ` Any hints on custom keyboard driver? Song Sam
2004-04-15 16:36 ` Brad Boyer
2004-04-16 6:18 ` Song Sam [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=20040416061853.85230.qmail@web15207.mail.bjs.yahoo.com \
--to=samlinuxppc@yahoo.com.cn \
--cc=flar@allandria.com \
--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).