From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Ian Forde <ian@duckland.org>, alsa-devel@lists.sourceforge.net
Subject: Re: Broken nforce3 support in ALSA on amd64?
Date: Mon, 07 Mar 2005 20:11:49 -0500 [thread overview]
Message-ID: <1110244309.1183.25.camel@mindpipe> (raw)
In-Reply-To: <s5hfyz7us6w.wl@alsa2.suse.de>
On Mon, 2005-03-07 at 21:17 +0100, Takashi Iwai wrote:
> At Mon, 07 Mar 2005 15:06:05 -0500,
> Lee Revell wrote:
> IMO, the reverse-engineering is not the first thing to do.
> The h/w vendors don't want to open their specs -- unless the manager
> realizes that many users want it in the world. So, crying out loudly
> to the h/w vendors would be the first. I don't think it's been done
> quite enough yet in this case. AFAIK, Nvidia guys don't know that the
> problem exists at all.
>
Good point. Although Nvidia's position on opening their drivers is well
known, their engineers have definitely helped open source developers
before. Someone should really ask them, and post the results here.
> BTW, off-topic: is the reverse-engineering allowed in US, too?
>
AIUI it's generally prohibited by the DMCA but there is an explicit
exception that allows reverse engineering for the purpose of creating
interoperable software. The intention was to prevent people from using
the anti-reverse engineering provisions to implement vendor lock-in.
IANAL, in fact all my legal knowledge comes from LKML and slashdot, but
I have interpreted this to mean that reverse engineering Windows drivers
to make Linux drivers is fair game.
Maybe the US courts will find one day that I don't have a right to write
a Linux driver for a device I paid for. But until that happens, I am
not worried.
Any US lawyers on this list?
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-08 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 1:45 Broken nforce3 support in ALSA on amd64? Ian Forde
2005-03-07 13:31 ` Takashi Iwai
2005-03-07 20:06 ` Lee Revell
2005-03-07 20:17 ` Takashi Iwai
2005-03-08 1:11 ` Lee Revell [this message]
2005-03-08 5:45 ` Ian Forde
2005-03-08 11:43 ` Takashi Iwai
2005-03-10 4:40 ` Ian Forde
-- strict thread matches above, loose matches on Subject: below --
2005-02-27 1:47 Ian Forde
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=1110244309.1183.25.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ian@duckland.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.