From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Scanners
Date: Thu, 26 Nov 2009 20:08:05 +0200 [thread overview]
Message-ID: <f32c04411f827f652d7d29445d28f6bc@proxima.alt.za> (raw)
In-Reply-To: <2B3F3286-3140-4DE6-A5B3-3F9E32B70318@fastmail.fm>
> This may vary by device type, I think I
> heard Linux framebuffer driver source was most useful to developers
> of one OS.
As a NetBSD user, I found the ISDN drivers in Linux considerably
easier to read than the FreeBSD ones (NetBSD didn't include them at
the time). I think NetBSD's philosophy of drawing a very clear
boundary between machine-dependent and machine-indepndent comes
closest to Plan 9; unfortunately, NetBSD is a bit more strict in its
application: Plan 9 prefers the device drivers to be entirely in the
machine-dependent space. Bottom line, both NetBSD and Plan 9 take
their philosophy too far and neither can learn from the other.
Which is why Linux drivers become the examples to follow :-)
++L
next prev parent reply other threads:[~2009-11-26 18:08 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<4B0E14CF.3010406@conducive.org>
2009-11-26 5:51 ` erik quanstrom
2009-11-26 6:43 ` Sam Watkins
2009-11-26 6:51 ` Sam Watkins
2009-11-26 6:54 ` Sam Watkins
2009-11-26 9:25 ` Charles Forsyth
2009-11-26 13:01 ` Ethan Grammatikidis
2009-11-26 18:08 ` lucio [this message]
2009-11-26 23:41 ` Enrico Weigelt
2009-11-26 8:57 ` W B Hacker
[not found] <<4B0E42E2.80906@conducive.org>
2009-11-26 13:20 ` erik quanstrom
2009-11-26 14:35 ` W B Hacker
2009-11-26 14:45 ` erik quanstrom
2009-11-26 14:50 ` Anthony Sorace
2009-11-26 15:11 ` W B Hacker
[not found] <<20091126064335.GC8156@nipl.net>
2009-11-26 13:06 ` erik quanstrom
2009-11-26 18:30 ` ron minnich
2009-11-26 20:08 ` matt
2009-11-26 23:22 ` matt
[not found] <<4B0E0A29.5050106@conducive.org>
2009-11-26 5:06 ` erik quanstrom
2009-11-26 5:40 ` W B Hacker
2009-11-26 9:36 ` Charles Forsyth
[not found] <<3aaafc130911242005m5cfc0d8bs92094b33757711d9@mail.gmail.com>
2009-11-25 4:08 ` erik quanstrom
2009-11-25 9:45 ` Peter A. Cejchan
2009-11-25 11:32 ` Andreas Zell
2009-11-25 12:20 ` Peter A. Cejchan
2009-11-25 12:26 ` Peter A. Cejchan
2009-11-25 14:34 ` hiro
2009-11-25 14:28 ` Andreas Zell
2009-11-25 14:33 ` Jorden Mauro
2009-11-25 14:44 ` hiro
2009-11-25 16:45 ` Peter A. Cejchan
2009-11-25 16:43 ` Peter A. Cejchan
2009-11-25 17:03 ` Jack Norton
2009-11-26 0:51 ` cinap_lenrek
2009-11-25 16:53 ` ron minnich
2009-11-25 17:04 ` Brian L. Stuart
2009-11-25 17:08 ` John Floren
2009-11-25 19:04 ` Brian L. Stuart
2009-12-01 19:52 ` Steve Simon
2009-11-25 17:12 ` hiro
2009-11-25 17:20 ` erik quanstrom
2009-11-25 17:47 ` Anthony Sorace
2009-11-25 17:51 ` erik quanstrom
2009-11-26 3:48 ` Anthony Sorace
2009-11-26 5:16 ` W B Hacker
2009-11-25 19:18 ` ron minnich
2009-11-25 19:49 ` W B Hacker
2009-11-26 0:07 ` Charles Forsyth
2009-11-26 4:55 ` W B Hacker
2009-11-26 13:03 ` Ethan Grammatikidis
2009-11-26 22:59 ` Enrico Weigelt
2009-11-25 14:17 ` Jorden Mauro
2009-11-25 4:05 Jorden Mauro
2009-11-26 23:10 ` Enrico Weigelt
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=f32c04411f827f652d7d29445d28f6bc@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).