public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@googlemail.com>
To: s.schmidt@avm.de
Cc: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
	linux-kernel@vger.kernel.org, opensuse-factory@opensuse.org,
	kkeil@suse.de
Subject: Re: 2.6.16 serious consequences / GPL_EXPORT_SYMBOL / USB drivers of major vendor excluded
Date: Sat, 4 Feb 2006 20:24:51 +0100	[thread overview]
Message-ID: <58d0dbf10602041124h72b2ef0fi@mail.gmail.com> (raw)
In-Reply-To: <200602041627.k14GR6Pa019822@turing-police.cc.vt.edu>

2006/2/4, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu>:
> On Fri, 03 Feb 2006 17:24:10 +0100, s.schmidt@avm.de said:
>
> > If it is no longer possible to have non-GPL USB drivers, we shall have to
> > drop our Linux support for all AVM USB devices. We would even have to
> > discontinue the 802.11g++ WLAN USB device driver Linux developement.
>
> Why is there a problem releasing a GPL'ed USB driver?  That would solve

...especially compared to other vendors how do have open source WLAN
USB drivers these days?

> your problem just as well.  If you were really ambitious, you could clean
> up the code and submit it for inclusion in the mainline tree - thus lowering
> your support costs.
>

...and improve the code quality at the same time.

I had some trouble with the closed source fritz card dsl 2.0 driver
e.g. which suffers from a race on recent kernels (I guess Karsten Keil
informed you meanwhile). This should have been tracked down easier and
earlier (last worked on 2.6.8) if your drivers were part of the kernel
or at least taking part in the community.

I really like your hardware, but I dislike such license models.

> > This mail is not intended to provoke a discussion of open vs closed source.
> > The only intention of this mail is to make you aware of the consequences of
> > such a decision.

I tell you my opinion but I will not accept any discussion???

Well, I guess it's not your own decision that AVM is still stuck on
closed Linux drivers, your management may it's own ideas about it as
well. But who else should try to change this than the "engineer at the
front"? This is how many success stories of companies in the open
source domain took off.

I don't know your market, so I may neglect that you have to protect IP
very strictly from nosy competitors. But what part of this IP really
has to be inside the kernel driver? Can you explain this to the Linux
community? This may help a bit to understand your issues with free
drivers.

Jan

  reply	other threads:[~2006-02-04 19:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200601200904.00389.dazzle.digital@gmail.com>
2006-02-03 16:24 ` 2.6.16 serious consequences / GPL_EXPORT_SYMBOL / USB drivers of major vendor excluded s.schmidt
2006-02-03 22:50   ` Pavel Machek
2006-02-04 16:27   ` Valdis.Kletnieks
2006-02-04 19:24     ` Jan Kiszka [this message]
2006-02-09 15:52       ` Jan Engelhardt
2006-02-05 20:53   ` Greg KH
2006-02-16 14:24     ` Re[2]: " s.schmidt
2006-02-16 14:35       ` Arjan van de Ven
2006-02-16 19:49       ` [opensuse-factory] " Robert Schiele
2006-02-16 22:09       ` Carl-Daniel Hailfinger
2006-02-16 22:51         ` Karsten Keil
2006-02-17 23:00       ` Greg KH
2006-02-19 14:34         ` Stephan von Krawczynski
2006-03-06 12:47         ` Re[2]: " s.schmidt
2006-03-06 17:05           ` Greg KH
2006-03-06 21:09             ` [Libusb-devel] " Michael Bender
2006-03-06 22:02               ` Greg KH
2006-03-07  7:42           ` [opensuse-factory] Re[2]: " Silviu Marin-Caea
2006-03-07 22:10             ` Lee Revell
2006-03-07 23:37               ` Matthias Andree
2006-03-08  0:55                 ` Lee Revell
2006-03-08  1:39                   ` Douglas McNaught
2006-02-18  2:42       ` Lee Revell
2006-02-19  4:57       ` Sasha Khapyorsky
2006-02-19 17:02         ` Steven Rostedt
2006-02-20  3:11           ` Sasha Khapyorsky
2006-02-20  6:58             ` Steven Rostedt
2006-02-19 16:25       ` Re[2]: " Christoph Hellwig
2006-02-19  3:09     ` Anton Blanchard
2006-02-19  3:20       ` Greg KH

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=58d0dbf10602041124h72b2ef0fi@mail.gmail.com \
    --to=jan.kiszka@googlemail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opensuse-factory@opensuse.org \
    --cc=s.schmidt@avm.de \
    /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