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>
Subject: Re: SiS/Trident 4DWave sound driver (Update)
Date: Mon, 29 Oct 2001 12:19:45 +1100	[thread overview]
Message-ID: <5.1.0.14.0.20011029112004.01d98df0@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)

Update: - 2.4.3 appears to have the same issue of no-find the codec.

2.2.19pre17 reports the wrong h/ware address for the sound device (the same 
one as the IDE bus - urghy!), so I can't even load the driver to test if 
it'll work (which I doubt).

Upon looking at the code between 2.4.0 and 2.4.13, in particular at 
trident_ac97_get() and trident_ac97_set() there is practically no 
difference between them, except for the addition of another option in the 
switch statement for another card. Almost all the additions and changes 
between versions have been specifically ALi or similar chipsets, and don't 
seem to affect the SiS stuff.

So where to now?

Thinking mebbe I should hook this machine up to the net outside the 
firewall, plug in the webcam and point it at it, give you an ssh account on 
it, and connect an oscilloscope to the audio and let you fiddle. Useful for 
the SiS FrameBuffer thing as well I'd guess. *grin*

Talk about remote debugging eh?


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-29  1:19 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       ` SiS/Trident 4DWave sound driver Stuart Young
2001-10-29  1:19       ` Stuart Young [this message]
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.20011029112004.01d98df0@mail.amc.localnet \
    --to=sgy@amc.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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

all inboxes | Powered by JetHome®