From: Jeffrey Lim <jfs.world@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: help with writing a usb mouse driver
Date: Sat, 27 Nov 2004 23:39:37 +0800 [thread overview]
Message-ID: <4b3125cc041127073956f967de@mail.gmail.com> (raw)
Note: pls cc me in any replies as i'm not subscribed to the list.
hi guys, i've been trying to write a usb mouse driver for a custom
mouse, but i'm getting stuck.
I previously started out with trying to hack usbmouse.c, but
apparently after a wild goose chase, it seems that that is not the
recommended path to take. It supposedly conflicts with the hid driver,
though in what way i do not know. (If somebody could enlighten me on
this, pls do. Documentation/input/input.txt does not really explain
why).
So now it almost seems as if the only code i have for analysis and as
a sample is the hid code (hid-core.c, hid-input.c, i assume). But the
problem for me is that this code is too complex for me, and really
doesn't offer the easiest way to get started on this project. I'm not
too sure usb-skeleton.c does it either, because it doesn't have the
code for interfacing with the input layer.
While i could take some pointers for interfacing with the input layer
from usbmouse.c, i really don't see how I could differentiate what
code to take, cos heck, that thing doesnt even work (conflicts with
hid), and I don't even know why! (That thing looks pretty ok to me).
Could somebody give me some pointers on how to go about starting my
project, and where I might perhaps be able to get my hands on some
code that i can work with?
I'm using kernel 2.4.20.
Thanks,
-jf
next reply other threads:[~2004-11-27 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 15:39 Jeffrey Lim [this message]
2004-12-01 0:34 ` help with writing a usb mouse driver Greg KH
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=4b3125cc041127073956f967de@mail.gmail.com \
--to=jfs.world@gmail.com \
--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