kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: vikram186@gmail.com (Vikram Narayanan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: knewbies project? - updating LDD3 source (Jim Cromie)
Date: Wed, 25 May 2011 00:48:39 +0530	[thread overview]
Message-ID: <BANLkTimFBh+wwijE8d26wLuRZP+z5f6EdA@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
You can actually see the mail ID. click on the dots and it will ask
for a captcha and it will be revealed.
Try that.

-
Thanks,
Vikram

                 reply	other threads:[~2011-05-24 19:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BANLkTimFBh+wwijE8d26wLuRZP+z5f6EdA@mail.gmail.com \
    --to=vikram186@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).