Skip to contentSkip to conversation

Please open sysfs symbols to proprietary modules

DISCUSSION Jonathan A. George 2 participants 2 messages Feb 3, 2005 – Feb 4, 2005

lore
Share & tools
lore
#0 lore raw

<snip>

Quoted 1 line

...The EXPORT_SYMBOL_GPL is a license statement to binary module developers...

<snip>

As noted repeatedly a symbol prefix doesn't appear to carry any legal weight under U.S. law. In fact the GPL copyright notice is appear legally limited to the granting of *copy* *rights* per U.S. copyright law and specifically does _not_ appear to implicitly or explicitly create the kind of exceptions you seem to be looking for.

Quoted 3 lines

The one major stumbling block is that any code that imports symbols that are exported via "EXPORT_SYMBOL_GPL" can only legally _export_ symbols using the same, for the reason I stated above.

The GPL as a *copy* *right* notice can apparently only apply obviously derivative works under U.S. law, and an independent driver created for a different OS is obviously _not_ a derivative work. Basically the attempt to create such a distinction does not appear to be supported by U.S. law as applied to the GPL.

Quoted 2 lines

If it's a non-GPL module it _cannot_ legally use EXPORT_SYMBOL_GPLed symbols, either directly or indirectly, under any circumstances.

Actually you can probably use any symbols you want since only the glue layer to the OS independent driver is would appear derivative of Linux, and since the glue layer appears to be derivative of two *independent* works (the OS and the Driver when done this way) you might need to license the glue layer in a way which is compatible with both works. The current BSD license could be a good choice in this instance.

** As noted previously it would be interested to see the opinion of a U.S. IP lawyer who has conclusively tested the impact of copy right law where the boundary of what constitutes a derivative work was explicitly stated by a federal judge.

-----------------

P.S. Consider a kernel module which allows the use of a binary only MS-Windows driver in its unmodified stated. Could you actually consider the MS-Windows driver to be a derivative work of the Linux kernel by virtue of an intermediate glue module which was BSD licensed and made free use of all symbols? Would the Linux kernel be considered a derivative work of your motherboards firmware? These seem rather unlikely conclusions.

#1 lore raw
Quoted 6 lines · Jonathan A. George

...
** As noted previously it would be interested to see the opinion of a U.S. IP lawyer who has conclusively tested the impact of copy right law where the boundary of what constitutes a derivative work was explicitly stated by a federal judge.
...

Why is only the opinion of an US lawyer important?

E.g. if you distribute something in Germany and a German kernel developer thinks the code you distribute violates the licence of a part of the kernel he has the copyright on German copyright law applies - and German copyright law is quite different from US copyright law.

cu
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed