From: Andi Kleen <andi@firstfloor.org>
To: Nawn Given <wood.quinn.s@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Writing Device Drivers
Date: Fri, 27 Jun 2014 15:48:03 -0700 [thread overview]
Message-ID: <87y4wivujg.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <CAM83q7BgHSUs5RyWQat_z4O=1sGgecOUb11jAxkun4JSUOe-cg@mail.gmail.com> (Nawn Given's message of "Fri, 27 Jun 2014 16:54:20 -0500")
Nawn Given <wood.quinn.s@gmail.com> writes:
> I recently read some post-commentary on very old Linux mailing list
> messages (announcement to 0.96.)
>
> I'm interested in how someone writes a driver for their hardware. What
> is the process (or if it's become harder to explain since the early
> 90s, what was the process back then) for Linux?
1. Open editor
2. Type code
3. Test code
4. Repeat until code works.
No substantial change since 0.96 as far as I know.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-06-27 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 21:54 Writing Device Drivers Nawn Given
2014-06-27 22:48 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-26 20:10 writing device drivers RaúlNúñez de Arenas Coronado
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
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=87y4wivujg.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wood.quinn.s@gmail.com \
/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