From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] General question about hosted interfaces
Date: Fri, 13 Jul 2001 14:53:38 +0000 [thread overview]
Message-ID: <3B4F052A.56A2AAAA@null.net> (raw)
In-Reply-To: <20010712214742.0560A199C0@mail.cse.psu.edu>
bwc@borf.com wrote:
> I've found both the 3com site and the Intel developer's site to be useful.
> It still takes digging, but I've been lucky. The smaller companies are
> a problem. Many of their products are `clones' and they don't even bother
> to write a manual.
As someone who is trying to restore old computer systems, or even
simply getting a 9-track 1/2" magtape drive working on a modern PC,
I keep finding that manufacturers of > ~10 yr. old equipment claim
to have no corporate knowledge of their old products, not even
documentation on file. One gets the feeling that a lot of stuff
is developed by small ad hoc teams that are later disbanded
without having bothered to adequately document their work.
> Also, the PCMCIA, PCI, USB, and other consortia provide the baseline
> description of much of this stuff. The vendors often just say what
> parts they really do. ANSI for the ATA spec, for example. Since
> there are many vendors playing in the same space this makes sense.
> Back when only DEC defined what a VAX was, each peripheral's documentation
> would fully describe that peripheral. Now they say `vesa video controller'
> and just describe what makes them different.
Partly, it's a difference in the user population. In the Good Old Days,
a noticeable fraction of the controllers went to sites that needed the
detailed documentation. E.g. in order to write a UNIX device driver,
which was originally not such an intimidating task as it is now.
Today, only a handful of people (at most) develop low-level device
support, while maybe a million units are sold to end users who are
disinclined to buy anything that is accompanied by technical info.
next prev parent reply other threads:[~2001-07-13 14:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 21:48 bwc
2001-07-13 14:53 ` Douglas A. Gwyn [this message]
2001-07-13 15:32 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-07-12 21:58 jmk
2001-07-12 19:51 geoff
2001-07-12 19:45 geoff
2001-07-12 19:31 jmk
2001-07-12 21:09 ` Chris Locke
2001-07-12 21:24 ` Boyd Roberts
2001-07-12 22:01 ` Jim Choate
2001-07-12 18:38 nemo
2001-07-12 15:26 jmk
2001-07-12 18:14 ` Chris Locke
2001-07-13 14:53 ` Douglas A. Gwyn
2001-07-13 15:28 ` Boyd Roberts
2001-07-13 16:46 ` Douglas A. Gwyn
2001-07-14 0:40 ` Boyd Roberts
2001-07-11 10:54 forsyth
2001-07-11 10:58 ` Lucio De Re
2001-07-11 13:26 ` Boyd Roberts
2001-07-11 10:32 geoff
2001-07-12 8:31 ` Douglas A. Gwyn
2001-07-11 0:37 presotto
2001-07-10 18:22 rob pike
2001-07-10 19:08 ` Mike Haertel
2001-07-10 23:27 ` William K. Josephson
2001-07-11 8:34 ` Douglas A. Gwyn
2001-07-10 15:17 Douglas A. Gwyn
2001-07-10 18:09 ` Lucio De Re
2001-07-11 8:34 ` Douglas A. Gwyn
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=3B4F052A.56A2AAAA@null.net \
--to=dagwyn@null.net \
--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).