From: Tobin Davis <tdavis@dsl-only.net>
Cc: alsa-devel@alsa-project.org, Eran Guendelman <erang@stanford.edu>
Subject: Re: probing state of high definition audio card in windows / SigmaTel STAC9221 microphone problems
Date: Fri, 08 Jun 2007 16:07:47 -0700 [thread overview]
Message-ID: <1181344067.5053.8.camel@razman.gruemaster.com> (raw)
In-Reply-To: <75b66ecd0706081524v6242f1adw1038dc27d015ab4d@mail.gmail.com>
For Sigmatel Codecs, this is correct. You need to look at the verb
tables in the inf file. Other HD Audio drivers have the verb tables
built into the driver, and the inf file just tells the driver which
table to use.
As to building a program to gather this information, I have actually
been thinking of adding a virtual hal to Xen that would imitate an HD
Audio bus. This way, I could see what the driver is doing, just by
running Windows in a virtual machine. I need to see if this violates
any reverse engineering regulations first.
Tobin
On Fri, 2007-06-08 at 18:24 -0400, Lee Revell wrote:
> On 6/8/07, Eran Guendelman <erang@stanford.edu> wrote:
> > So the question is, does anyone have a ready-made utility for Windows to
> > do this probe of the high definition audio codec? I could probably try
> > writing one myself, but thought I'd check if it already exists.
>
> I think it's just in the .inf file.
>
> Lee
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Tobin Davis <tdavis@dsl-only.net>
prev parent reply other threads:[~2007-06-08 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 10:36 probing state of high definition audio card in windows / SigmaTel STAC9221 microphone problems Eran Guendelman
2007-06-08 22:24 ` Lee Revell
2007-06-08 22:40 ` Eran Guendelman
2007-06-08 23:07 ` Tobin Davis [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=1181344067.5053.8.camel@razman.gruemaster.com \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@alsa-project.org \
--cc=erang@stanford.edu \
/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.