From mboxrd@z Thu Jan  1 00:00:00 1970
From: dangets@gmail.com (DG)
Date: Tue, 24 May 2011 12:14:29 -0600
Subject: knewbies project? - updating LDD3 source
In-Reply-To: <alpine.DEB.2.00.1105241345340.4388@localhost6.localdomain6>
References: <BANLkTi=qmLcOdZJzEcRTAe0pxi0gEW4jhw@mail.gmail.com>
	<alpine.DEB.2.00.1105241345340.4388@localhost6.localdomain6>
Message-ID: <BANLkTik=XsJ0LOwA+tJ_XLSUOOsic-Arzg@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Tue, May 24, 2011 at 11:47 AM, Robert P. J. Day
<rpjday@crashcourse.ca> wrote:
> On Tue, 24 May 2011, Jim Cromie wrote:
>
>> over at http://code.google.com/p/ldd3/
>> it says:
>> The famous "Linux Device Drivers" released the sample code. but the
>> code does not reflect the latest kernel updates, some of code cannot
>> even compile. This project is to make it compatible with the current
>> kernel.
>>
>> http://lwn.net/Kernel/LDD3/
>> http://examples.oreilly.com/9780596005900/
>
> ?the one caution i would give here is that quite a bit of code in
> LDD3 shouldn't be updated, anyway, since it reflects features that
> have been deprecated for quite some time.
>
> ?for instance, no one should be writing proc files anymore. ?also,
> ioctl()s are also discouraged for the most part. ?so i would be
> selective about what parts of LDD3 code *should* be updated as
> examples of good kernel programming.
>
> rday

There is a repo on GitHub with the same purpose.  I haven't checked it
out personally, but it's probably worth a look.

https://github.com/martinezjavier/ldd3