public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: License violation?
Date: Fri, 02 Mar 2007 01:36:06 +0100	[thread overview]
Message-ID: <45E77176.7070200@gmail.com> (raw)
In-Reply-To: <45E77073.1000208@goop.org>

Jeremy Fitzhardinge napsal(a):
> Jiri Slaby wrote:
>> 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.) 
> 
> 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,
-- 
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 <hnus@fi.muni.cz> is an alias for /dev/null

  reply	other threads:[~2007-03-02  0:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02  0:13 License violation? Jiri Slaby
2007-03-02  0:31 ` Jeremy Fitzhardinge
2007-03-02  0:36   ` Jiri Slaby [this message]
2007-03-02  0:37     ` Jeremy Fitzhardinge
2007-03-02  1:07       ` Jiri Slaby
     [not found]         ` <45E77931.5090005@goop.org>
2007-03-02  1:27           ` Jiri Slaby
2007-03-02 12:41       ` Alan
2007-03-02 20:43         ` Jiri Slaby
2007-03-02 21:18 ` David Schwartz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45E77176.7070200@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox