public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Bender <Michael.Bender@Sun.COM>
To: Greg KH <greg@kroah.com>
Cc: s.schmidt@avm.de, kkeil@suse.de,
	libusb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	linux-kernel-owner@vger.kernel.org,
	opensuse-factory@opensuse.org, torvalds@osdl.org
Subject: Re: [Libusb-devel] Re: 2.6.16 serious consequences / GPL_EXPORT_SYMBOL / USB drivers of major vendor excluded
Date: Mon, 06 Mar 2006 13:09:52 -0800	[thread overview]
Message-ID: <440CA520.8070507@sun.com> (raw)
In-Reply-To: <20060306170542.GB8142@kroah.com>

Greg KH wrote:
> On Mon, Mar 06, 2006 at 01:47:43PM +0100, s.schmidt@avm.de wrote:
>
>>Compared to other operating systems, such as Mac OS, BeOS,
>>Windows etc., Linux is walking a solitary path with the "user mode only"
>>shift. One gets the impression, that legal concerns are leading Linux to a
>>technically suboptimal/isolated solution.
>
> No, right now, Linux has the best latency numbers _by far_ than any
> other operating system, so we can move stuff to userspace.
> 
> And again, it's your legal issues that are forcing you that way, if you
> change that, putting everything in the kernel would be fine :)

(Since this came to me via the libusb list, and we've kind of
gone past libusb-specific-related discussion, I thought I'd
add another question to the thread).

What's the rationale behind the dichotomy between userspace
and kernel licensing models?

mike

  reply	other threads:[~2006-03-06 21:10 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
2006-03-06 12:47         ` Re[2]: " s.schmidt
2006-03-06 17:05           ` Greg KH
2006-03-06 21:09             ` Michael Bender [this message]
2006-03-06 22:02               ` [Libusb-devel] " 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=440CA520.8070507@sun.com \
    --to=michael.bender@sun.com \
    --cc=greg@kroah.com \
    --cc=kkeil@suse.de \
    --cc=libusb-devel@lists.sourceforge.net \
    --cc=linux-kernel-owner@vger.kernel.org \
    --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