From: matthias.bgg@googlemail.com (Matthias Brugger)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Guidance on writing device drivers
Date: Fri, 18 Nov 2011 16:50:15 +0000 [thread overview]
Message-ID: <4EC68CC7.9060900@gmail.com> (raw)
In-Reply-To: <CAAFf3B_1ZsZHsy+Tm2LBv4Dd778XdJQBnV_4FyBQpu0NSn4RKw@mail.gmail.com>
On 11/10/2011 05:26 AM, Prajosh Premdas wrote:
> [...]
> On Thu, Nov 10, 2011 at 10:08 AM, rohan puri <rohan.puri15@gmail.com
> <mailto:rohan.puri15@gmail.com>> wrote:
> On Wed, Nov 9, 2011 at 10:40 PM, suraj khurana
> <surajkhurana27 at gmail.com <mailto:surajkhurana27@gmail.com>> wrote:
>
> Hi all,
> I am a newbie in linux world and want to learn linux device drivers.
>
> I am currently reading book - "Linux Device Drivers" by O'reilly.
>
> Does anyone has any problem statements based on device drivers
> for practice
> so that I can enhance my skills in writing device drivers.
The Linux Device Driver book (ldd3) is outdated, as Linux kernel ABI
changes constantly, although I would still recommend the book as good
starting point.
Martinez Javier started to port the source code examples to the actual
Kernel versions. I'm not sure about the actual status of the work, but I
vaguely remember that I tried to use the block device driver some month
ago. It compiled without any warning but crashed when used.
Maybe you want to dig in the example code and see if you can find and
resolve some issues.
https://github.com/martinezjavier/ldd3
Regards,
Matthias
>
>
> Thanks,
> Suraj
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> <mailto:Kernelnewbies@kernelnewbies.org>
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
> Hello Suraj,
> I would suggest complete reading the book with the examples given in
> the book.
>
> Regards,
> Rohan Puri
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
>
>
> --
> Regards,
>
> Prajosh Premdas
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
---
http://motzblog.wordpress.com/
next prev parent reply other threads:[~2011-11-18 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 17:10 Guidance on writing device drivers suraj khurana
2011-11-10 4:38 ` rohan puri
2011-11-10 5:26 ` Prajosh Premdas
2011-11-18 16:50 ` Matthias Brugger [this message]
2011-11-24 22:28 ` Javier Martinez Canillas
2011-12-15 5:14 ` पारस
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=4EC68CC7.9060900@gmail.com \
--to=matthias.bgg@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.