From: Dan Hollis <goemon@sasami.anime.net>
To: linux-sound@vger.kernel.org
Subject: Re: [linux-audio-dev] Re: 4D-NXs (was Re: Sync Issues)
Date: Thu, 28 Oct 1999 18:14:41 +0000 [thread overview]
Message-ID: <marc-linux-sound-94114192016211@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94114191816205@msgid-missing>
On Thu, 28 Oct 1999, Joe Miklojcik wrote:
> > > * "we think our hardware's proprietary secrets will be revealed
> > > if there is a source code driver"
> > Uh, isnt this what patents are for? If someone reverse engineers their
> > card, they are *completely screwed* unless they have patent protection.
> Shhh :) They haven't figured that out yet. It's the only thing saving us
> on a lot of the hardware Linux supports. I'm not a lawyer, but I think that
> they can deny the right to reverse engineer in a user license, which would
> make some drivers illegal.
So you reverse engineer them in a country where such shrinkwrap licenses
themselves are illegal. Isnt this most of europe? :)
Isnt there some precedent law in the US which basically says such licenses
are unenforceable?
-Dan
prev parent reply other threads:[~1999-10-28 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-28 18:08 [linux-audio-dev] Re: 4D-NXs (was Re: Sync Issues) Joe Miklojcik
1999-10-28 18:14 ` Dan Hollis [this message]
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=marc-linux-sound-94114192016211@msgid-missing \
--to=goemon@sasami.anime.net \
--cc=linux-sound@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