From: Takashi Iwai <tiwai@suse.de>
To: ANDREI LAHUN <zhirnyi@yahoo.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Patch for ali5451 (ATI IGP chipset) "ali_codec_ready: codec is not ready"
Date: Mon, 07 Apr 2003 17:30:19 +0200 [thread overview]
Message-ID: <s5hwui6qq9g.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030329162502.21778.qmail@web21512.mail.yahoo.com>
At Sat, 29 Mar 2003 08:25:02 -0800 (PST),
ANDREI LAHUN wrote:
>
> [1 <text/plain; us-ascii (7bit)>]
> Hello.
> Since i bought new laptop (Packard bell igo 3xxx) (ATI
> IGP chipset, ALI 5451 sound) i had a problems with a
> sound .Trident from OSS worked but quality was not
> good. Alsa always hunged with messages (during
> modprobe) -
> "ali_codec_ready: codec is not ready" all over the
> place. Finally i found a fix - to make it work like in
> trident OSS driver. For me now alsa works perfectly
> in native mode and in OSS emulation. Thank u for great
> drivers!
thanks, i committed your patch to cvs.
i changed the bit-and value to ~0x8000, since the alsa driver uses
outl() for accessing while oss uses outw().
to be sure, please check whether the latest driver works for you.
ciao,
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
next prev parent reply other threads:[~2003-04-07 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 16:25 Patch for ali5451 (ATI IGP chipset) "ali_codec_ready: codec is not ready" ANDREI LAHUN
2003-04-07 15:30 ` Takashi Iwai [this message]
2003-04-07 22:28 ` ANDREI LAHUN
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=s5hwui6qq9g.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=zhirnyi@yahoo.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.