public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Hoogerhuis <alexh@ihatent.com>
To: Torgeir Veimo <torgeir@pobox.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: possible GPL violation by Sigma Designs
Date: 09 Sep 2003 17:05:50 +0200	[thread overview]
Message-ID: <87d6eahui9.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <1063117206.3569.39.camel@africa.netenviron.com>

Torgeir Veimo <torgeir@pobox.com> writes:

> Would writing a driver based on registers found by looking at the
> disassembled binary driver be considered a derivative work? Does it need
> to be done by a different person, acting as a proxy?
> 

Dunno, I've just read anough about it that I'd be careful looking at
the tray-table hinge on a flight through the US in case I'm
reverse-engineering a patented hinge by trying to understand how it
works ;)

> Torgeir Veimo <torgeir@pobox.com>

mvh,
A
-- 
Alexander Hoogerhuis                               | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE                          | +47 908 21 485
"You have zero privacy anyway. Get over it."  --Scott McNealy

  reply	other threads:[~2003-09-09 15:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08  1:49 possible GPL violation by Sigma Designs Torgeir Veimo
2003-09-08  8:25 ` Jose Luis Domingo Lopez
2003-09-08  8:45   ` Russell King
2003-09-08 12:33 ` Alan Cox
2003-09-08 12:46   ` Torgeir Veimo
2003-09-09  2:33     ` Torgeir Veimo
2003-09-09 13:49       ` Alexander Hoogerhuis
2003-09-09 14:20         ` Torgeir Veimo
2003-09-09 15:05           ` Alexander Hoogerhuis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-28 16:23 Iain Barker
2003-11-29  4:58 ` Benjamin Herrenschmidt

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=87d6eahui9.fsf@lapper.ihatent.com \
    --to=alexh@ihatent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torgeir@pobox.com \
    /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