From: Dave Airlie <airlied@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Greg KH <greg@kroah.com>, Lee Revell <rlrevell@joe-job.com>,
Mark Fortescue <mark@mtfhpc.demon.co.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Can't use SYSFS for "Proprietry" driver modules !!!.
Date: Mon, 28 Mar 2005 08:41:43 +1000 [thread overview]
Message-ID: <21d7e99705032714417148217f@mail.gmail.com> (raw)
In-Reply-To: <1111948631.27594.14.camel@localhost.localdomain>
> > How about the fact that when you load a kernel module, it is linked into
> > the main kernel image? The GPL explicitly states what needs to be done
> > for code linked in.
> >
> I've always wondered about dynamically loaded modules (and libraries for
> that matter). The standard IANAL, but I've talked to many to try to
> understand what is really legal, and I usually come up with the
> conclusion, it's just an interpretation of the law by the judge.
>
> If the user is loading the module (or library) and the distributer
> doesn't, then is the the user breaking the license and not the
> distributer?
I think this is probably what the lawyers are telling the graphics
card companies at the moment, the GPL is broken by the act of linking
and at what stage is the link considered to have happened, so if I
distribute a GPL or BSD licensed stub layer in source form, a big
binary blob that doesn't use any kernel interfaces except my stub
layer ones, and never distribute any of it with a kernel or linked
into anything, am I breaking the GPL on the kernel? all I'm doing is
releasing some source code and some binary image files, the user is
doing the linking by loading my code into their running kernel and
I'm not distributing my code with the kernel...
It'll be an interesting day in court... and maybe then derived work
will become nicely defined at least for one country....
Dave.
next prev parent reply other threads:[~2005-03-27 22:41 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 17:52 Can't use SYSFS for "Proprietry" driver modules !!! Mark Fortescue
2005-03-26 18:28 ` Greg KH
2005-03-26 20:34 ` Lee Revell
2005-03-26 20:46 ` Jan Engelhardt
2005-03-27 0:48 ` Greg KH
[not found] ` <1111885480.1312.9.camel@mindpipe>
2005-03-27 3:20 ` Greg KH
2005-03-27 3:30 ` Lee Revell
2005-03-27 18:10 ` Greg KH
2005-03-27 18:37 ` Steven Rostedt
2005-03-27 22:01 ` Adrian Bunk
2005-03-27 23:54 ` Steven Rostedt
2005-03-28 1:39 ` Adrian Bunk
2005-03-28 1:50 ` Steven Rostedt
2005-03-28 9:31 ` Jan Engelhardt
2005-03-28 14:45 ` Adrian Bunk
2005-03-27 22:41 ` Dave Airlie [this message]
2005-03-28 0:53 ` Chris Wedgwood
2005-03-27 15:04 ` Alan Cox
2005-03-28 3:56 ` Clemens Schwaighofer
2005-03-29 2:37 ` Coywolf Qi Hunt
2005-03-29 5:58 ` Jim Crilly
2005-03-28 16:52 ` Mark Fortescue
2005-03-28 18:38 ` Rik van Riel
2005-03-29 3:36 ` Greg KH
2005-03-29 6:17 ` Kevin Puetz
2005-03-27 12:42 ` Sean
2005-03-27 13:53 ` Wichert Akkerman
2005-03-27 15:06 ` Alan Cox
2005-03-28 13:12 ` Geert Uytterhoeven
2005-03-29 3:41 ` Lee Revell
2005-03-29 1:53 ` David Schwartz
2005-03-29 2:06 ` Kyle Moffett
2005-03-29 19:00 ` David Schwartz
2005-03-30 14:15 ` Olivier Galibert
2005-04-02 2:11 ` David Schwartz
2005-03-27 20:50 ` James Courtier-Dutton
-- strict thread matches above, loose matches on Subject: below --
2005-03-27 1:15 Aaron Gyes
2005-03-27 1:29 ` Lee Revell
2005-03-27 2:55 ` Kyle Moffett
2005-03-27 8:57 ` Jan Engelhardt
2005-03-27 17:09 ` Willy Tarreau
[not found] ` <1111913399.6297.28.camel@laptopd505.fenrus.org>
2005-03-27 17:40 ` Kyle Moffett
2005-03-27 17:52 ` Dave Airlie
2005-03-27 17:58 ` Kyle Moffett
2005-03-27 18:04 ` Dr. David Alan Gilbert
2005-03-27 18:35 ` Adrian Bunk
2005-03-27 18:46 ` Jan Engelhardt
2005-03-27 19:16 ` Aaron Gyes
2005-03-27 19:30 ` Kyle Moffett
2005-03-28 1:54 ` Horst von Brand
2005-03-28 9:27 ` Jan Engelhardt
2005-03-28 12:04 ` Steven Rostedt
2005-03-28 13:12 ` linux-os
2005-03-28 13:46 ` Steven Rostedt
2005-03-28 14:50 ` Jan Engelhardt
[not found] ` <1112016850.6003.13.camel@laptopd505.fenrus.org>
2005-03-28 13:57 ` Steven Rostedt
2005-03-28 23:43 ` Paul Jackson
2005-03-29 0:21 ` Steven Rostedt
2005-03-29 0:56 ` Kyle Moffett
2005-03-29 1:27 ` Steven Rostedt
2005-03-29 12:15 ` linux-os
2005-03-29 12:29 ` Sean
2005-03-30 19:47 ` Rik van Riel
2005-03-30 19:57 ` linux-os
2005-03-31 11:35 ` Sean
2005-03-31 12:34 ` linux-os
2005-03-31 14:20 ` Sean
2005-03-31 22:55 ` Kyle Moffett
2005-03-30 23:30 ` John Pearson
2005-04-03 14:07 ` Clemens Schwaighofer
2005-03-29 16:31 ` Horst von Brand
2005-03-30 14:38 ` Olivier Galibert
2005-03-30 19:49 ` Rik van Riel
2005-03-29 1:22 ` Paul Jackson
2005-03-29 1:31 ` Steven Rostedt
2005-03-28 20:47 ` Horst von Brand
2005-03-27 19:37 ` Adrian Bunk
2005-03-27 21:22 ` Diego Calleja
2005-03-27 23:09 ` Greg KH
2005-03-28 13:14 ` Geert Uytterhoeven
2005-03-27 18:12 ` Greg KH
2005-03-29 1:04 ` Aaron Gyes
2005-03-29 3:33 ` Greg KH
2005-03-29 4:03 ` Zan Lynx
2005-03-29 4:44 ` Greg KH
2005-04-03 23:41 ` Mark Lord
2005-04-04 4:01 ` Paul Jackson
2005-04-04 7:15 ` Christoph Hellwig
2005-03-29 4:28 ` Aaron Gyes
2005-03-29 4:45 ` Greg KH
2005-03-29 5:01 ` Aaron Gyes
2005-03-29 5:05 ` Greg KH
2005-03-29 5:29 ` Aaron Gyes
2005-03-29 5:37 ` Brian Gerst
2005-03-27 5:20 Chuck Ebbert
2005-03-27 7:21 Manfred Spraul
2005-03-28 1:03 Albert Cahalan
2005-03-28 2:04 Aaron Gyes
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=21d7e99705032714417148217f@mail.gmail.com \
--to=airlied@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=rlrevell@joe-job.com \
--cc=rostedt@goodmis.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