From owner-freebsd-current Tue Feb 22 14:33:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id AC36737B796 for ; Tue, 22 Feb 2000 14:33:48 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id XAA14110; Tue, 22 Feb 2000 23:33:26 +0100 (CET) (envelope-from asmodai) Date: Tue, 22 Feb 2000 23:33:26 +0100 From: Jeroen Ruigrok van der Werven To: "Daniel O'Connor" Cc: current@FreeBSD.ORG, Lyndon Nerenberg Subject: Re: status of 'device awe' ? Message-ID: <20000222233325.A14094@lucifer.bart.nl> References: <20000222132327.O5555@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from doconnor@gsoft.com.au on Wed, Feb 23, 2000 at 08:49:42AM +1030 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000222 23:25], Daniel O'Connor (doconnor@gsoft.com.au) wrote: > >On 22-Feb-00 Jeroen Ruigrok van der Werven wrote: >> Should be used instead. >> I am so in favor of just declaring voxware dead... But the armchair >> generals wouldn't like that. > >The awe device controls the AWE's wavetable.. newpcm doesn't talk to this >(yet - no idea if there are any plans) newmidi is underway... That's why I wanted to kill voxware in 4.0, would allow pcm to be used from default... Now we're stuck to the voxware crap for another release cycle until 5.0 hits the public. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message