From: Pedro Venda <pjvenda@arrakis.dhis.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Eugene K <evgfpeters@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: How to start
Date: Sun, 02 Jan 2005 13:39:57 +0000 [thread overview]
Message-ID: <41D7F9AD.3000509@arrakis.dhis.org> (raw)
In-Reply-To: <41D769CE.1070902@verizon.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jim Nelson wrote:
| Eugene K wrote:
|
|> For many years I've been involved in OS/kernel and
|> network development on various platforms (including
|> Intel86) and OSes, but I am totally new to Linux. What
|> would be an optimal way for somebody like me to learn
|> both Linux driver development and Linux Kernel
|> internals ?
this has been very recently asked on the list. some of the suggested answers were:
books:
. linux kernel development by robert love
. linux device drivers by Alessandro Rubini and Jonathan Corbet.
. understanding linux kernel by Daniel P. Bovet and Marco Cesati.
(last two will have new editions soon covering 2.6 kernels)
regards,
pedro venda.
- --
Pedro João Lopes Venda
email: pjlv@mega.ist.utl.pt
http://arrakis.dhis.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB1/mteRy7HWZxjWERAs1zAJ9C0j4kvmENHvuKgtnCQHCFZU7BJQCfcEju
9z+wZb1KlV1cN0k2B2K71Iw=
=Eplx
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-01-02 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 3:04 How to start Eugene K
2005-01-02 3:26 ` Jim Nelson
2005-01-02 13:38 ` Pedro Venda
2005-01-02 13:39 ` Pedro Venda [this message]
2005-01-02 14:36 ` Christoph Anton Mitterer
2005-01-02 14:31 ` Lethalman
-- strict thread matches above, loose matches on Subject: below --
2005-01-03 6:22 Kotian, Deepak
2005-01-03 15:13 ` Jonathan Corbet
2005-01-04 7:26 Kotian, Deepak
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=41D7F9AD.3000509@arrakis.dhis.org \
--to=pjvenda@arrakis.dhis.org \
--cc=evgfpeters@yahoo.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