From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: looking for simple module/driver programming examples in source tree
Date: Tue, 3 May 2011 05:28:00 -0700 [thread overview]
Message-ID: <20110503122800.GA24483@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105030734250.7346@localhost6.localdomain6>
On Tue, May 03, 2011 at 07:45:54AM -0400, Robert P. J. Day wrote:
> once you see that living, breathing example, what more would you
> need to know about how to have your module/driver create a simple
> read-only proc file?
You need to know that if your module/driver ever creates a simple
read-only proc file, they will be flamed to a crisp on lkml when they
submit it :)
Seriously, don't ever create a new proc file, it's not anything anyone
should ever be doing anymore.
> 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.
The kobject documentation should be good, and there are examples in the
samples/ directory in the kernel that should be a great place to start.
Also look at drivers/usb/usb-skeleton.c for an example usb driver. It
is a bit complex, but then again, it's a real-world one so that's needed
in places.
hope this helps,
greg k-h
next prev parent reply other threads:[~2011-05-03 12:28 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 [this message]
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
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=20110503122800.GA24483@kroah.com \
--to=greg@kroah.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).