From owner-freebsd-hardware Sat Aug 2 20:56:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA02614 for hardware-outgoing; Sat, 2 Aug 1997 20:56:24 -0700 (PDT) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA02605 for ; Sat, 2 Aug 1997 20:56:21 -0700 (PDT) Received: from [207.3.81.149] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id ja242043 for ; Sat, 2 Aug 1997 22:56:15 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 02 Aug 1997 22:54:35 -0000 (GMT) From: Chris Dillon To: Conrad Sabatier Subject: Re: AWE32 Cc: hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 02-Aug-97 Conrad Sabatier wrote: > >On 02-Aug-97 Randall Hopper wrote: >> >>Build a new kernel with: >> >> controller snd0 >> device pas0 at isa? port 0x388 irq 10 drq 3 vector pasintr >> device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr >> device sbxvi0 at isa? drq 5 >> device sbmidi0 at isa? port 0x330 >> device opl0 at isa? port 0x388 >> device awe0 at isa? port 0x620 > >Just wondering, why use the pas device for a Soundblaster? And won't it >conflict with the opl device? I was wondering the same thing. :) >Also, any chance of ever getting the awe device to recognize and work >with >an AWE 64? Seems to only be compatible with the AWE 32. > >Conrad, who admittedly hasn't fiddled with this stuff much lately :-) The AWE64 is nothing but an AWE32 with a slight change in how RAM is upgraded and some nifty new connectors on the Gold edition. Programming interface is exactly the same, AFAIK. --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet (http://www.freebsd.org)