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 15:06:05 -0500 [thread overview]
Message-ID: <1110225967.935.12.camel@mindpipe> (raw)
In-Reply-To: <s5hr7irwpjf.wl@alsa2.suse.de>
On Mon, 2005-03-07 at 14:31 +0100, Takashi Iwai wrote:
> Unfortunately, the datasheet of nforce is not available at all, so we
> have no chance to fix this problem yet unless you do some reverse
> engineering (but I never recommend to do that, it's a waste of time).
Do you mean reverse engineering Nvidia drivers, or RE in general? If
it's the latter I have to disagree strongly. It't not fast or easy, but
many ALSA drivers have gained useful features this way.
I strongly encourage reverse engineering proprietary drivers. Look at
what James did with the Audigy LS. And look how much is known about the
EMU DSP instruction set, all that info is reverse engineered.
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-07 20:06 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 [this message]
2005-03-07 20:17 ` Takashi Iwai
2005-03-08 1:11 ` Lee Revell
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=1110225967.935.12.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.