All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: alsa-devel@alsa-project.org
Subject: Info needed for creative SB 0220 with STAC9758 codec, to get the REAR channels working.
Date: Sun, 02 May 2004 18:00:55 +0000	[thread overview]
Message-ID: <40953757.2080800@superbug.demon.co.uk> (raw)

Just for everyone's information.
I now have all the info I need to get the Rear channel working.
I thank Voluspa for giving me ssh root access so that I could find out 
the details via trial and error.

But the summary is: -
This tells the emu10k1 chip which slots to fill on the AC-LINK between 
the emu10k1 and the stac9758.
snd_emu10k1_ptr_write(emu, AC97SLOT, 0, XXX);

Where XXX is:
/* bit 0 is AC97SLOT_REAR_LEFT
  * bit 1 is AC97SLOT_REAR_RIGHT
  * bit 2 is Unknown, Maybe spdif. Not tested.
  * bit 3 is Unknown, Maybe spdif. Not tested.
  * bit 4 is AC97SLOT_CNTR
  * bit 5 is AC97SLOT_LFE
  */
So, for the stac9758, we would set XXX to  0x33

DSP code: -
OP(icode, &ptr, iACC3, EXTOUT(13)...   <- Rear Left
OP(icode, &ptr, iACC3, EXTOUT(14)...   <- Rear Right

Cheers
James


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click

             reply	other threads:[~2004-05-02 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-02 18:00 James Courtier-Dutton [this message]
     [not found] ` <409572D9.2070704@netzero.net>
     [not found]   ` <409573D9.6040101@superbug.demon.co.uk>
2004-05-03 23:49     ` alsa emu10k1 Francisco Moraes

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=40953757.2080800@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@alsa-project.org \
    /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.