From owner-freebsd-multimedia  Sun Aug 10 12:44:44 1997
Return-Path: <owner-freebsd-multimedia>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id MAA09755
          for multimedia-outgoing; Sun, 10 Aug 1997 12:44:44 -0700 (PDT)
Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA09742
          for <multimedia@freebsd.org>; Sun, 10 Aug 1997 12:44:38 -0700 (PDT)
Received: from ct.picker.com by whqvax.picker.com with SMTP;
          Sun, 10 Aug 1997 15:43:52 -0400 (EDT)
Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1)
	id AA11662; Sun, 10 Aug 97 15:43:50 EDT
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id PAA29164; Sun, 10 Aug 1997 15:41:13 -0400
Message-Id: <19970810154112.04412@ct.picker.com>
Date: Sun, 10 Aug 1997 15:41:12 -0400
From: Randall Hopper <rhh@ct.picker.com>
To: Alex <garbanzo@hooked.net>
Cc: multimedia@freebsd.org
Subject: Re: AWE32/64 support?
References: <19970810113200.09723@ct.picker.com> <Pine.BSF.3.96.970810120054.253B-100000@zippy.dyn.ml.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81
In-Reply-To: <Pine.BSF.3.96.970810120054.253B-100000@zippy.dyn.ml.org>; from Alex on Sun, Aug 10, 1997 at 12:21:03PM -0700
Sender: owner-freebsd-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Alex:
 |On Sun, 10 Aug 1997, Randall Hopper wrote:
 | 
 |>      The AWE driver provides wavetable support for the the SB cards that
 |> have the EMU-8000 synth chip (SB32s, AWE32s, and AWE64s), giving you synth
 |> music in Doom, great-sounding MIDIs, MODs, 669s, S3Ms, GUS sequencer
 |> compatibility, etc.  As Doug mentioned, the SB16 drivers are used for DSP
 |> support since effectively that's what's on these cards (SB16 or the
 |> compatible Vibra16 chipset).
 |
 |So this doesn't _just_ support the AWE32s and AWE64s? I have a 32PnP and
 |for kicks added the awe device line, and it _seems_ to find it at port 620
 |but then later says "AWE Not Found" "AWE: Not Detected". *shrug*  Also,
 |does the awe driver need the sb driver to work? or will they work
 |independant of each other?

     To the last question, I think the #ifdefs in the sounddriver nested so
that you probably have to define at least some of the SB DSP devices to get
a kernel to link with AWE support.  Probably just want to include them all:

     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

     To the first question, the driver itself doesn't have PnP detection
and initialization, but you can still use your card with it.  You need to
grab Sujal Patel's ISA PnP Tools and link those into your kernel.  Once
they init the card, the driver will detect and use it.

Here's one URL to Sujal's package:

     ftp://rah.star-gate.com/pub/FreeBSD-ISA_PnP_June8.tar.gz

I've gotten e-mail and seen list posts from several folks that have gotten
their PnP SoundBlaster cards (e.g. AWE32 PnP, AWE64 PnP, and SB16 PnP)
working using Sujal's kit.

     Note that once the experimental sound drivers Amancio and Luigi are
heading-up the rework for stabilize and are checked in, PnP init for
soundcards in general will probably be handled in the sound drivers
themselves.  For now though it's handled external to the sound drivers with
the ISA PnP tools.

Randall