From: Alex deVries <adevries@thepuffingroup.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dave@hiauly1.hia.nrc.ca, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] HP releasing docs...
Date: Thu, 16 Dec 1999 18:09:10 -0500 [thread overview]
Message-ID: <38597116.3E8A11A2@thepuffingroup.com> (raw)
In-Reply-To: E11yEJD-0001UT-00@the-village.bc.nu
Alan Cox wrote:
> > Ideally, though, developers will have access to all the hardware they're
> > porting to.
> Irrespective of who they work for ?
I actually meant that they'd have docs for the hardware they're porting
too, but this is true too.
I think we've been pretty blind in giving hardware out at the start, and
I don't see this changing.
However, what doesn't make sense is to ship people hardware that contain
critical components that either a) don't yet have drivers written or b)
we can't send docs on.
- Alex
--
Alex deVries
Vice President of Engineering
The Puffin Group
next prev parent reply other threads:[~1999-12-19 16:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-15 1:22 [parisc-linux] Puffin sells out! John David Anglin
1999-12-15 2:39 ` Alan Cox
1999-12-15 7:00 ` Eric Molitor
1999-12-16 5:47 ` Alex deVries
1999-12-19 17:43 ` Philipp Rumpf
1999-12-15 8:25 ` [parisc-linux] HP releasing docs Alex deVries
1999-12-15 13:17 ` Alan Cox
1999-12-16 23:09 ` Alex deVries [this message]
1999-12-19 19:19 ` Eric Molitor
1999-12-19 19:10 ` Alan Cox
1999-12-19 20:16 ` John David Anglin
1999-12-15 8:04 ` [parisc-linux] Puffin sells out! Alex deVries
1999-12-15 16:25 ` John David Anglin
[not found] ` <19991214215358.A31893@thepuffingroup.com>
1999-12-15 18:36 ` Jack Perdue
1999-12-15 20:36 ` Matthew Wilcox
1999-12-15 20:56 ` John David Anglin
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=38597116.3E8A11A2@thepuffingroup.com \
--to=adevries@thepuffingroup.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@thepuffingroup.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.