d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added a note about OPTi 82C929 based cards.

Browse Source 
Clarified GUS DMA Settings.
Other misc. changes.

This should hold us over until I can finish cleaning up TASD, and finish
reintegrating all of the FreeBSD changes to the sound driver.  At that time
this document will be removed, and it's information moved to the handbook.
This commit is contained in:
Sujal Patel 1996-04-11 15:34:22 +00:00
parent cf09a2067c
commit e04401bad1
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=15198
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
sys/i386/isa/sound/sound.doc
View File

@ -1,4 +1,4 @@
$Id: sound.doc,v 1.4 1995/09/01 19:09:10 jkh Exp $
$Id: sound.doc,v 1.5 1996/04/11 06:23:18 scrappy Exp $
Instructions on using audio on a FreeBSD 2.1 (or 2.0-current) system.
See also /sys/i386/conf/LINT.
@ -26,6 +26,8 @@ sound card you have:
#device sbmidi0 at isa? port 0x300
# Gravis UltraSound - for GUS, GUS16, GUSMAX
# For cards that use 2 DMA Channels:
# drq = Write DMA Channel, flags = Read DMA Channel
#device gus0 at isa? port 0x220 irq 11 drq 1 flags 0x3 vector gusintr
# Gravis UltraSound 16 bit option - for GUS16 - requires gus0
@ -72,6 +74,7 @@ Other Options:
#options OPTI_MAD16_PORT
Adds support for the OPTI MAD16 Chip. (Part of the MSS driver)
If your soundcard has a chip labeled "OPTi 82C929" then try this.
#options __SGNXPRO__
Adds support for the SG NX Pro mixer. (Part of the SB driver)
@ -100,16 +103,18 @@ accordingly.
Also: You can configure more then one card on a single DMA using
ALLOW_CONFLICT_DMA. This is useful for boards with more then one type of
emulation.
the conflicts keyword in your configuration file. This is useful for boards
with more then one type of emulation.
Probing problems: Since the SB16 uses the same IRQ and addresses for
the different drivers, some of the snd dirvers will not be probed because
the different drivers, some of the snd drivers will not be probed because
the kernel thinks there is a conflict. This can be worked-around by
setting the ALLOW_CONFLICT_IOADDR or ALLOW_CONFLICT_IRQ options.
using the "conflicts" keyword on the sb16's device line.
For further information, contact multimedia@freebsd.org
- Jordan Hubbard (jkh@freefall.cdrom.com)
- Steven Wallace (swallace@freefall.cdrom.com)
- Sujal Patel (smpatel@wam.umd.edu)