From owner-freebsd-mobile Tue Apr 28 10:54:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17662 for freebsd-mobile-outgoing; Tue, 28 Apr 1998 10:54:44 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17657 for ; Tue, 28 Apr 1998 10:54:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA00551; Tue, 28 Apr 1998 09:50:14 -0700 (PDT) Message-Id: <199804281650.JAA00551@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: rob@remarque.org (Rob Robertson) cc: Nate Williams , freebsd-mobile@FreeBSD.ORG Subject: Re: weird sound problem with tp 560 In-reply-to: Your message of "Tue, 28 Apr 1998 10:48:14 PDT." <199804281748.KAA22993@remarque.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Apr 1998 09:50:13 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > is it a software or firmware/hardware problem? anyone know what's up > > > with that? > > > > Probably a software problem. I don't believe the sound code is APM > > aware, so it won't re-configure itself upon resume. > > That's correct. I've discussed this with our current lead sound > developer, but he's not laptop-enabled so things have been slow. > > my question then is: why does hibernate do the right thing, but > suspend doesn't? Hibernation doesn't lose the state of the DMA/sound hardware, it just pauses it. After a suspend/resume cycle, you have to reinitialise the hardware and restart the DMA, and our code doesn't do that. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message