public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Don Raikes <don.raikes@oracle.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: RE: OT: looking for resources
Date: Wed, 17 Jul 2013 20:19:13 -0700 (PDT)	[thread overview]
Message-ID: <1716186c-3af0-4dc1-be76-e41e96525ca0@default> (raw)
In-Reply-To: <87sizcy626.fsf@mushroom.PK5001Z>

Thanks chris,

Fortunately I am working with a 2.6.28 kernel.
-----Original Message-----
From: Chris Brannon [mailto:chris@the-brannons.com] 
Sent: Wednesday, July 17, 2013 7:07 PM
To: Speakup is a screen review system for Linux.
Subject: Re: OT: looking for resources

Don Raikes <don.raikes@oracle.com> writes:

> While I have taken a class in c programming and have spent the last 
> several days scouring the internet for resources, I am wondering if 
> anyone on this list might have some good tips on getting started with 
> kernel programming real fast.

> Unfortunately the assignment is due on Sunday, but my biggest problem 
> at the moment is allocating memory in the kernel.

I learned from a book called Linux Device Drivers.
It's available online in HTML format.  Just use Google.
If you want plain text, ask me off-list.
Unfortunately, the book was written for the 2.6.x kernels, and its age is starting to show.  In fact, I don't think the sample programs will still compile without some modification.

HTH,
-- Chris
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Don Raikes
 ` Chris Brannon
   ` Don Raikes [this message]
     ` Jason White
       ` Don Raikes
       ` Chris Brannon
         ` Jason White
           ` Don Raikes

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=1716186c-3af0-4dc1-be76-e41e96525ca0@default \
    --to=don.raikes@oracle.com \
    --cc=speakup@linux-speakup.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 read-only IMAP folder(s) and NNTP newsgroup(s).