All of lore.kernel.org
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Mouse driver
Date: Fri, 06 Mar 2015 23:34:20 -0500	[thread overview]
Message-ID: <54FA7FCC.6030707@gmail.com> (raw)
In-Reply-To: <CACeEjSJa0Eb4DpLL87iHZJwR6G6qhQTHRj1pfomQUkvYC+gHVQ@mail.gmail.com>

Ronit,
What are your reasons for writing this driver? In addition if you have 
the kernel tree lying around look under drivers/input/mouse for mouse
drivers that are in production to help you understand how to write
one better.
Good Luck,
Nick 

On 2015-03-06 11:27 PM, Ronit Halder wrote:
> Hi,I want to write mouse driver for linux ( usb mouse). I am reading
> "Linux device driver" and "Linux kernel development". But i don't how
> to start writing the driver.
> So,Please help.
> 
> Best regards,
> Ronit.
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 

  reply	other threads:[~2015-03-07  4:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07  4:27 Mouse driver Ronit Halder
2015-03-07  4:34 ` nick [this message]
     [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
     [not found] <757c55c6040712065266e867e5@mail.gmail.com>
     [not found] ` <20040712172844.GA2375@prot.minidns.net>
     [not found]   ` <757c55c6040713071814ff655c@mail.gmail.com>
2004-07-13 19:10     ` Maikon Bueno
2004-07-13 20:19       ` Vojtech Pavlik
  -- 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=54FA7FCC.6030707@gmail.com \
    --to=xerofoify@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.