public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <landley@trommello.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Cc: whampton@staffnet.com, cobra@linse.ufsc.br
Subject: Re: CS423x audio driver updates for testing
Date: Tue, 27 Nov 2001 13:34:53 -0500	[thread overview]
Message-ID: <01112713345300.01486@localhost.localdomain> (raw)
In-Reply-To: <E164Ja5-0007qT-00@the-village.bc.nu>
In-Reply-To: <E164Ja5-0007qT-00@the-village.bc.nu>

On Thursday 15 November 2001 05:17, Alan Cox wrote:
> This gets rid of the nasty clicks on the thinkpad. On the TP600 this leaves
> us with fully functional sound including save/restore (if your bios is
> not too ancient at least). The mixer changes are from Daniel Cobra, I added
> the ident changes and made the driver pick the right (I hope) feature sets
> for each board.
>
> Can folks with cs42xx series audio give it a test make sure it doesn't
> break anything
>
> Alan

Well, it didn't break anything, but it didn't fix my no-sound after suspend 
problem.

Without your patch, sound on my dell inspiron 3500 laptop works fine until 
the first APM suspend and resume cycle, after which noatun under KDE will 
block indefinitely trying to write sound and trying sound from the command 
line (no X/KDE running) can get a little sound out sometimes, but it loops 
endlessly with warnings printing to the console about an IRQ problem.  To get 
sound working again, I have to power the laptop off and back on.

I just applied the patch against 2.5.0 (with the 
don't-eat-your-filesystem-on-shutdown patch as well: hey, it's 2.5, it's 
supposed to do that, isn't it?) and it made no noticeable difference.

lspci produces the same output before and after APM suspend.  It's a strange 
chipset, but it's using the ad1848 sound driver:

lspci -s 01:00.1 -v -v

01:00.1 Multimedia audio controller: Neomagic Corporation [MagicMedia 256AV 
Audio] (rev 12)
        Subsystem: Dell Computer Corporation MagicMedia 256AV Audio Device on 
Colorado Inspiron
        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B+
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin B routed to IRQ 11
        Region 0: Memory at fe000000 (32-bit, prefetchable) [size=4M]
        Region 1: Memory at fe700000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-


Any clues?

Rob

  reply	other threads:[~2001-11-27 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15 10:17 CS423x audio driver updates for testing Alan Cox
2001-11-27 18:34 ` Rob Landley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-15 13:55 Thomas Hood
2001-11-15 17:28 ` Alan Cox
2001-11-15 18:45   ` J Sloan
2001-11-15 23:18     ` Zach Brown

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=01112713345300.01486@localhost.localdomain \
    --to=landley@trommello.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cobra@linse.ufsc.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=whampton@staffnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox