public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Craig Milo Rogers <rogers@isi.edu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Xavier Bestel <xavier.bestel@free.fr>,
	Christoph Hellwig <hch@infradead.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	webcam@smcc.demon.nl
Subject: Re: Termination of the Philips Webcam Driver (pwc)
Date: Fri, 27 Aug 2004 11:55:41 -0700	[thread overview]
Message-ID: <20040827185541.GC24018@isi.edu> (raw)
In-Reply-To: <Pine.LNX.4.58.0408271106330.14196@ppc970.osdl.org>

On 04.08.27, Linus Torvalds wrote:
> But Greg is right - we don't keep hooks that are there purely for binary
> drivers. If somebody wants a binary driver, it had better be a whole
> independent thing - and it won't be distributed with the kernel.

	If you read Nemosoft's final driver release (which has been
reposted, and of which I now have a copy), you can see that he was
rewriting his code to move the proprietary codecs out of the kernel
entirely, and into user-mode libraries to be linked with consenting
applications -- he was quite sensitive to the kernel issues involved.
Of course, this is still nowhere as good as a wholly open source
solution, a position with which I think Nemosoft concurs, based on his
messages.

	Linus, would you adress a moot issue, please?  If Nemosoft (or
someone else) were to release some of the codecs in question as one or
more open-source loadable kernel modules (similar to sound card
support modules in the ALSA system), while other codecs remain
binary-only loadable kernel modules (distributed outside the kernel,
but using the same hook as the open-source loadable modules), would
the pwc driver and codec extension hook be allowable, in your opinion,
please?

					Craig Milo Rogers

  reply	other threads:[~2004-08-27 18:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 23:32 Termination of the Philips Webcam Driver (pwc) Craig Milo Rogers
2004-08-26 23:47 ` Christoph Hellwig
2004-08-27  0:03   ` Linus Torvalds
2004-08-27  8:43     ` Christoph Hellwig
2004-08-27  9:48       ` Craig Milo Rogers
2004-08-27 17:28       ` Linus Torvalds
2004-08-27 17:37         ` Xavier Bestel
2004-08-27 18:13           ` Linus Torvalds
2004-08-27 18:55             ` Craig Milo Rogers [this message]
2004-08-27 19:06               ` Linus Torvalds
2004-08-27 19:34                 ` Jeff Garzik
2004-08-27 21:42                 ` Nemosoft Unv.
2004-08-27 22:49                   ` Marek Habersack
2004-08-27 23:40                     ` Dmitry Torokhov
2004-08-28 17:42                       ` Pavel Machek
2004-08-27 23:04                   ` Craig Milo Rogers
2004-08-27 21:59                 ` non-i386 architectures (Re: Termination of the Philips Webcam Driver (pwc)) Daniel Egger
2004-08-27 19:06               ` Termination of the Philips Webcam Driver (pwc) Martin J. Bligh
2004-08-27 19:12             ` Alex Belits
2004-08-27 21:36             ` Anton Altaparmakov
2004-08-27 21:42               ` Anton Altaparmakov
2004-08-27 22:26                 ` Geert Uytterhoeven
2004-08-27 21:52               ` Linus Torvalds
2004-08-27 22:22                 ` Jeff Garzik
2004-08-28  0:45                   ` Paul Jakma
2004-08-28  0:53                     ` Craig Milo Rogers
2004-08-28 10:29             ` Norbert van Nobelen
2004-08-29 14:37         ` Alan Cox
2004-08-28  9:26     ` chris
2004-08-29 14:41       ` Alan Cox
2004-08-29 14:36     ` Alan Cox
2004-08-29 18:09       ` Linus Torvalds
2004-08-29 18:57         ` Alan Cox
2004-08-29 19:40         ` Greg KH
2004-08-30  9:35         ` Craig Milo Rogers
  -- strict thread matches above, loose matches on Subject: below --
2004-08-27 10:14 Koos Vriezen
2004-08-27 11:03 ` Marcus Metzler
2004-08-28  2:16 lkml-mail
2004-08-28  5:30 ` 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=20040827185541.GC24018@isi.edu \
    --to=rogers@isi.edu \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=webcam@smcc.demon.nl \
    --cc=xavier.bestel@free.fr \
    /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