mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stuart Young <sgy@amc.com.au>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	compumike@compumike.com (Michael F. Robbins),
	rml@tech9.net (Robert Love),
	tachino@open.nm.fujitsu.co.jp (Tachino Nobuhiro)
Subject: Re: SiS/Trident 4DWave sound driver
Date: Mon, 29 Oct 2001 10:06:40 +1100	[thread overview]
Message-ID: <5.1.0.14.0.20011029095844.01f60df0@mail.amc.localnet> (raw)
In-Reply-To: <E15x86H-0000GV-00@the-village.bc.nu>
In-Reply-To: <5.1.0.14.0.20011026125325.024517e0@mail.amc.localnet>

At 03:36 PM 26/10/01 +0100, Alan Cox wrote:
> > though the codec->codec_read(codec, AC97_VENDOR_ID#) isn't returning the
> > codec value for this system at all.
>
>Something is failing to bring up the AC97 codec bus and/or set it up
>properly. Can you find exactly which patch broke that for you (you'll
>possibly want to keep fixing the codec table as you test older ones)

Well the thing is this system has never had working sound. I've got 2 of 
these machines, both with the array fix, and neither get sound. I've tried 
2.4.7 (which didn't have the array fix), 2.4.9, 2.4.12, 2.4.13, and I'm 
about to try some earlier kernels, but since this chip is "notoriously new" 
I would not be suprised if it's not returning anything for what should be 
valid codec calls. Will take a peek and get back to you.

PS: This is one of these SiS630S all in one integrated things, and also one 
of the offenders in that SiS FrameBuffer stuff we've been discussing, so I 
wouldn't be suprised in anomalies at all.


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


  parent reply	other threads:[~2001-10-28 23:06 UTC|newest]

Thread overview: 16+ 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
2001-10-26 14:36       ` Alan Cox
2001-10-26 14:47         ` Trever L. Adams
2001-10-28 23:06       ` Stuart Young [this message]
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

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.20011029095844.01f60df0@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

all inboxes | Powered by JetHome®