From: Vojtech Pavlik <vojtech@suse.cz>
To: Maikon Bueno <maikon@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mouse driver
Date: Tue, 13 Jul 2004 22:19:37 +0200 [thread overview]
Message-ID: <20040713201936.GA3124@ucw.cz> (raw)
In-Reply-To: <757c55c604071312106d515d78@mail.gmail.com>
On Tue, Jul 13, 2004 at 04:10:09PM -0300, Maikon Bueno wrote:
> Hi all...
> I'm developing a serial mouse driver and I would like to know how can
> I do to associate a driver with the device.
> To do this driver code I followed a tutorial by Alan Cox. I used the
> register_chrdev function to associate the driver with the device,
> however when I issue "cat /dev/mymouse" (the mymouse device was
> created using the "mknod" command with the same major number of the
> driver and the module is already loaded), I got a error message.
> Is there any way of to do this?
> When are the open_mouse and ourmouse_interrupt functions called?
>
> Thanks!!
I think you should take a look at
Documentation/input/input-programming.txt
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-07-13 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <757c55c6040712065266e867e5@mail.gmail.com>
[not found] ` <20040712172844.GA2375@prot.minidns.net>
[not found] ` <757c55c6040713071814ff655c@mail.gmail.com>
2004-07-13 19:10 ` Mouse driver Maikon Bueno
2004-07-13 20:19 ` Vojtech Pavlik [this message]
2015-03-07 4:27 Ronit Halder
2015-03-07 4:34 ` nick
[not found] ` <CACeEjSLORnMtw-xHem9kOkVeU9kmXFq=LTC+siOJTDSRXwmc9w@mail.gmail.com>
2015-03-07 4:39 ` nick
2015-03-08 21:51 ` Maxime Ripard
2015-03-08 22:09 ` Nicholas Krause
2015-03-09 1:12 ` Ronit Halder
2015-03-09 1:15 ` Nicholas Krause
-- strict thread matches above, loose matches on Subject: below --
2004-01-17 4:18 mouse driver roshan mulla
2004-01-15 7:16 roshan mulla
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=20040713201936.GA3124@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=maikon@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.