From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Eliezer@conectiva.com.br, dos@conectiva.com.br,
Santos@conectiva.com.br,
=?iso-8859-1?Q?Magalh=E3es_=3Cmagalhaes=40intime-ne?=@conectiva.com.br,
=?iso-8859-1?B?dC5jb20uYnI+?=@conectiva.com.br
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: writing device drivers
Date: Thu, 27 Dec 2001 12:57:10 -0200 [thread overview]
Message-ID: <20011227125710.C29178@conectiva.com.br> (raw)
In-Reply-To: <F68qvDuJhqFo9iLG7c500010b4e@hotmail.com> <01c301c18e45$6e2dd6b0$6400000a@cyber> <20011226174157.A14542@havoc.gtf.org> <006901c18ee6$bcacad60$6400000a@cyber>
In-Reply-To: <006901c18ee6$bcacad60$6400000a@cyber>
Em Thu, Dec 27, 2001 at 12:56:58PM -0200, Eliezer dos Santos Magalhães escreveu:
> No , it was just an example , I would like to take a source of a device
> drive , and study the code ... well , I have got that book ... I think I
> need to read it very slowly ... thank for the help ...
Some tips: there's some IRC channels that you may find interesting, namely:
#kernelnewbies and #kernel-br, both at irc.openprojects.net, go there and
you'll find plenty of helpful people willing to help you to get into this
kernel hacking journey, join us! :)
- Arnaldo
next prev parent reply other threads:[~2001-12-27 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 18:54 Concerning a driver rewrite (NOT THE KERNEL) victor1 torres
2001-12-26 19:42 ` writing device drivers Eliezer dos Santos Magalhães
2001-12-26 20:01 ` Arnaldo Carvalho de Melo
2001-12-26 20:13 ` Robert Szentmihalyi
2001-12-26 20:15 ` Riley Williams
2001-12-26 22:41 ` Legacy Fishtank
2001-12-27 14:56 ` Eliezer dos Santos Magalhães
2001-12-27 14:57 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-26 20:10 RaúlNúñez de Arenas Coronado
2014-06-27 21:54 Writing Device Drivers Nawn Given
2014-06-27 22:48 ` Andi Kleen
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=20011227125710.C29178@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc==?iso-8859-1?B?dC5jb20uYnI+?=@conectiva.com.br \
--cc==?iso-8859-1?Q?Magalh=E3es_=3Cmagalhaes=40intime-ne?=@conectiva.com.br \
--cc=Eliezer@conectiva.com.br \
--cc=Santos@conectiva.com.br \
--cc=dos@conectiva.com.br \
--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