From: Howard Owen <hbo@egbok.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: LKML List <linux-kernel@vger.kernel.org>
Subject: Re: Newbie Roadmap?
Date: Wed, 29 Jun 2005 21:39:44 -0700 [thread overview]
Message-ID: <1120106385.13733.11.camel@owen.egbok.com> (raw)
In-Reply-To: <9a87484905062914275c5de0c9@mail.gmail.com>
On Wed, 2005-06-29 at 23:27 +0200, Jesper Juhl wrote:
> >
> > What I've done so far: I've picked up and started reading "Linux Device
> > Drivers" both editions 2 and 3. I'm about half way through Love's "Linux
> > Kernel Development"
>
> Good choice of books.
>
Thanks for that feedback. They seemed like good choices, but I couldn't
be sure.
> [...]
> > I'm starting
> > out running Slack 10.1, so I'll probably tackle the 2.4 driver first.
> >
> Slackware runs just fine with a 2.6 kernel. I've been running 2.5.x
> and 2.6.x kernels on Slack for ages and I'm currently running
> 2.6.13-rc1 with Slackware-current.
I had planned to switch to the 2.6.x kernel after doing the 2.4 work.
Something tells me there will be a lot of documentation about porting a
driver from 2.4 to 2.6, and somewhat less in the other direction. 8)
> And this I find to be a good website for new kernel hackers :
> http://kernelnewbies.org/
Thanks for that pointer. Although for someone pushing 50, the picture of
the nursing penguin is a little incongruous. 8)
--
Howard Owen hbo@egbok.com "Even if you are on the right
EGBOK Consultants Linux Architect track, you'll get run over if you
fwd:50279 pstn:+1-650-218-2216 just sit there." - Will Rogers
prev parent reply other threads:[~2005-06-30 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 18:20 Howard Owen
2005-06-28 21:41 ` Horst von Brand
2005-06-29 1:08 ` Howard Owen
2005-06-29 21:27 ` Jesper Juhl
2005-06-30 4:39 ` Howard Owen [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=1120106385.13733.11.camel@owen.egbok.com \
--to=hbo@egbok.com \
--cc=jesper.juhl@gmail.com \
--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
all inboxes | Powered by JetHome®