Skip to contentSkip to conversation

License violation?

DISCUSSION Jiri Slaby 4 participants 9 messages Mar 2, 2007 1 message not in the archive

lore
Share & tools
lore

Jiri Slaby

author
#0 lore raw

Hi.

I have a GPL driver (written by me) with workarounds, since I hadn't know-how, when I wrote it. Now I've got 2.4 proprietary driver from the vendor. Is use of the 2.4 driver know-how OK? (And could be such driver merged?)

These are lines from the proprietary driver:
IMPORTANT SAFETY & LEGAL INFORMATION:

This source file is provided as part of the SensAble Technologies PDD/GHOST Software Development Toolkit in order to facilitate the use of PCI-based PHANToM haptic interface devices across various Linux kernel revisions. It is meant to be recompiled without modification. It should NOT be modified in any way. Any modification of this source code will void any and all software and/or hardware warranties and maintenance agreements with SensAble Technologies or its assignees. Furthermore, modification of this source file may result in the damage or failure of the user's hardware. SensAble Technologies and its assignees assume no responsibility for any damage or injury resulting from the modification of this file.

It's obvious, that if somebody was using the GPL driver, he'll lost warranty et al. (But this is not the question.)

thanks,

Signature · 6 lines
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

Hnus <[email protected]> is an alias for /dev/null
#1 lore raw
Quoted 24 lines · Jiri Slaby

Hi.

I have a GPL driver (written by me) with workarounds, since I hadn't know-how, when I wrote it. Now I've got 2.4 proprietary driver from the vendor. Is use of the 2.4 driver know-how OK? (And could be such driver merged?)

These are lines from the proprietary driver:
IMPORTANT SAFETY & LEGAL INFORMATION:

This source file is provided as part of the SensAble Technologies PDD/GHOST Software Development Toolkit in order to facilitate the use of PCI-based PHANToM haptic interface devices across various Linux kernel revisions. It is meant to be recompiled without modification. It should NOT be modified in any way. Any modification of this source code will void any and all software and/or hardware warranties and maintenance agreements with SensAble Technologies or its assignees. Furthermore, modification of this source file may result in the damage or failure of the user's hardware. SensAble Technologies and its assignees assume no responsibility for any damage or injury resulting from the modification of this file.

Quoted 2 lines

It's obvious, that if somebody was using the GPL driver, he'll lost warranty et al. (But this is not the question.)

Seems reasonable to me. This isn't license text. They're not saying
you can't modify it; they're just saying you own the pieces if you modify it and break it. Is there an actual license?

J

author
#2 lore raw

Jeremy Fitzhardinge napsal(a):

Quoted 25 lines
Quoted 24 lines · Jiri Slaby

Hi.

I have a GPL driver (written by me) with workarounds, since I hadn't know-how, when I wrote it. Now I've got 2.4 proprietary driver from the vendor. Is use of the 2.4 driver know-how OK? (And could be such driver merged?)

These are lines from the proprietary driver:
IMPORTANT SAFETY & LEGAL INFORMATION:

This source file is provided as part of the SensAble Technologies PDD/GHOST Software Development Toolkit in order to facilitate the use of PCI-based PHANToM haptic interface devices across various Linux kernel revisions. It is meant to be recompiled without modification. It should NOT be modified in any way. Any modification of this source code will void any and all software and/or hardware warranties and maintenance agreements with SensAble Technologies or its assignees. Furthermore, modification of this source file may result in the damage or failure of the user's hardware. SensAble Technologies and its assignees assume no responsibility for any damage or injury resulting from the modification of this file.

Quoted 6 lines
Quoted 2 lines

It's obvious, that if somebody was using the GPL driver, he'll lost warranty et al. (But this is not the question.)

Seems reasonable to me. This isn't license text. They're not saying
you can't modify it; they're just saying you own the pieces if you modify it and break it. Is there an actual license?

No other text in there, but simple Copyright:

/* Copyright (c) 1997-2002 Sensable Technologies, Inc.
All rights reserved.

Aha, I've read it second time, and I get the point now.

regards,

Signature · 6 lines
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

Hnus <[email protected]> is an alias for /dev/null
#3 lore raw
Quoted 4 lines · Jiri Slaby

No other text in there, but simple Copyright:

/* Copyright (c) 1997-2002 Sensable Technologies, Inc.
All rights reserved.

Well, I think that means you can use info from that file to make your's better, but you can't copy actual code.

J

author
#4 lore raw

Jeremy Fitzhardinge napsal(a):

Quoted 8 lines
Quoted 4 lines · Jiri Slaby

No other text in there, but simple Copyright:

/* Copyright (c) 1997-2002 Sensable Technologies, Inc.
All rights reserved.

Well, I think that means you can use info from that file to make your's better, but you can't copy actual code.

Nice to hear this, thanks,

Signature · 6 lines
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

Hnus <[email protected]> is an alias for /dev/null
author
#6 lore raw
In reply to a message not in the archive

Jeremy Fitzhardinge napsal(a):

Quoted 5 lines
Quoted 1 line · Jiri Slaby

Nice to hear this, thanks,

Don't take it as legal advice. If you have any agreements with the provider of the proprietary driver, you should check with them or a lawyer.

After digging through the whole e-mail from person, who gave me a note to 2.4 driver source, I found this out:

Quoted 2 lines

However, we provide source code for PCI kernel driver (attached) so that customers can update it for 2.6 kernel.

I think, it would be no problem in that case.

regards,

Signature · 6 lines
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

Hnus <[email protected]> is an alias for /dev/null
#7 lore raw
In reply to Jeremy Fitzhardinge
Quoted 8 lines · On Thu, 01 Mar 2007 16:37:45 -0800 Jeremy Fitzhardinge <[email protected]> wrote:
Quoted 4 lines · Jiri Slaby

No other text in there, but simple Copyright:

/* Copyright (c) 1997-2002 Sensable Technologies, Inc.
All rights reserved.

Well, I think that means you can use info from that file to make your's better, but you can't copy actual code.

Have you tried asking them ?

author
#8 lore raw

Alan napsal(a):

Quoted 11 lines
Quoted 7 lines · On Thu, 01 Mar 2007 16:37:45 -0800 Jeremy Fitzhardinge <[email protected]> wrote:
Quoted 4 lines · Jiri Slaby

No other text in there, but simple Copyright:

/* Copyright (c) 1997-2002 Sensable Technologies, Inc.
All rights reserved.

Well, I think that means you can use info from that file to make your's better, but you can't copy actual code.

Have you tried asking them ?

Unfortunately with no reply so far. Maybe something will arrive next week.

regards,

Signature · 6 lines
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

Hnus <[email protected]> is an alias for /dev/null
#9 lore raw
In reply to Jiri Slaby
Quoted 6 lines

I have a GPL driver (written by me) with workarounds, since I hadn't know-how,
when I wrote it. Now I've got 2.4 proprietary driver from the vendor. Is use of
the 2.4 driver know-how OK? (And could be such driver merged?)

Unless you made some kind of agreement with the copyright holder or did not lawfully acquire the software, you have every right to study it and learn from it. You have every right to use your own knowledge to implement a driver any way you want.

What you can't do, of course, is steal protected expression from the driver. Function is not protected. Facts are not protected.

DS