9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: bwc@borf.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] General question about hosted interfaces
Date: Thu, 12 Jul 2001 17:48:21 -0400	[thread overview]
Message-ID: <20010712214742.0560A199C0@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]

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.

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.

In 1996 I had top secret copies of one of Intel's chipset I was using.
Today you can the equivilant document off the web.

  Brantley

[-- Attachment #2: Type: message/rfc822, Size: 2013 bytes --]

From: "Chris Locke" <chris@cjl1.demon.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] General question about hosted interfaces
Date: Thu, 12 Jul 2001 22:09:10 +0100
Message-ID: <003d01c10b16$e8128b40$2248dec2@falken>

> So? What makes you think that someone else can?

As an individual (not representing a corporation)
I find it extremely difficult to get hold of data sheets.

I have filled in countless web-forms to register
for the ability to access the 'developer' pages
on a manufacturers site.

I have yet to gain access to a single one!

This make it hard for the hobbyist to get involved in
writing drivers.


             reply	other threads:[~2001-07-12 21:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12 21:48 bwc [this message]
2001-07-13 14:53 ` Douglas A. Gwyn
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=20010712214742.0560A199C0@mail.cse.psu.edu \
    --to=bwc@borf.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).