public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: s.schmidt@avm.de
Cc: opensuse-factory@opensuse.org, Greg KH <greg@kroah.com>,
	torvalds@osdl.org, kkeil@suse.de, linux-kernel@vger.kernel.org,
	libusb-devel@lists.sourceforge.net
Subject: Re: [opensuse-factory] Re[2]: 2.6.16 serious consequences / GPL_EXPORT_SYMBOL / USB drivers of major vendor excluded
Date: Thu, 16 Feb 2006 23:09:21 +0100	[thread overview]
Message-ID: <43F4F811.1090308@gmx.net> (raw)
In-Reply-To: <OFED05BE20.31E2BACE-ONC1257115.005DE6CA-C1257117.004F2C48@avm.de>

s.schmidt@avm.de wrote:
> 
> The user space does not ensure the reliability of time critical analog
> services like Fax G3 or analog modem emulations. This quality of service
> can only be guaranteed within the kernel space.
> [...] 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.

Thanks for clarifying the situation.

Since your intellectual property is in the DSP algorithms, are there
any obstacles opensourcing the parts of the ISDN drivers which only
handle normal ISDN without fax/modem emulation? This would make every
distribution out there support your devices without any additional work
on your side.
You can still offer your full-featured drivers as usual.

Regards,
Carl-Daniel Hailfinger

  parent reply	other threads:[~2006-02-16 22:09 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 [this message]
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=43F4F811.1090308@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.net \
    --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