From owner-freebsd-current Sun Sep 26 14:30:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id 38F3114C25 for ; Sun, 26 Sep 1999 14:30:40 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA14132; Sun, 26 Sep 1999 14:23:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909262123.OAA14132@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dmaddox@conterra.com Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Loss of Functionality with newpnp In-reply-to: Your message of "Sun, 26 Sep 1999 16:05:19 EDT." <19990926160519.A350@dmaddox.conterra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Sep 1999 14:23:18 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Sep 26, 1999 at 12:29:46PM -0700, Mike Smith wrote: > > > > > > But we do have a working driver for the AWE64. Or rather, it worked fine > > > before the new PnP code was comitted, now it doesn't. It seems to me that > > > this indicates a deficiency in the new PnP code. Isn't that correct? > > > > No. > > > > I have already explained to you that the AWE64 driver that you were > > using (one actually of _three_ that we have) only worked with PnP cards > > as an accidental side-effect of the old PnP code. Now that the PnP > > code has been fixed, the brokenness of the old driver is exposed. > > Can you give me a few hints on what would be necessary to get the old > driver to work with the new PnP? As has already been explained to you (you _do_ read these messages in their entirety, right?), the old driver has been obsoleted. You need to take the functionality that you want from the old driver and implement it in the newpcm code. > It's amazing that one of the most popular sound cards of all time, one > that works fine on practically every OS from DOS3.3 to Linux and BeOS, > is of no concern to FBSD developers :-/ Since the AWE64 is already reported to work just fine with the current generation sound code, this sounds just a little hysterical to me. You seem to have a slightly more specialised requirement that's not yet being catered to that does require some more attention. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message