06-25-2008 12:16 PM
06-26-2008 01:36 AM
08-11-2008 03:39 PM
08-12-2008 03:37 AM
09-15-2008 05:29 AM
This problem will not go away, as the NI driver with a GPL-incompatible license uses kernel symbols that are marked usable only by GPL licensed code. The error the OP sees is to stop a license violation. According to the commit (more than 6 months ago now)
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=782e70c6fc2290a0395850e8e02583b8b62264d8
"Over two years ago, the Linux USB developers stated that they believed
there was no way to create a USB kernel driver that was not under the
GPL. This patch moves the USB apis to enforce that decision."
So even in 2006 the NIKAL module already violated the license as it was understood by the Linux kernel developers, even though it was not yet enforced.
Which leads to the following question: Why is this NIKAL module necessary at all? It seems to me that libusb allows all of this to be done in userspace, without requiring any kernel modules at all.
04-04-2017 10:42 PM
@cryotak wrote:
If you were to look in the right C file(s), I believe it may be called nikal.c, and change the definition of the MODULE_LICENSE variable from the NI blurb to "GPL", then that may fool the installation process into thinking that the software is actually GPL and not some encumbered piece of NI software.
That would be an direct and intentional license infringement, thus terminating the license immediately. NI then would loose the right to use the Linux kernel as a whole.
Seems they just decided just killing any Linux support for their usb devices (at least legally correct).
Looks like few pieces of information on how to talk to these devices must be some military-level secret, as important as nuclear launch keys, so they don't even dare to hand out libusb-based userland driver binaries ...