* libata dev guide updated
@ 2004-11-17 22:48 Jeff Garzik
0 siblings, 0 replies; 2+ messages in thread
From: Jeff Garzik @ 2004-11-17 22:48 UTC (permalink / raw)
To: linux-ide@vger.kernel.org; +Cc: Alan Cox
I updated the in-kernel DocBook libata guide to include a (short)
chapter describing the hooks needed to implement a driver.
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/libata.pdf
Appearing at a "make pdfdocs" near you, soon.
Jeff
^ permalink raw reply [flat|nested] 2+ messages in thread
* libata dev guide updated
@ 2005-05-31 0:54 Jeff Garzik
0 siblings, 0 replies; 2+ messages in thread
From: Jeff Garzik @ 2005-05-31 0:54 UTC (permalink / raw)
To: linux-ide@vger.kernel.org; +Cc: Linux Kernel
Just made a run through the libata docs, updating them for the latest
hooks and filling in missing details like locking/context documentation.
I've been playing with lulu.com self-publishing, and published this
newly updated libata Developer's Guide there as a short book (92 pages):
http://www.lulu.com/content/130446
I think the muddy road on the front cover is apropos :)
This guide continues to be open source -- just run "make pdfdocs" in the
kernel source tree.
A PDF of the book is available for free on lulu.com or at
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata.pdf or by
running "make pdfdocs" (or "make psdocs", "make htmldocs", ...).
The source code for the guide is in the kernel source tree, with new
additions in the 'docs' branch of
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-05-31 0:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-11-17 22:48 libata dev guide updated Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-05-31 0:54 Jeff Garzik
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).