From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "Glover George" <dime@gulfsales.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Kernel/Hardware hacking start?
Date: Fri, 28 Dec 2001 23:40:14 -0200 [thread overview]
Message-ID: <20011228234014.B1296@conectiva.com.br> (raw)
In-Reply-To: <007501c18fe6$d3a39e10$0300a8c0@yellow>
In-Reply-To: <007501c18fe6$d3a39e10$0300a8c0@yellow>
Em Fri, Dec 28, 2001 at 03:30:09PM -0600, Glover George escreveu:
> As Eliezer dos Santos Magalhaes was wondering, I too am wanting to learn
> about hacking the linux kernel as well as device drivers. I actually own
> Linux Device Drivers (1st edition), but was wondering if someone could
> direct me towards a source that explained how operating systems deal with
> boot up, initialization of hardware, and the like. In other words, I want
> to learn the kernel from boot up to shutdown. Is there a comprehensive
> guide out there for this?
Have you looked at Documentation at all? :) Ok, I'll do that for you, this
time:
Documentation/kernel-docs.txt
http://www.moses.uklinux.net/patches/lki.html
- Arnaldo
prev parent reply other threads:[~2001-12-29 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 21:30 Kernel/Hardware hacking start? Glover George
2001-12-29 1:40 ` Arnaldo Carvalho de Melo [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=20011228234014.B1296@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=dime@gulfsales.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