From: Erik Andersen <andersen@codepoet.org>
To: "Dave Rattay [ITeX]" <Dave.Rattay@itexinc.com>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
Benjamin LaHaise <bcrl@redhat.com>,
alan@lxorguk.ukuu.org.uk, egberts@yahoo.com,
lkml@secureone.com.au, linux-kernel@vger.kernel.org,
ITeX Tech Support <techsupport@itexinc.com>
Subject: Re: Dlink DSL PCI Card
Date: Fri, 22 Feb 2002 16:39:21 -0700 [thread overview]
Message-ID: <20020222233921.GA524@codepoet.org> (raw)
In-Reply-To: <E788BA1D236784409F3F7138F1EABFDDE4E2@iteusa-nt.itexinc.com>
In-Reply-To: <E788BA1D236784409F3F7138F1EABFDDE4E2@iteusa-nt.itexinc.com>
On Fri Feb 22, 2002 at 03:27:56PM -0800, Dave Rattay [ITeX] wrote:
> release. This just doesn't happen with Linux. I agree that this would
You have _always_ had access to Linux. You have had the entire
OS along with full source code to it for the last 10 years....
So 6 months of binary only access beats 10 years of full source?
> Now as to specs for the board itself you can check with sales because I
> am not even sure what our policy is on that and I wish you luck in those
> regards.
If you were able to release full specs for your DSL PCI Card
(including specs on DSPs and the microcode needed to drive them),
I would gladly buy one tomorrow, even without a driver, because I
would know that even if nobody else cared about that card under
Linux, I could read the specs myself and fix the driver, or I
could pay somebody to fix the driver for me. Without that
information, the card dies when Dlink loses interest...
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2002-02-22 23:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 23:27 Dlink DSL PCI Card Dave Rattay [ITeX]
2002-02-22 23:39 ` Erik Andersen [this message]
2002-02-23 12:42 ` Mark H. Wood
-- strict thread matches above, loose matches on Subject: below --
2002-02-23 13:10 Per Jessen
2002-02-22 23:00 Dave Rattay [ITeX]
2002-02-22 22:33 Dave Rattay [ITeX]
2002-02-22 22:49 ` Benjamin LaHaise
2002-02-23 0:00 ` Michal Jaegermann
2002-02-22 23:15 ` Stephan von Krawczynski
2002-02-20 0:36 Andrew Hatfield
2002-02-20 1:57 ` Andrew Hatfield
2002-02-20 18:50 ` S W
2002-02-20 19:53 ` Alan Cox
2002-02-20 20:14 ` S W
2002-02-22 16:36 ` Benjamin LaHaise
2002-02-22 17:19 ` Stephan von Krawczynski
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=20020222233921.GA524@codepoet.org \
--to=andersen@codepoet.org \
--cc=Dave.Rattay@itexinc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=egberts@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@secureone.com.au \
--cc=skraw@ithnet.com \
--cc=techsupport@itexinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox