From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Steven_Snyder@3com.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Current doc for writing device drivers?
Date: Mon, 13 Nov 2000 10:53:30 -0500 [thread overview]
Message-ID: <3A100E7A.2F00682E@mandrakesoft.com> (raw)
In-Reply-To: <88256996.00570596.00@hqoutbound.ops.3com.com>
Steven_Snyder@3com.com wrote:
> My device driver reference "Linux Device Drivers" (Rubini, published by O'Reilly
> on Feb. '98) is getting pretty long in the tooth. The book's primary focus is
> on Linux v2.0.x, with some v2.2.x material tacked on to the end.
>
> What reference(s) are recommended for current (v2.2/v2.4) Linux kernels?
The Rubini book is being updated for 2.2 and 2.4, but I dunno when it
will go to press.
The best reference is the source code. When working with the Linux
kernel, you -quickly- learn to hone your code-reading skills, because
the code is the best documentation.
When you want to figure out how to do something, find a similar example
in the kernel source tree. When you want to figure out the conditions
under which certain code is called, examine all callers. And all
callers of callers. Until you are satisfied you see the complete call
path.
Use the source Luke :)
--
Jeff Garzik |
Building 1024 | The chief enemy of creativity is "good" sense
MandrakeSoft | -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-13 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 15:49 Current doc for writing device drivers? Steven_Snyder
2000-11-13 15:53 ` Jeff Garzik [this message]
2000-11-13 23:11 ` Jonathan Corbet
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=3A100E7A.2F00682E@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Steven_Snyder@3com.com \
--cc=linux-kernel@vger.kernel.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