Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 5 Aug 2002 10:20:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 5 Aug 2002 10:20:32 -0400 Received: from mx7.sac.fedex.com ([199.81.194.38]:62224 "EHLO mx7.sac.fedex.com") by vger.kernel.org with ESMTP id ; Mon, 5 Aug 2002 10:20:31 -0400 Date: Mon, 5 Aug 2002 21:51:34 +0800 (SGT) From: Jeff Chua X-X-Sender: root@boston.corp.fedex.com To: Alan Cox cc: Thomas Munck Steenholdt , Linux Kernel Subject: Re: Sv: i810 sound broken... In-Reply-To: <1028555196.18130.36.camel@irongate.swansea.linux.org.uk> Message-ID: MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on ENTPM11/FEDEX(Release 5.0.8 |June 18, 2001) at 08/05/2002 09:53:02 PM, Serialize by Router on ENTPM11/FEDEX(Release 5.0.8 |June 18, 2001) at 08/05/2002 09:53:06 PM, Serialize complete at 08/05/2002 09:53:06 PM Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1039 Lines: 27 On 5 Aug 2002, Alan Cox wrote: > On Mon, 2002-08-05 at 12:45, Thomas Munck Steenholdt wrote: > > > The changes in the recent i810 audio are > > > - Being more pessimistic in our interpretation of codec power up > > > - Turning on EAPD in case the BIOS didn't do so at boot up > > > > > > Longer term full EAPD control as we do with the cs46xx is on my list, > > > paticularly as i8xx laptops are becoming common . (EAPD is the amplifier > > > power controller) > > > > That's strange - I get the same scratchy sounds on 2.4.19 as I did on 2.4.18 > > and a couple of the 2.4.19-pre's... Is there anything I should try, to > > make sure things are configged / built correctly..? > > What was the last tree that worked correctly on your box ? Works for me on all 2.4.19-prex and 2.4.19. Jeff. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/