From: jim.cromie@gmail.com (Jim Cromie)
To: kernelnewbies@lists.kernelnewbies.org
Subject: knewbies project? - updating LDD3 source
Date: Tue, 24 May 2011 11:35:26 -0600 [thread overview]
Message-ID: <BANLkTi=qmLcOdZJzEcRTAe0pxi0gEW4jhw@mail.gmail.com> (raw)
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/
Neither the OReilly tarball, nor the googlecode's svn repo will compile for me
on an updated F-14 box, neither against uname -r, or a local git-tree.
So I pulled the svn-tree, and made these changes.
I got a fair way to getting things to compile.
Changes are quick-n-dirty, and some may be wrong,
esp around workqueue stuff - I pretty much did what compiler told me,
w/o any analysis.
I didnt even get compilation on the aio/iovec users, on the changes from 2003.
I havent really gotten my head around the whole conversion strategy;
I know a loop over iovec elements is probably needed,
but Im unclear where it should be.
and Im unsure whether these functions are now cluttering up things.
static void sculld_do_deferred_op(void *p)
static int sculld_defer_op(int write, struct kiocb *iocb, const struct
iovec *iov,
size_t count, loff_t pos)
I guess the point is Ive run out of time now, and am hoping for a dose
of clarity, and further patches, to get LDD3 source compiling, up-to-date,
and reflecting current best practices.
GRUMBLING: its annoying that the googlecode web-page obfuscates the
site owner, making it impossible to reach him.
Username: guanzhi1... at gmail.com
Is there another LDD3 repo somewhere, that a google search didnt reveal to me ?
perhaps on kernel.org ??
Should there be ?
Im attaching my svndiff, in hte hopes that folks here will
apply it and improve upon it.
thanks
~jimc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ldd3-code.svndiff
Type: application/octet-stream
Size: 20910 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110524/c9441ff7/attachment-0001.obj
next reply other threads:[~2011-05-24 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 17:35 Jim Cromie [this message]
2011-05-24 17:47 ` knewbies project? - updating LDD3 source Robert P. J. Day
2011-05-24 18:14 ` DG
2011-05-24 20:17 ` Javier Martinez Canillas
2011-05-24 20:26 ` Robert P. J. Day
2011-05-24 20:32 ` Leon Woestenberg
2011-05-24 20:36 ` Robert P. J. Day
2011-05-24 21:02 ` Javier Martinez Canillas
2011-05-24 20:37 ` Manohar Vanga
2011-05-25 3:42 ` naren.mehra at gmail.com
2011-05-25 6:27 ` Mohamed Thalib H
2011-05-25 7:29 ` sumeet linux
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='BANLkTi=qmLcOdZJzEcRTAe0pxi0gEW4jhw@mail.gmail.com' \
--to=jim.cromie@gmail.com \
--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).