From: Benson Chow <blc@q.dyndns.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ac97, alc101+kt8235 sound
Date: Tue, 15 Apr 2003 11:09:11 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0304151057090.31225-100000@q.dyndns.org> (raw)
In-Reply-To: <1050406611.27745.34.camel@dhcp22.swansea.linux.org.uk>
Cool, my ecs p4vxasd2+ (p4x333/kt8235/alc101) works with onboard sound
now.
What's the normal flow to get this added into ac97_codecs.c?
+ {0x414C4730, "ALC101", &null_ops},
Adding this line into the table in ac97_codecs.c (with a few missing
#defines fixed... then I noticed they're already in -ac1 :) in
2.4.21-pre7 made sound work fine.
Now hopefully those of us who bought those Fry's "free" p4vxasd2+ 5.0's
can have sound. I just mplayer'ed an avi with the new table entry and it
appears to work fine. Volume controls look functional. Will do some more
testing (record, etc.) tonight.
Thanks,
-bc
On 15 Apr 2003, Alan Cox wrote:
> Date: 15 Apr 2003 12:36:51 +0100
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> To: Benson Chow <blc+lkml@q.dyndns.org>
> Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> Subject: Re: ac97, alc101+kt8235 sound
>
> On Maw, 2003-04-15 at 12:49, Benson Chow wrote:
> > hoping that these via chips were pretty close. Unfortunately no, it
> > still doesn't work. It did, however, find the AC97 codec fine (I added
> > some printk's), but no sound is produced. Any ideas on how to get this
> > vt8235-based motherboard sound working? (and ALSA-0.9.2 seems to do
> > nothing but segfault it seems.)
>
> See 2.4.21pre - that has the driver for VIA8233/5
>
WARNING: All HTML emails get deleted. DO NOT SEND HTML MAIL.
next prev parent reply other threads:[~2003-04-15 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 11:49 ac97, alc101+kt8235 sound Benson Chow
2003-04-15 11:36 ` Alan Cox
2003-04-15 17:09 ` Benson Chow [this message]
2003-04-15 16:28 ` Alan Cox
2003-04-17 5:01 ` Benson Chow
2003-04-17 1:08 ` Mark Rutherford
2003-04-17 13:14 ` Alan Cox
2003-04-18 3:37 ` ac97, alc101+kt8235 sound (2.4.21-pre7-ac1) Benson Chow
2003-04-18 11:36 ` Alan Cox
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=Pine.LNX.4.44.0304151057090.31225-100000@q.dyndns.org \
--to=blc@q.dyndns.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).