From: anish198519851985@gmail.com (anish singh)
To: kernelnewbies@lists.kernelnewbies.org
Subject: looking for simple module/driver programming examples in source tree
Date: Tue, 3 May 2011 20:14:29 +0530 [thread overview]
Message-ID: <BANLkTimFcpK3+PGBkwiDMhZ=5AonU9_uRw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimmBxjnvv4POBZanGW-wD55LaoznA@mail.gmail.com>
On Tue, May 3, 2011 at 7:50 PM, Javier Martinez Canillas <
martinez.javier@gmail.com> wrote:
> >
> >> i'm also interesting in collecting examples of documentation for
> >> basic kernel programming concepts. sometimes, there are excellent
> >> examples in the source Documentation/ directory, sometimes not.
> >
>
> I think a useful work would be to keep an up-to-date version for the
> example drivers found in Linux Device Drivers 3. Despite being a few
> years old, the book is a valuable source of information regarding
> kernel drivers development.
>
> There are lots of repositories with examples updated to many kernel
> versions. A few months ago I needed the examples updated to 2.6.32 and
> found repositories for older kernels. I sent a few patches to the
> author of the most up-to-date repository I found (I think It was
> 2.6.28) but didn't have any feedback so I (also) started my own git
> tree with examples to kernel versions 2.6.32, 2.6.35 and 2.6.38.
>
Yes https://github.com/martinezjavier/ldd3 is very helpful indeed,other day
someone
was asking(on kernelnewbies IRC) for some examples not compiling in latest
kernel
and i gave this link which helped.
>
> Maybe instead having so many repositories all over the Internet trying
> to do the same. It will be good to have a kernelnewbies oficial
> repository for virtual device drivers. These drivers can be a good
> starting point for someone doing real driver development (something
> like the usb-skeleton.c for usb drivers). Also it could be a
> playground for people eager to learn and start contributing with more
> examples.
>
> --
> Javier Mart?nez Canillas
> (+34) 682 39 81 69
> PhD Student in High Performance Computing
> Computer Architecture and Operating System Department (CAOS)
> Universitat Aut?noma de Barcelona
> Barcelona, Spain
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110503/cbb2e213/attachment-0001.html
prev parent reply other threads:[~2011-05-03 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 11:45 looking for simple module/driver programming examples in source tree Robert P. J. Day
2011-05-03 12:28 ` Greg KH
2011-05-03 12:38 ` Robert P. J. Day
2011-05-03 12:54 ` Greg KH
2011-05-03 12:59 ` Robert P. J. Day
2011-05-03 13:39 ` Mandeep Sandhu
2011-05-03 13:44 ` Robert P. J. Day
2011-05-03 13:51 ` Mandeep Sandhu
2011-05-03 14:11 ` Greg KH
2011-05-03 14:20 ` Javier Martinez Canillas
2011-05-03 14:44 ` anish singh [this message]
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='BANLkTimFcpK3+PGBkwiDMhZ=5AonU9_uRw@mail.gmail.com' \
--to=anish198519851985@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).