From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Scanners
Date: Thu, 26 Nov 2009 08:20:59 -0500 [thread overview]
Message-ID: <98c0883597934b1e6f7edea9190916ea@brasstown.quanstro.net> (raw)
In-Reply-To: <<4B0E42E2.80906@conducive.org>>
> But take note of Haiku's move to make their OS capable of using *BSD drivers.
>
> That sort of adapter layer seems worthwhile, even if the results do not
> initially approach 'native' performance.
>
> *After* the dust settles (who woulda thunk, on apparent 'merit' or lack thereof,
> that the dodgy Realtek silicon would ever have become soooo ubiquitous?)
>
> ..THEN 'native' drivers could be gone after for the much smaller subset of
> 'common survivors'. IOW, better a slow, or feature-stripped driver than none at
> all.
i have known about haiku (and a few other oses) using bsd drivers.
i'm sure that most everyone who writes drivesrs for plan 9 knows about
this too.
one of the chief advantages of plan 9 is that it can be understood by
one person. if you drag sk_bufs and all that other goo into the kernel,
you dimish one of plan 9's chief advantages by a considerable amount.
also there is a lot to be gained by writing one's own driver. it pays to
understand the hardware, especially if you depend on it. you may
have to fix some critical bugs. i know some of the hardware that coraid
uses has some fixes that i know linux does not have.
useless observation:
it's fun to see the linux guys bragging about how their drivers are so
small. bsd drivers are typically half their size. plan 9 drivers are typically
half again as large. to be fair, plan 9 drivers typicall give up things like
tso.
- erik
next parent reply other threads:[~2009-11-26 13:20 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<4B0E42E2.80906@conducive.org>
2009-11-26 13:20 ` erik quanstrom [this message]
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] <<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
2009-11-26 23:41 ` Enrico Weigelt
2009-11-26 8:57 ` W B Hacker
[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=98c0883597934b1e6f7edea9190916ea@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).