All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Witzel <witzel.thomas@comcast.net>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Programming the unknow P16v chip on the Audigy2
Date: Tue, 1 Jun 2004 15:15:28 -0500	[thread overview]
Message-ID: <200406011515.34504.witzel.thomas@comcast.net> (raw)
In-Reply-To: <40B789D7.8060704@superbug.demon.co.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 28 May 2004 01:49 pm, James Courtier-Dutton wrote:
> Basically, one writes the register address to PTR, and then read or
> write to DATA.
>
> On the Audigy2 there is a similar setup for 0x20 and 0x24. I suspect
> that this is used to program the p16v chip.
I guess that is correct. 
> Had anyone looked into those registers, and tried to guess what they do ?
With virtually no information this would be difficult. It seems like that 
playback over the P16V would be an easier goal than getting the inputs
to work, but I have no idea how to make a PCM extension for the P16V.
The routing diagram shown on the kX webpage indicates that there should be 
direct playback not using the 10k2 at all. They have made a special effects 
module which allows input coming through the P16V to be routed into the 10k2,
but normally there doesn't seem to be a connection.

												Thomas

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAvOPkErlRqeo9RVURAtmxAJ4tgZDpge2ccMwlbXiwuEuTMewzvQCfdYJo
cg5An6CWYX9ari21NEVgGug=
=+WsE
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504

      reply	other threads:[~2004-06-01 20:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 18:49 Programming the unknow P16v chip on the Audigy2 James Courtier-Dutton
2004-06-01 20:15 ` Thomas Witzel [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=200406011515.34504.witzel.thomas@comcast.net \
    --to=witzel.thomas@comcast.net \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.