From: jpaugh@gmx.us (Jonathan Paugh)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Writing device drivers
Date: Mon, 17 Jun 2013 02:53:21 -0400 [thread overview]
Message-ID: <kpmbot$cae$1@ger.gmane.org> (raw)
In-Reply-To: <51B87AA3.3010108@gmail.com>
On 06/12/2013 09:41 AM, shampavman wrote:
>> Now i would like to know how to take it forward and start writing
>> drivers for a profession.
<snip>
> here again the same thing, Unless I have the right hardware i dont know
> what the heck works and what doesn't . Or is there another way to work
> around this limitation?
Why not look for a problem with an existing device driver you *can*
test? I can think of several annoying bugs that my laptop has had at
different times. Even if you can't make contributions right away, just
looking at the code of an interesting driver can help your skill &
understanding. Probably more so than trying to write one from scratch,
because you get the benefit of others' experience.
Regards,
Jonathan Paugh
next prev parent reply other threads:[~2013-06-17 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 13:11 Writing device drivers shampavman
2013-06-12 13:36 ` Victor Rodriguez
2013-06-12 13:41 ` shampavman
2013-06-17 6:53 ` Jonathan Paugh [this message]
-- 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='kpmbot$cae$1@ger.gmane.org' \
--to=jpaugh@gmx.us \
--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.