public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Current doc for writing device drivers?
@ 2000-11-13 15:49 Steven_Snyder
  2000-11-13 15:53 ` Jeff Garzik
  0 siblings, 1 reply; 3+ messages in thread
From: Steven_Snyder @ 2000-11-13 15:49 UTC (permalink / raw)
  To: linux-kernel



Hello.

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?

Thank you.



PLANET PROJECT will connect millions of people worldwide through the combined
technology of 3Com and the Internet. Find out more and register now at
http://www.planetproject.com


-
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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Current doc for writing device drivers?
  2000-11-13 15:49 Current doc for writing device drivers? Steven_Snyder
@ 2000-11-13 15:53 ` Jeff Garzik
  2000-11-13 23:11   ` Jonathan Corbet
  0 siblings, 1 reply; 3+ messages in thread
From: Jeff Garzik @ 2000-11-13 15:53 UTC (permalink / raw)
  To: Steven_Snyder; +Cc: linux-kernel

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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Current doc for writing device drivers?
  2000-11-13 15:53 ` Jeff Garzik
@ 2000-11-13 23:11   ` Jonathan Corbet
  0 siblings, 0 replies; 3+ messages in thread
From: Jonathan Corbet @ 2000-11-13 23:11 UTC (permalink / raw)
  To: linux-kernel; +Cc: Steven_Snyder

> The Rubini book is being updated for 2.2 and 2.4, but I dunno when it
> will go to press.

We're working on it - honest!

The book will go out for technical review before too long; I believe the
current target date to have it on the shelves is April.  We'd hoped for
sooner, but, given how 2.4 development has gone, I think the timing is
about right.  After all, we wouldn't want to present the wrong prototype
for kmap() or miss out on the new inter-module communication API...:)

jon
-
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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2000-11-13 23:41 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-11-13 15:49 Current doc for writing device drivers? Steven_Snyder
2000-11-13 15:53 ` Jeff Garzik
2000-11-13 23:11   ` Jonathan Corbet

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox