public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Adrian Bunk <bunk@stusta.de>, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] HOWTO do Linux kernel development - take 2
Date: Wed, 16 Nov 2005 09:46:02 +0800	[thread overview]
Message-ID: <2cd57c900511151746k341b93a3u@mail.gmail.com> (raw)
In-Reply-To: <20051116011032.GA16604@kroah.com>

2005/11/16, Greg KH <greg@kroah.com>:
> On Wed, Nov 16, 2005 at 01:23:48AM +0100, Adrian Bunk wrote:
> > > Introduction
> > > ------------
> > >...
> > > The kernel is written mostly in C, with some architecture-dependent
> > > parts written in assembly. A good understanding of C is required for
> > > kernel development.  Assembly (any architecture) is not required unless
> > > you plan to do low-level development for that architecture.  Though they
> > > are not a good substitute for a solid C education and/or years of
> > > experience, the following books are good for, if anything, reference:
> > >  - "The C Programming Language" by Kernighan and Ritchie [Prentice Hall]
> > >  - "Practical C Programming" by Steve Oualline [O'Reilly]
> > >  - "Programming the 80386" by Crawford and Gelsinger [Sybek]
> > >  - "UNIX Systems for Modern Architectures" by Curt Schimmel [Addison Wesley]
> >
> >
> > "UNIX Systems for Modern Architectures" is a good book about cpu caches.
> >
> > But it's hardly interesting for the average driver writer and even less
> > a book about C programming.
>
> True, I've removed it now, thanks.

Also why you have to mention those non-free books here? I don't read
them and I live OK. There's plenty of free information one can always
find on the net.

>
> > LDD (as you might have heard, it's also available online for free ;-) )
> > and the book by Robert Love are good starting points for learning kernel
> > programming, and they should IMHO be listed here.
>
> But that's what the Documentation/kernel-docs.txt file has in it.  I
> don't want to get into judging which kernel books go into this file, as
> people might think I am a bit biased :)
>
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/

  reply	other threads:[~2005-11-16  1:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 21:05 [RFC] HOWTO do Linux kernel development - take 2 Greg KH
2005-11-15 21:52 ` Avuton Olrich
2005-11-15 21:54   ` Greg KH
2005-11-16  5:31   ` Rogério Brito
2005-11-16  5:38     ` Greg KH
2005-11-15 22:06 ` Jesper Juhl
2005-11-15 22:01   ` Greg KH
2005-11-15 22:08 ` Andreas Schwab
2005-11-15 21:59   ` Greg KH
2005-11-15 22:21 ` Jesper Juhl
2005-11-15 22:30   ` Greg KH
2005-11-18  5:40     ` Jody McIntyre
2005-11-21 22:03       ` Greg KH
2005-11-15 22:27 ` Jesper Juhl
2005-11-15 22:36   ` Greg KH
2005-11-16  0:23 ` Adrian Bunk
2005-11-16  1:10   ` Greg KH
2005-11-16  1:46     ` Coywolf Qi Hunt [this message]
2005-11-16  2:01       ` Alistair John Strachan
2005-11-16  2:17     ` Adrian Bunk
2005-11-16  5:47       ` Greg KH
2005-11-16 17:28 ` David Woodhouse
2005-11-16 17:38   ` Randy.Dunlap
2005-11-16 17:40   ` Jörn Engel

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=2cd57c900511151746k341b93a3u@mail.gmail.com \
    --to=coywolf@gmail.com \
    --cc=bunk@stusta.de \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.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