All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Alex Austin <circuitsoft.alex@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Trying to get unsupported CODEC to work
Date: Fri, 12 Dec 2008 10:23:02 +0100	[thread overview]
Message-ID: <s5h1vwdd9xl.wl%tiwai@suse.de> (raw)
In-Reply-To: <53baa24a0812120054u6c605987seba0d3066b2d5fa7@mail.gmail.com>

At Fri, 12 Dec 2008 02:54:25 -0600,
Alex Austin wrote:
> 
> Shoot. The DAE-3 is a controller for a 5-CH Amplifier card driving speakers
> directly, but I still need the subwoofer output from the ALC888. I may be
> able to get by without the ALC using high-level inputs on the sub amp. Even
> without it, what do I need to do to enable the DAE-3? I'm comfortable in C,
> but I don't know ALSA much, if at all, yet.

The codec parser isn't present for DAE-3, and the generic parser
obviously doesn't work for it.  So, you need to create a new codec
parser such as other patch_*.c.


Takashi

> On Fri, Dec 12, 2008 at 1:02 AM, Takashi Iwai <tiwai@suse.de> wrote:
> 
> > At Thu, 11 Dec 2008 16:28:28 -0600,
> > Alex Austin wrote:
> > >
> > > HelloI have an MSI Media Live DIVA motherboard. It has an AMD SB600 HD
> > Audio
> > > controller, and two CODECs on the HDA bus.
> > >
> > > First is an ALC888
> > > Second is an Intersil DAE-3.
> >
> > The analog outputs on both codecs are really used at the same time?
> > Then it doesn't work right now.  Simply "not implemented".  And no
> > concrete plan to fix it yet.  This might require a fundamental
> > re-design.
> >
> >
> > Takashi
> >
> > >
> > > Two alsa-info outputs in different circumstances
> > >
> > http://www.alsa-project.org/db/?f=20c86e755fdbbdbc8761c8c2f4de76bce2ea0c11
> > >
> > http://www.alsa-project.org/db/?f=15c5e5eab0104622a84b2dd0df03f26c17c7242d
> > >
> > > Output of codecgraph with "modprobe hda-intel probe_mask=2"
> > > http://pastebin.com/f54b6a9b8
> > >
> > > What's the next step to get this supported?
> > > --
> > > - Alex Austin
> > > (651) 238-9273
> > >
> > > "...and then I visited Wikipedia ...and the next 8 hours are a blur."
> > > _______________________________________________
> > > Alsa-devel mailing list
> > > Alsa-devel@alsa-project.org
> > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> > >
> >
> 
> 
> 
> -- 
> - Alex Austin
> (651) 238-9273
> 
> "...and then I visited Wikipedia ...and the next 8 hours are a blur."
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 

  reply	other threads:[~2008-12-12  9:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 22:28 Trying to get unsupported CODEC to work Alex Austin
2008-12-11 23:55 ` stan
2008-12-12  0:05   ` Alex Austin
2008-12-12  7:02 ` Takashi Iwai
2008-12-12  8:54   ` Alex Austin
2008-12-12  9:23     ` Takashi Iwai [this message]
2008-12-12  9:29       ` Alex Austin
2008-12-12  9:32         ` Takashi Iwai
2009-11-05  9:15           ` Alex Austin
2009-11-05 10:21             ` Takashi Iwai
2009-11-05 10:27               ` Alex Austin
2009-11-05 10:47                 ` Takashi Iwai
2009-11-05 11:44                   ` Alex Austin
2009-11-05 12:13                     ` 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=s5h1vwdd9xl.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=circuitsoft.alex@gmail.com \
    /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.