From: Benjamin LaHaise <bcrl@redhat.com>
To: "Dave Rattay [ITeX]" <Dave.Rattay@itexinc.com>
Cc: Stephan von Krawczynski <skraw@ithnet.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 17:49:59 -0500 [thread overview]
Message-ID: <20020222174959.A16169@redhat.com> (raw)
In-Reply-To: <E788BA1D236784409F3F7138F1EABFDDE4DF@iteusa-nt.itexinc.com>
In-Reply-To: <E788BA1D236784409F3F7138F1EABFDDE4DF@iteusa-nt.itexinc.com>; from Dave.Rattay@itexinc.com on Fri, Feb 22, 2002 at 02:33:48PM -0800
On Fri, Feb 22, 2002 at 02:33:48PM -0800, Dave Rattay [ITeX] wrote:
> Stephan,
>
> I am not sure if you actually requesting anything but here are some
> points on this matter. First and foremost we do not make these cards.
> They are made by our customers that we supply chips for. We do make the
> drivers for these boards but they can then be customized by our
> customers. The point is that we do support Linux for our customers and
> our customers are not really end-users. Now since end-users are
> indirectly our customers we do supply Linux drivers on request. Also if
> we cannot meet a request for any reason that information is added to our
> Marketing data for future driver development. Due to previous licensing
> agreements we cannot release our source code to anyone including our
> direct customers and there is no way around that. Sorry. Now if you
> have a request for a driver please let me know the kernel version being
> used as well as the ADSL protocol that you have. I will see what I can
> do to get you a usable driver.
You're missing the point. We as developers want the specifications for
the hardware as we're completely willing to write our own driver from
scratch. Until Itex is able to provide this to developers, products
based on your chipsets will remain not recommended for Linux users as
it will continually result in a poor user experience.
-ben
next prev parent reply other threads:[~2002-02-22 22:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 22:33 Dlink DSL PCI Card Dave Rattay [ITeX]
2002-02-22 22:49 ` Benjamin LaHaise [this message]
2002-02-23 0:00 ` Michal Jaegermann
2002-02-22 23:15 ` Stephan von Krawczynski
-- strict thread matches above, loose matches on Subject: below --
2002-02-23 13:10 Per Jessen
2002-02-22 23:27 Dave Rattay [ITeX]
2002-02-22 23:39 ` Erik Andersen
2002-02-23 12:42 ` Mark H. Wood
2002-02-22 23:00 Dave Rattay [ITeX]
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=20020222174959.A16169@redhat.com \
--to=bcrl@redhat.com \
--cc=Dave.Rattay@itexinc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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