From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: Warning: Rant. Please disregard. [Was: Re: [9fans] Is IBM ThinkPad R60e notebook compatible with Plan9?]
Date: Wed, 16 May 2007 10:03:02 -0400 [thread overview]
Message-ID: <d6bb5494b1cc80203cb3368d3befa8f2@coraid.com> (raw)
In-Reply-To: <d846ee8c0705160500v186355c2r2b6ea3b1659b78ad@mail.gmail.com>
grow or die
this seems to me to be a statement, not an argument.
you also imply that hobbists can't write drivers. does being
a hobbist set some bit in one's brain that inhibits the device-driver
region?
i suspect the real reason more devices are not supported is:
hardware makers often make it hard or impossible to
obtain specifications. there are big exceptions to this. ahci
was fully documented, for example.
with proper documentation there is nothing magic about a
device driver that makes it any more difficult to write than anything
else.
by the way, there are plenty of professionals working on plan 9.
(and at least 4 new drivers this year.)
- erik
next prev parent reply other threads:[~2007-05-16 14:03 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 8:43 Vester Thacker
2007-05-12 14:36 ` Warning: Rant. Please disregard. [Was: Re: [9fans] Is IBM ThinkPad lucio
2007-05-12 21:56 ` Navin Johnson
2007-05-12 14:38 ` lucio
2007-05-15 17:13 ` Warning: Rant. Please disregard. [Was: Re: [9fans] Is IBM ThinkPad R60e notebook compatible with Plan9?] Dave Lukes
2007-05-16 4:10 ` Navin Johnson
2007-05-16 4:41 ` Warning: Rant. Please disregard. [Was: Re: [9fans] Is IBM lucio
2007-05-16 4:46 ` lucio
2007-05-16 7:29 ` Charles Forsyth
2007-05-16 12:00 ` Warning: Rant. Please disregard. [Was: Re: [9fans] Is IBM ThinkPad R60e notebook compatible with Plan9?] Robert Sherwood
2007-05-16 13:46 ` W B Hacker
2007-05-16 14:03 ` erik quanstrom [this message]
2007-05-16 14:56 ` Robert Sherwood
2007-05-16 17:54 ` Warning: Rant. Please disregard. [Was: Re: [9fans] Is IBM lucio
2007-05-16 18:38 ` Charles Forsyth
2007-05-16 18:42 ` lucio
2007-05-16 23:32 ` W B Hacker
2007-05-16 23:51 ` Uriel
2007-05-17 0:13 ` W B Hacker
2007-05-17 4:41 ` lucio
2007-05-17 11:34 ` W B Hacker
2007-05-17 18:01 ` lucio
2007-05-17 14:26 ` [9fans] Wearables john
2007-05-17 14:33 ` Gabriel Diaz
2007-05-17 14:33 ` David Leimbach
2007-05-17 15:20 ` john
2007-05-17 14:58 ` W B Hacker
2007-05-17 15:30 ` john
2007-05-17 16:38 ` W B Hacker
2007-05-17 15:24 ` ron minnich
2007-05-17 15:33 ` john
2007-05-17 16:00 ` Charles Forsyth
2007-05-17 16:14 ` ron minnich
2007-05-17 16:38 ` john
2007-05-17 16:45 ` Skip Tavakkolian
2007-05-17 16:51 ` W B Hacker
2007-05-17 17:04 ` Salva Peiró
2007-05-17 17:14 ` erik quanstrom
2007-05-17 17:18 ` ron minnich
2007-05-17 19:04 ` tlaronde
2007-05-17 17:24 ` Charles Forsyth
2007-05-17 18:43 ` Charles Forsyth
2007-05-17 18:07 ` lucio
2007-05-18 16:54 ` Warning: Rant. Please disregard. [Was: Re: [9fans] Is IBM Cranky Old Bat
2007-05-18 18:49 ` lucio
2007-05-18 18:58 ` Devon H. O'Dell
2007-05-18 19:32 ` David Leimbach
2007-05-18 19:35 ` ron minnich
2007-05-18 21:21 ` Skip Tavakkolian
2007-05-21 23:32 ` Enrico Weigelt
2007-05-18 19:54 ` Markus Sonderegger
2007-05-16 14:45 ` Douglas A. Gwyn
2007-05-17 14:32 ` Dave Lukes
2007-05-17 18:09 ` lucio
2007-05-18 12:36 ` Gorka Guardiola
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=d6bb5494b1cc80203cb3368d3befa8f2@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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).