linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
To: linux-wireless@vger.kernel.org
Subject: Re: Vendor support stickers for devices supported under Linux wireless
Date: Fri, 1 Aug 2008 18:30:02 +0000 (UTC)	[thread overview]
Message-ID: <g6vkn3$3lc$1@ger.gmane.org> (raw)
In-Reply-To: 1217610561.13107.28.camel@dv

On Fri, 01 Aug 2008 13:09:21 -0400, Pavel Roskin wrote:

> On Fri, 2008-08-01 at 10:58 +0200, Michael Renzmann wrote:
>=20
>> How about a "Linux Wireless Foundation"? Some kind of official entit=
y
>> that wireless vendors could talk to for Linux support, certification
>> process for getting the logo, and so on.
>=20
> My concern is that giving any certification would imply that we promi=
se
> to keep the driver in the Linux sources.  However, I don't think we c=
an
> accept legal obligations on behalf of the developers.

Pardon me for butting in, but any vendor reading this thread would like=
ly=20
read "support" to mean user support, rather than exclusively developer=20
support. An often overlooked-by-vendors advantage of fully GPLing a=20
driver is that they can legitimately disclaim any and all end-user=20
support in favor of the community. If they don't fully GPL, they still=20
bear a user-support burden, regardless of whether they meet that burden=
=2E

A formal WiFi Foundation specific to the Linux kernel would be quite=20
excessive. There already is The Linux Foundation, which could potential=
ly=20
take care of any formal vendor liaison with the informal=20
linuxwireless.org group.

If certification is done, the most manageable way to do it would be for=
=20
vendors not to be able to choose what they can say about compatibility,=
=20
but just plaster on a logo with whatever number of "Tux"es shaded the=20
linuxwireless.org assigns them. This, of course, has the disadvantage o=
f=20
requiring retailers to replace compatibility stickers on retail boxes i=
f=20
and when the compatibility status of a device changes, but that would, =
of=20
course, be at vendor discretion.

Come to think of it, the above could apply to *any* hardware=E2=80=A6

--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-08-01 18:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 20:27 Vendor support stickers for devices supported under Linux wireless Luis R. Rodriguez
2008-07-30 20:57 ` drago01
2008-07-30 20:58   ` Luis R. Rodriguez
2008-07-31  9:16     ` Michael Renzmann
2008-07-31 10:08     ` Johannes Berg
2008-07-31 17:05       ` Luis R. Rodriguez
2008-07-31 17:12         ` Johannes Berg
2008-07-31 17:19           ` Luis R. Rodriguez
2008-10-10 17:51             ` Luis R. Rodriguez
2008-10-10 17:52               ` Luis R. Rodriguez
2008-07-31 13:57 ` Nick Kossifidis
2008-07-31 16:51   ` Luis R. Rodriguez
2008-08-01  8:58   ` Michael Renzmann
2008-08-01 17:09     ` Pavel Roskin
2008-08-01 17:45       ` Luis R. Rodriguez
2008-08-01 18:30       ` Daniel Gimpelevich [this message]
2008-08-01 19:09         ` Pavel Roskin

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='g6vkn3$3lc$1@ger.gmane.org' \
    --to=daniel@gimpelevich.san-francisco.ca.us \
    --cc=linux-wireless@vger.kernel.org \
    /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).