From: Norman Wilson <norman@oclsc.org>
To: tuhs@tuhs.org
Subject: [TUHS] MASSCOMP MC-500 Guide to Writing a Unix Device Driver
Date: Mon, 29 Apr 2019 10:38:57 -0400 [thread overview]
Message-ID: <1556548741.10439.for-standards-violators@oclsc.org> (raw)
Dennis's `The UNIX I/O System' paper in Volume 2 of the 7/e
manual is basically about how drivers work. Is that near
enough, possibly as augmented by Ken's `UNIX Implementation'
paper in the same book?
Those were my own starting point, long ago, for understanding
how to write device drivers. Along with existing source code
as examples, of course, but (unlikely many who hack on device
drivers, I'm afraid) I have always preferred to have a proper
statement of rules, conventions, and interfaces rather than
just reading code and guessing.
Norman Wilson
Toronto ON
next reply other threads:[~2019-04-29 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 14:38 Norman Wilson [this message]
2019-04-29 14:53 ` Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2019-04-29 13:49 Warner Losh
2019-04-29 14:45 ` Clem Cole
2019-04-29 14:53 ` Larry McVoy
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=1556548741.10439.for-standards-violators@oclsc.org \
--to=norman@oclsc.org \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).