All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Glover George" <dime@gulfsales.com>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel/Hardware hacking start?
Date: Fri, 28 Dec 2001 15:30:09 -0600	[thread overview]
Message-ID: <007501c18fe6$d3a39e10$0300a8c0@yellow> (raw)

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?  I would like to learn more about the low level
hardware stuff and programming it (the more i think about it, the more it
seems like i just need to re-read Linux Device Drivers :-) ) Is the kernel
the best place to learn this?  Any suggestions would be apprecitated.  Thank
you.



             reply	other threads:[~2001-12-28 21:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 21:30 Glover George [this message]
2001-12-29  1:40 ` Kernel/Hardware hacking start? Arnaldo Carvalho de Melo

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='007501c18fe6$d3a39e10$0300a8c0@yellow' \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.