public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Gabucino <gabucino@mplayerhq.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pwc+pwcx is not illegal
Date: Sat, 28 Aug 2004 12:30:05 +0200	[thread overview]
Message-ID: <20040828103005.GA1841@ucw.cz> (raw)
In-Reply-To: <20040828081534.GA30353@mail.banki.hu>

On Sat, Aug 28, 2004 at 10:15:34AM +0200, Gabucino wrote:
> Guess GPL maniacs would have been happy, should avifile/MPlayer/xine never
> supported loading Win32 video+audio codecs. These players are probably
> considered non-GPL by Linus. Fine. Way to go, kernel developers.
> 
> Maybe you people should instead test release kernels at least with NFS before
> releasing. It's kinda basic feature, ya know.
> 
> Anyway, GPL only forbids _distribution_ of GPL+binary stuff, not the
> _possibility_ to use it. Time for Linus and Greg to come to their
> senses.

Loading binary modules is considered OK in the kernel in case the binary
module was implemented independently of the kernel.

So if the same logic was applied to mplayer and win32 codecs, then that
would be considered OK.

What is not considered OK is to develop a module with the sole intent to
use it with the kernel and then distribute it as binary only. While we
kernel developers can't do much about it, at least we don't support it
by allowing specific hooks for that.

In the case of pwc+pwcx, pwcx (the decoder module) is completely useless
without pwc (the driver module), and thus is obviously falling in the
second class described above.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2004-08-28 10:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-28  8:15 pwc+pwcx is not illegal Gabucino
2004-08-28 10:30 ` Vojtech Pavlik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-28 12:18 Kenneth Lavrsen
2004-08-28 13:11 ` Adrian Bunk
2004-08-28 15:24   ` Kenneth Lavrsen
2004-08-29 14:02   ` Alan Cox
2004-09-01 22:51     ` Rogier Wolff
2004-08-27 19:18 Albert Cahalan
2004-08-27 19:29 ` Linus Torvalds
2004-08-27 20:06   ` Kenneth Lavrsen
2004-08-27 20:21     ` Linus Torvalds
2004-08-27 20:24     ` David S. Miller
2004-08-27 20:26     ` Paul Jakma
2004-08-30 17:41       ` Brian Litzinger
2004-08-27 20:38     ` David Ford
2004-08-27 20:57   ` Albert Cahalan
2004-08-27 21:04     ` Greg KH
2004-08-27 21:09     ` Linus Torvalds
2004-08-29 14:00   ` Alan Cox
2004-08-29 16:33     ` Nemosoft Unv.
2004-08-29 15:42       ` Alan Cox
2004-08-29 17:16       ` Norbert van Nobelen
2004-08-27 19:34 ` Paulo Marques
2004-08-27 21:34   ` Albert Cahalan

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=20040828103005.GA1841@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=gabucino@mplayerhq.hu \
    --cc=linux-kernel@vger.kernel.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