kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Mouse driver
Date: Fri, 06 Mar 2015 23:39:21 -0500	[thread overview]
Message-ID: <54FA80F9.4080806@gmail.com> (raw)
In-Reply-To: <CACeEjSLORnMtw-xHem9kOkVeU9kmXFq=LTC+siOJTDSRXwmc9w@mail.gmail.com>



On 2015-03-06 11:36 PM, Ronit Halder wrote:
> This is my semester project and Thanks.
> 
Does it have to be a input driver? If you really want to impress your teacher and
get a better mark,try writing a basic network or usb driver.
Nick

> On Sat, Mar 7, 2015 at 10:04 AM, nick <xerofoify@gmail.com> wrote:
>> 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
>>>

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07  4:27 Mouse driver Ronit Halder
2015-03-07  4:34 ` nick
     [not found]   ` <CACeEjSLORnMtw-xHem9kOkVeU9kmXFq=LTC+siOJTDSRXwmc9w@mail.gmail.com>
2015-03-07  4:39     ` nick [this message]
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

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=54FA80F9.4080806@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 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).