public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Greg KH <greg@kroah.com>
Cc: s.schmidt@avm.de, torvalds@osdl.org, kkeil@suse.de,
	linux-kernel@vger.kernel.org, opensuse-factory@opensuse.org,
	libusb-devel@lists.sourceforge.net
Subject: Re: 2.6.16 serious consequences / GPL_EXPORT_SYMBOL / USB drivers of major vendor excluded
Date: Sun, 19 Feb 2006 15:34:26 +0100	[thread overview]
Message-ID: <20060219153426.17a26d2b.skraw@ithnet.com> (raw)
In-Reply-To: <20060217230004.GA15492@kroah.com>

On Fri, 17 Feb 2006 15:00:04 -0800
Greg KH <greg@kroah.com> wrote:

> On Thu, Feb 16, 2006 at 03:24:44PM +0100, s.schmidt@avm.de wrote:
> > As a private corporation our primary focus is market relevance. AVM
> > invested more than 10 years of work to make analog services like Fax G3 and
> > analog modem emulation available to users of the digital ISDN network. The
> > situation is similar for the DSL part of the driver with very complex DSP
> > algorithms. To anticipate any "open vs. closed source" discussion:Only a
> > handful of companies worldwide have such know-how. With regard to our
> > competitive situation, we have to protect our hard-won intellectual
> > property and therefore cannot open the closed source part of the driver.

I am fine with that. I prefer stable GPL-drivers anyway, no need to use
yours...

Regards,
Stephan



  reply	other threads:[~2006-02-19 14:34 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
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 [this message]
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=20060219153426.17a26d2b.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=greg@kroah.com \
    --cc=kkeil@suse.de \
    --cc=libusb-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opensuse-factory@opensuse.org \
    --cc=s.schmidt@avm.de \
    --cc=torvalds@osdl.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