From owner-cvs-all Sat Jun 10 7:16:47 2000 Delivered-To: cvs-all@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BC73137B81D; Sat, 10 Jun 2000 07:16:42 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id HAA66836; Sat, 10 Jun 2000 07:15:58 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Richard Seaman, Jr." Cc: Brian Somers , Maxim Sobolev , Kenneth Wayne Culver , Chris Piazza , Cameron Grant , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: cvs commit: src/sys/dev/sound/pcm channel.c In-reply-to: Your message of "Fri, 09 Jun 2000 14:45:58 CDT." <20000609144558.B566@tar.com> Date: Sat, 10 Jun 2000 07:15:58 -0700 Message-ID: <66833.960646558@localhost> From: "Jordan K. Hubbard" Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm also finding that applications like mpg123 don't play audio anymore whereas that very application does with a May 15th kernel, that being the most recent "old" kernel I have lying around on this laptop. If I play a WAV file with waveplay, it works fine. That does tend to suggest that the speed at which you can cram data down the audio subsystem's throat is a factor. - Jordan > On Fri, Jun 09, 2000 at 02:11:29PM -0500, Richard Seaman, Jr. wrote: > > > > If I just cat a .au file into /dev/audio, I get about 1/4 of a second > > > of plan and then silence, with & without the patch. > > > > Your symptoms are different then. Don't know if the cause is the > > same. > > Thinking about this some more, and as a followup to my last message, here's > what I'm guessing is happening to you. > > You fill the device buffers very rapidly. Since chn_wrintr is not getting > called as dma activity occurs, the only time the dma pointers can get updated > and therefore indicate that the buffers aren't full is when you write to > the buffers -- but you can't because they're already marked full. ie. > you're deadlocked. The sound you hear is the dma buffers emptying, but your > app never knows it happened because the buffers are still marked full. > > My case is the opposite side of the problem. My app doesn't always fill the > buffers fast enough, and the dma pointers get corruped. > > I'd guess that those that don't have problems either a) are getting > dma interrupts, or b) manage to fill the buffers at a rate that is > neither too fast nor too slow. > > -- > Richard Seaman, Jr. email: dick@tar.com > 5182 N. Maple Lane phone: 262-367-5450 > Nashotah WI 53058 fax: 262-367-5852 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message