All of lore.kernel.org
 help / color / mirror / Atom feed
From: shampavman.cg@gmail.com (shampavman)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Writing device drivers
Date: Wed, 12 Jun 2013 18:41:30 +0530	[thread overview]
Message-ID: <51B87382.8070000@gmail.com> (raw)

Hi all,

I've followed up LDD3 and started off with writing device drivers . As 
usual i've started with char drivers given in that book and also started 
to make minor modifications to learn it better and so on.

Now i would like to know how to take it forward and start writing 
drivers for a profession.
I know its too early to call myself a guy writing device drivers but how 
do i take if forward from here so that i can become one.

Is the only solution to pick up a device which does not work on linux 
and get it working? Are there any other ways as well?


Shampavman

             reply	other threads:[~2013-06-12 13:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 13:11 shampavman [this message]
2013-06-12 13:36 ` Writing device drivers Victor Rodriguez
2013-06-12 13:41   ` shampavman
2013-06-17  6:53     ` Jonathan Paugh
  -- strict thread matches above, loose matches on Subject: below --
2014-06-27 21:54 Writing Device Drivers Nawn Given
2014-06-27 22:48 ` Andi Kleen
2001-12-26 20:10 writing device drivers RaúlNúñez de Arenas Coronado
2001-12-26 18:54 Concerning a driver rewrite (NOT THE KERNEL) victor1 torres
2001-12-26 19:42 ` writing device drivers Eliezer dos Santos Magalhães
2001-12-26 20:01   ` Arnaldo Carvalho de Melo
2001-12-26 20:13   ` Robert Szentmihalyi
2001-12-26 20:15   ` Riley Williams
2001-12-26 22:41   ` Legacy Fishtank
2001-12-27 14:56     ` Eliezer dos Santos Magalhães
2001-12-27 14:57       ` Arnaldo Carvalho de Melo

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=51B87382.8070000@gmail.com \
    --to=shampavman.cg@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.