Skip to contentSkip to conversation

Please open sysfs symbols to proprietary modules

DISCUSSION [email protected] 3 participants 3 messages Feb 17, 2005 – Feb 18, 2005

lore
Share & tools
lore
#0 lore raw
Quoted 7 lines · Arjan van de Ven
Quoted 5 lines · Pavel Roskin

Hello!

I'm writing a module under a proprietary license. I decided to use sysfs to do the configuration. Unfortunately, all sysfs exports are available to GPL modules only because they are exported by EXPORT_SYMBOL_GPL.

Quoted 5 lines

I suggest you talk to a lawyer and review the general comments about binary modules with him (http://people.redhat.com/arjanv/COPYING.modules
for example). You are writing an addition to linux from scratch, and it is generally not considered OK to do that in binary form (I certainly do not consider it OK).

So what about companies like ImageStream who write proprietary Linux network drivers for their hardware from scratch with no previous ports from another OS?

#1 lore raw
Quoted 10 lines · [email protected] wrote:
Quoted 5 lines · Arjan van de Ven

I suggest you talk to a lawyer and review the general comments about binary modules with him (http://people.redhat.com/arjanv/COPYING.modules
for example). You are writing an addition to linux from scratch, and it is generally not considered OK to do that in binary form (I certainly do not consider it OK).

So what about companies like ImageStream who write proprietary Linux network drivers for their hardware from scratch with no previous ports from another OS?

Obviously he doesn't consider that to be okay, and those companies are taking a risk that someone will take legal action against them.

Chris

#2 lore raw
In reply to [email protected]
Quoted 8 lines · On Thu, 2005-02-17 at 17:13 -0600, [email protected] wrote:
Quoted 7 lines · Arjan van de Ven
Quoted 5 lines · Pavel Roskin

Hello!

I'm writing a module under a proprietary license. I decided to use sysfs to do the configuration. Unfortunately, all sysfs exports are available to GPL modules only because they are exported by EXPORT_SYMBOL_GPL.

Quoted 8 lines
Quoted 5 lines

I suggest you talk to a lawyer and review the general comments about binary modules with him (http://people.redhat.com/arjanv/COPYING.modules
for example). You are writing an addition to linux from scratch, and it is generally not considered OK to do that in binary form (I certainly do not consider it OK).

So what about companies like ImageStream who write proprietary Linux network drivers for their hardware from scratch with no previous ports from another OS?

Note that "has a previous port" is not enough for me to consider a proprietary driver "ok".

Anyway you asked... if your description is accurate then yes I consider those modules (if they are distributed of course) a violation of the license of the code I contributed to the kernel.