From: "Jared D. McNeill" <jared.mcneill@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel@lists.sourceforge.net, jmcneill@netbsd.org
Subject: Re: intel8x0m and conexant ac97 modem codecs
Date: Tue, 12 Apr 2005 15:14:53 -0300 [thread overview]
Message-ID: <41d6f0b905041211143edfd71e@mail.gmail.com> (raw)
In-Reply-To: <1113329101.31159.23.camel@mindpipe>
On Apr 12, 2005 3:05 PM, Lee Revell <rlrevell@joe-job.com> wrote:
> On Tue, 2005-04-12 at 13:05 -0300, Jared D. McNeill wrote:
> > Hi folks, not sure if this is the right place to ask but I might as
> > well give it a shot anyway --
> >
> > I'm working on adding AC97 modem support to NetBSD, and I have run
> > into a stumbling block. From what I've read, it looks like Conexant
> > AC97 modem codecs aren't supported by the ALSA intel8x0m / slmodem
> > solution. What are the technical reasons for this?
>
> Do you know if any open source driver ever existed for these? "Lack of
> documentation" is the obvious suspect...
I was under the impression that all AC97 modem codecs were supposed to
work the same (as in, use them as the AC97 spec says to). The NetBSD
driver appears to be working for non-Conexant codecs, but I can't get
a Conexant chip to power up through the same initialization routine.
ac97_read(as, AC97_REG_EXT_MODEM_CTRL, ®) always returns 0xff00
("everything powered down" in the AC97 modem world) on the few
variations of Conexant codecs we've tried.
"Lack of documentation" is most likely the reason; I guess I was just
looking for confirmation from another group that either "Yes, these
chips are broken, we don't support them because we don't have any
documentation", or "Yes, these chips are broken, we had to work around
the problem by doing foo".
Meanwhile, I'm still working on getting some useful documentation from
Conexant..
Cheers,
Jared
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-04-12 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 16:05 intel8x0m and conexant ac97 modem codecs Jared D. McNeill
2005-04-12 18:05 ` Lee Revell
2005-04-12 18:14 ` Jared D. McNeill [this message]
[not found] ` <20050413212806.GB1096@tecr>
2005-04-13 22:53 ` Jared D. McNeill
[not found] ` <20050414103910.GA12914@tecr>
2005-04-22 12:30 ` Jared D. McNeill
2005-04-14 0:33 ` Jared D. McNeill
2005-04-12 18:17 ` Peter Zubaj
2005-04-12 18:22 ` Jared D. McNeill
2005-04-12 18:42 ` Peter Zubaj
2005-04-12 18:44 ` Jared D. McNeill
[not found] ` <20050413213717.GC1096@tecr>
2005-04-13 22:55 ` Jared D. McNeill
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=41d6f0b905041211143edfd71e@mail.gmail.com \
--to=jared.mcneill@gmail.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jmcneill@netbsd.org \
--cc=rlrevell@joe-job.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.