Re: [PATCH 0/2] module: Block modules by Tuxedo from accessing GPL symbols

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Am 15.11.24 um 11:22 schrieb Greg KH:
On Fri, Nov 15, 2024 at 10:40:56AM +0100, Werner Sembach wrote:
Am 15.11.24 um 10:18 schrieb Greg KH:
On Fri, Nov 15, 2024 at 10:00:23AM +0100, Werner Sembach wrote:
I guess what I try to convince you and others is that we _are_ taking Open
Source licenses seriously, but still there are mistakes to be made,
especially with complex projects like the Linux kernel, e.g. I'm not aware
of any other project that uses a similar construct to
EXPORT_SYMBOL_GPL()/MODULE_LICENSE().
The Linux kernel is very simple from a license point of view, your code
has to be GPLv2 compatible.  That's it, nothing complex or odd about
that at all.
Then why does the proprietary NVIDIA driver exist?
You will have to discuss that with that company's lawyers.  That was
their business decision to make, and in my opinion, the contracts they
wrote around that thing were a mastery of license law in "how to pass
the liability onto someone else."
But you see where there is complexity, and where my misconception stems from?

Luckily we now have open drivers for almost all of that hardware, so
it's not so much of an issue anymore.

Again, talk about this with your company lawyers, they can explain it
all much better than I can.

thanks,

greg k-h




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux