From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Are these books outdated?
Date: Sun, 24 Jul 2016 06:58:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1607240651150.14647@localhost.localdomain> (raw)
In-Reply-To: <20160714114044.zmizqjiwqj7lo2s6@sith>
On Thu, 14 Jul 2016, Fran?ois wrote:
> On Thu, Jul 14, 2016 at 02:01:55PM +0300, Aleksander Alekseev wrote:
>
> Hello Aleksander,
>
> I only know LDD 3:
> > * Linux Device Drivers, 3rd Edition (2005)
>
> Since this book is freely available in PDF, I would advise you to read it.
> It is out-dated (in sense you won't compile snippets as is) but it is well
> written, and pleasant to read.
>
> The version 4 was scheduled for dec 2015 iirc, but is now annonced
> for nov 2017 on O'Reilly's website.
i have it on reasonably good authority that it's iffy whether there
will ever be an LDD4, only because of the massive amount of work that
would be involved.
i think it would be more productive to concentrate on finding and/or
writing much smaller snippets that focus on how to properly write a
*single* type of driver.
i'm not convinced of the value of trying to invest the time in
writing a book that tries to cover *all* drivers anymore, given the
variety. i think it would be far more useful to find people who,
having expertise in one specific type of driver, would be willing to
write a short tutorial for *just* that type of driver and posting it
online. then, slowly but surely, one could build up a useful set of
online tutorials.
so you're interested in the linux kernel and have no idea where to
start? there's your answer. pick a driver/subsystem you're
*interested* in, and start figuring out how it works. and while
you're doing that, write it up. or if there's already a writeup for
that under the Documentation/ directory, make sure it's up to date and
if it isn't, fix it.
there's no point sitting around waiting for LDD4, hoping others are
going to do your work for you. get to work, start reading and start
writing.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2016-07-24 10:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 11:01 Are these books outdated? Aleksander Alekseev
2016-07-14 11:40 ` François
2016-07-24 10:58 ` Robert P. J. Day [this message]
2016-07-24 18:44 ` Greg KH
2016-07-14 11:43 ` Ricardo Ribalda Delgado
2016-07-14 11:50 ` François
2016-07-14 12:26 ` Robert P. J. Day
2016-07-14 12:49 ` Rami Rosen
2016-07-14 13:53 ` Robert P. J. Day
2016-07-14 14:25 ` Andrey Skvortsov
2016-07-14 14:44 ` Rami Rosen
2016-07-14 21:17 ` Kosta Zertsekel
2016-07-18 9:22 ` Raul Piper
2016-08-07 13:29 ` John Chludzinski
2016-08-10 17:46 ` Raul Piper
2016-08-10 18:14 ` John Chludzinski
2016-08-10 18:17 ` Greg KH
2016-08-10 18:21 ` John Chludzinski
2016-08-11 3:52 ` Raul Piper
2016-08-11 5:27 ` Stefan Wahren
2016-08-11 8:06 ` Aleksander Alekseev
2016-08-11 8:11 ` Raul Piper
2016-08-11 12:49 ` Raul Piper
2016-08-14 19:48 ` Andrey Skvortsov
2016-08-14 20:37 ` Stefan Wahren
2016-08-15 8:02 ` Aleksander Alekseev
2016-08-15 19:17 ` Raul Piper
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=alpine.LFD.2.20.1607240651150.14647@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--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 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).