From: Stuart Young <sgy@amc.com.au>
To: linux-kernel@vger.kernel.org
Cc: "Michael F. Robbins" <compumike@compumike.com>,
Robert Love <rml@tech9.net>,
Tachino Nobuhiro <tachino@open.nm.fujitsu.co.jp>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: SiS/Trident 4DWave sound driver oops
Date: Fri, 26 Oct 2001 13:24:48 +1000 [thread overview]
Message-ID: <5.1.0.14.0.20011026125325.024517e0@mail.amc.localnet> (raw)
In-Reply-To: <1004064125.19937.5.camel@phantasy>
In-Reply-To: <g087jff1.wl@nisaaru.dvs.cs.fujitsu.co.jp> <1004016263.1384.15.camel@tbird.robbins> <7ktjw58u.wl@nisaaru.dvs.cs.fujitsu.co.jp> <1004060759.11258.12.camel@phantasy> <6693w4ds.wl@nisaaru.dvs.cs.fujitsu.co.jp> <1004061741.11366.32.camel@phantasy> <g087jff1.wl@nisaaru.dvs.cs.fujitsu.co.jp>
At 10:42 PM 25/10/01 -0400, Robert Love wrote:
>On Thu, 2001-10-25 at 22:36, Tachino Nobuhiro wrote:
> > No. {0, } is the last elemnet of ac97_codec_ids[] and that index is
> > ARRAY_SIZE(ac97_code_ids) - 1. So this element which should be used as
> > a loop terminator is used as a valid entry in for loop incorrectly.
> >
> > Please read ac97_codec.c
>
>You are right; I apologize.
Implemented the patch suggested, and the module no longer oops's, and I get
codec id's listed as 0x0000:0x0000 (Unknown). I still get no sound like I
did with 2.4.7 (using mpg123 as a test, with a known working mp3 file), and
output to the device is blocked (nothing gets written).
How can I find out the ac97 codec ID for this chipset (if there is one) so
it can be added to the ac97_codec_ids array? From what I can tell, it's as
though the codec->codec_read(codec, AC97_VENDOR_ID#) isn't returning the
codec value for this system at all.
Any suggestions?
AMC Enterprises P/L - Stuart Young
First Floor - Network and Systems Admin
3 Chesterville Rd - sgy@amc.com.au
Cheltenham Vic 3192 - Ph: (03) 9584-2700
http://www.amc.com.au/ - Fax: (03) 9584-2755
next prev parent reply other threads:[~2001-10-26 3:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 13:24 SiS/Trident 4DWave sound driver oops Michael F. Robbins
2001-10-26 1:37 ` Tachino Nobuhiro
2001-10-26 1:56 ` Tachino Nobuhiro
2001-10-26 2:36 ` Tachino Nobuhiro
2001-10-26 1:45 ` Robert Love
2001-10-26 2:02 ` Robert Love
2001-10-26 2:42 ` Robert Love
2001-10-26 3:13 ` David Weinehall
2001-10-26 3:28 ` Robert Love
2001-10-26 3:24 ` Stuart Young [this message]
2001-10-26 14:36 ` Alan Cox
2001-10-26 14:47 ` Trever L. Adams
2001-10-28 23:06 ` SiS/Trident 4DWave sound driver Stuart Young
2001-10-29 1:19 ` SiS/Trident 4DWave sound driver (Update) Stuart Young
2001-10-29 4:04 ` SiS drivers (more) Stuart Young
2001-10-26 23:43 ` SiS/Trident 4DWave sound driver oops Michael F. Robbins
-- strict thread matches above, loose matches on Subject: below --
2001-10-25 1:07 Michael F. Robbins
2001-10-25 5:55 ` Stuart Young
2001-10-25 7:02 ` Stuart Young
2001-10-23 6:15 Stuart Young
2001-10-23 16:19 ` Alan Cox
2001-10-24 23:55 ` Stuart Young
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=5.1.0.14.0.20011026125325.024517e0@mail.amc.localnet \
--to=sgy@amc.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=compumike@compumike.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=tachino@open.nm.fujitsu.co.jp \
/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).