From owner-freebsd-hardware Sat Aug 2 16:16:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20974 for hardware-outgoing; Sat, 2 Aug 1997 16:16:07 -0700 (PDT) Received: from as5200-port-254.no.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA20913 for ; Sat, 2 Aug 1997 16:15:54 -0700 (PDT) Received: (from conrads@localhost) by as5200-port-254.no.neosoft.com (8.8.6/8.8.6) id SAA05940 for hardware@FreeBSD.ORG; Sat, 2 Aug 1997 18:14:05 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19970802110825.42121@ct.picker.com> Date: Sat, 02 Aug 1997 18:14:04 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: hardware@FreeBSD.ORG Subject: Re: AWE32 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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? 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 :-) -- Conrad Sabatier http://www.neosoft.com/~conrads/