[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1202411113.15090.263.camel@violet>
Date: Thu, 07 Feb 2008 20:05:13 +0100
From: Marcel Holtmann <marcel@...tmann.org>
To: David Newall <davidn@...idnewall.com>
Cc: Pekka Enberg <penberg@...helsinki.fi>, Greg KH <greg@...ah.com>,
Christer Weinigel <christer@...nigel.se>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: mark USB drivers as being GPL only
Hi David,
> >>> I think you're missing my point: as long as the license stays the way
> >>> it is now, you can never distribute proprietary code unless you've
> >>> consulted a lawyer and even then you run the risk of being sued for
> >>> infringement if the copyright holder thinks what you have is derived
> >>> work.
> >>>
> >> Yes I can, if the proprietary code is not linked with GPL code (and the
> >> proprietary code is original). Loadable modules are not linked. This is a
> >> very clear-cut case.
> >>
> >
> > that is not clear-cut case. You link at run-time. Otherwise the module
> > would do nothing.
>
> That's why it's allowed. The module isn't linked when it's distributed,
> and the author doesn't do or cause the linking; the user does. And the
> user never distributes in the linked state. Distribution is key to GPL.
so how do you build this module that is not linked without using the
Linux kernel. Hence derivative work. Hence dynamic linking at runtime of
binary only code is violating the GPL.
Same goes for dynamic linking at runtime against GPL libraries. Nobody
thinks that is possible and ships binary applications that link against
GPL libaries. So why do you think you can distribute a binary only
kernel module.
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists