public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: alan@lxorguk.ukuu.org.uk, egberts@yahoo.com,
	lkml@secureone.com.au, linux-kernel@vger.kernel.org,
	techsupport@itexinc.com
Subject: Re: Dlink DSL PCI Card
Date: Fri, 22 Feb 2002 18:19:50 +0100	[thread overview]
Message-ID: <20020222181950.2fa06bb3.skraw@ithnet.com> (raw)
In-Reply-To: <20020222113600.F14673@redhat.com>
In-Reply-To: <20020220185044.31163.qmail@web10502.mail.yahoo.com> <E16dcnl-0004Wd-00@the-village.bc.nu> <20020222113600.F14673@redhat.com>

On Fri, 22 Feb 2002 11:36:00 -0500
Benjamin LaHaise <bcrl@redhat.com> wrote:

> I did some digging on the chipset used by the dlink card, and its made by the 
> folks at http://www.itexinc.com/ .  They claim Linux support, but only in the 
> form of an infrequently updated binary only module that is only available 
> through OEMs.  Unfortunately, they're uncooperative in providing documentation 
> for writing an open source driver.  It would be Really Nice if the guidelines 
> on the use of the Linux trademark prevented claims of Linux support without 
> driver source (ie, forcing binary only module drivers to be marketed as 
> "partial Linux support through kernel specific binary modules").

I guess I would prefer the hard line: if it states "linux support" there has to be a driver source - or at least full docs for _any_ requesting parties. Otherwise the trademark should not be useable at all. If you provide several "stages" of support, poor "Aunt Tilly" user (is this already tm'ed? :-) won't be able to understand the difference - and you distro-guys (this is not meant to be a BadName) want this type of user to a certain extent.
But this is a very purist point of view.

Beat me,
Stephan



  reply	other threads:[~2002-02-22 17:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20  0:36 Dlink DSL PCI Card 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-22 23:00 Dave Rattay [ITeX]
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-23 13:10 Per Jessen

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=20020222181950.2fa06bb3.skraw@ithnet.com \
    --to=skraw@ithnet.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=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