From owner-freebsd-multimedia Tue Apr 4 12:48:15 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id 07FC237B8D6 for ; Tue, 4 Apr 2000 12:47:52 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 12cZIT-0009Q9-0U; Tue, 4 Apr 2000 20:47:33 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA68710; Tue, 4 Apr 2000 20:52:31 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 4 Apr 2000 20:53:56 +0100 (BST) From: Doug Rabson To: Martin Cracauer Cc: Conrad Sabatier , Travis Mikalson , multimedia@freebsd.org Subject: Re: newpcm glitches with AWE64 In-Reply-To: <20000404194438.A44076@cons.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 4 Apr 2000, Martin Cracauer wrote: > In , Conrad Sabatier wrote: > > > > On 03-Apr-00 Travis Mikalson wrote: > > > I have an SB AWE64 ISA PnP that I'm having some problems with since I > > > upgraded to 4.0. > > > > > > Basically the sound is interrupting (very short, about 200ms) once or > > > twice a minute whether I use mpg123, xmms, realplayer, etc. > > > > > > I was using voxware in 3.x-STABLE and not having any problems, even > > > under heavy load. > > > > > > Unfortunately that's all I know. No weird messages from anything, > > > everything seems happy enough. > > > > > > It's an SMP system, dual PPro 200 on a Tyan Titan Pro ATX. > > > > > > /dev/sndstat: > > > FreeBSD Audio Driver (newpcm) Apr 1 2000 08:39:50 > > > Installed devices: > > > pcm0: at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex) > > > > > > Anybody else having any similar problems? Any suggestions? > > > > I experienced the same sort of behavior when I upgraded to 4.0 a few weeks > > ago. I've since reverted to 3.4-STABLE, and everything's working fine > > again. > > > > The new pcm driver is really "Not Ready For Prime Time" just yet. Why > > it's being forced on people (i.e., if you want to use 4.0) at this point is > > beyond me. > > newbus > > Every driver had to be updated and that the only update that was > contributed at the time was Cameron's newpcm. Not quite. Newbus provided (and still provides) a compatibility layer which allows most driver written to the old apis to work unchanged. > For the same reason you > can't get the commercial OSS thing for FreeBSD-4.x/5.x. The reason that OSS does not work in 4.x is that OSS uses an interrupt registration interface which has been deprecated since approximately FreeBSD 2.2. There are suitable replacement interfaces which integrate properly with the resource management systems of the kernel but the OSS engineers chose not to change their driver to with with the new system. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message