From: Richard Samson <samson.richard@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Stephen Warren <swarren@nvidia.com>,
Nitin Daga <ndaga@nvidia.com>
Subject: Re: [PATCH] add new Fermi 5xx codec IDs to snd-hda
Date: Sat, 05 Mar 2011 14:08:13 +0100 [thread overview]
Message-ID: <1299330493.1921.3.camel@cartman.lan> (raw)
In-Reply-To: <s5hk4ggju9r.wl%tiwai@suse.de>
Le jeudi 03 mars 2011 à 12:52 +0100, Takashi Iwai a écrit :
> At Tue, 1 Mar 2011 09:45:54 -0800,
> Stephen Warren wrote:
> >
> > Richard Samson wrote at Tuesday, March 01, 2011 10:16 AM:
> > > Le mardi 01 mars 2011 à 08:40 -0800, Stephen Warren a écrit :
> > > > Richard Samson wrote at Tuesday, March 01, 2011 8:15 AM:
> > > > > Le lundi 28 février 2011 à 19:09 +0100, Takashi Iwai a écrit :
> > > > > > At Mon, 28 Feb 2011 18:56:20 +0100,
> > > > > > samson.richard@gmail.com wrote:
> > > > > > > As Stephen Warren said, a patch with full support of 5xx cards will be
> > > > > > > more useful.
> > > > > >
> > > > > > OK, Stephen, could you prepare the patch including all missing IDs?
> > > > >
> > > > > I wrote an new patch with three new codec IDs for Nvidia Fermi cards.
> > > > > I attended to use existing IDs and online technical specifications to
> > > > > get two others cards :
> > > > > - Nvidia GeForce GTX 470 : id = 0x10de0015
> > > > > - Nvidia GeForce GTX 560 Ti : id = 0x10de0016 (works fine)
> > > > > - Nvidia GeForce GTX 570 : id = 0x10de0017
> > > >
> > > > They don't appear to match our Windows driver. Where did you get the values
> > > > from? (0x17 isn't in the Windows driver at all. 0x15 shouldn't be a GTX 470)
> > >
> > > I ask to a reseller, it seems a bad idea.
> >
> > The only way to find the values that I know of would be to plug the card
> > in, run Linux, and look at the ALSA /proc files. (Perhaps there's some
> > equivalent tool under Windows)
> >
> > > If I can help, where are these values in the Windows driver ?
> >
> > They encoded into the binary. I doubt they're user-accessible.
> >
> > So, I think the best way to proceed is for you to modify your patch to add
> > IDs 0x15 and 0x16 only. I'm pretty sure ID 0x17 isn't assigned to anything.
> > Let's not remove any NVIDIA IDs even though I'm pretty sure a couple aren't
> > actually assigned; if I'm wrong, we'd just have to add them back later, and
> > having them in won't harm anything.
>
> OK, I modified Richard's patch to get rid of 0x17 and merged now
> to sound git tree.
>
>
> thanks,
>
> Takashi
Hello,
Thank you for this commit.
Richard Samson
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2011-03-05 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 1:10 [PATCH] add new Fermi 5xx codec IDs to snd-hda Richard Samson
2011-02-28 17:13 ` Stephen Warren
2011-02-28 17:21 ` Takashi Iwai
2011-02-28 17:56 ` samson.richard
2011-02-28 18:09 ` Takashi Iwai
2011-03-01 15:14 ` Richard Samson
2011-03-01 16:40 ` Stephen Warren
2011-03-01 17:16 ` Richard Samson
2011-03-01 17:45 ` Stephen Warren
2011-03-03 11:52 ` Takashi Iwai
2011-03-05 13:08 ` Richard Samson [this message]
2011-02-28 17:19 ` Takashi Iwai
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=1299330493.1921.3.camel@cartman.lan \
--to=samson.richard@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ndaga@nvidia.com \
--cc=swarren@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).