gus(4) [netbsd man page]

GUS(4)							   BSD Kernel Interfaces Manual 						    GUS(4)

NAME

     gus -- Gravis UltraSound/UltraSound MAX audio device driver

SYNOPSIS

     gus0 at isa? port 0xPPP irq X drq Y drq2 Z
     audio* at audiobus?

DESCRIPTION

     The gus driver provides support for the Gravis UltraSound (GUS) and GUS MAX audio cards.  Both cards have on-board memory which is used for
     seamless playback of samples.  They can play back 8- or 16-bit samples at up to 44.1kHz.  They can record 8-bit samples at up to 44.1kHz.
     The UltraSound MAX is a full-duplex sound device, and if configured with two DRQ channels can be used for simultaneous playback and record-
     ing.  The I/O port base is jumper-selected, and may be chosen from 0x210-0x260 in steps of 0x10.  (The normal setting is 0x220.)  The GUS
     takes 16 ports at its base address and 8 ports at its base address + 0x100.

     The IRQ is software programmed, so you may select any IRQ from the set {3,5,7,9,11,12,15}.  The DRQ lines are software programmed, and may be
     chosen from {1,3,5,6,7}.  The drq2 field in the configuration file line specifies a second DRQ line for recording.  If there is no drq2 field
     in the config file, the playback channel will be used for recording DMA and only half-duplex mode will be available.

     The Gravis UltraSound MAX has an additional CODEC onboard which is addressed with four ports at an offset of 0x10C from the base ports
     (0x31C-0x36C).

SEE ALSO

     audio(4)

REFERENCES

     Gravis UltraSound Low-Level Toolkit, Revision 2.01, 20 May 1993, published by Advanced Gravis and Forte Technologies.

HISTORY

     The gus device driver appeared in NetBSD 1.1.

BUGS

     The full-duplex features of the GUS MAX have not been fully tested, and full-duplex on the original GUS may not be possible at all.

     Only two voices on the GF1 synthesizer chip are used by this driver (for left and right channels).

     Manipulating the mixer while audio samples are playing can lead to device driver confusion (and maybe even a system panic).

     Manipulating the mixer device seems to create pregnant system pauses, probably due to excessive interrupt masking.

     The joystick and MIDI port interfaces are not supported.

BSD
								   June 22, 2005							       BSD

Check Out this Related Man Page

SND_SBC(4)						   BSD Kernel Interfaces Manual 						SND_SBC(4)

NAME

     snd_sbc, snd_sb16, snd_sb8 -- Creative Sound Blaster ISA and compatible bridge device driver

SYNOPSIS

     To compile this driver into the kernel, place the following lines in your kernel configuration file:

	   device sound
	   device snd_sbc
	   device snd_sb16
	   device snd_sb8

     Alternatively, to load the driver as a module at boot time, place the following lines in loader.conf(5):

	   snd_sbc_load="YES"
	   snd_sb16_load="YES"
	   snd_sb8_load="YES"

     Non-PnP cards require the following lines in device.hints(5):

	   hint.sbc.0.at="isa"
	   hint.sbc.0.port="0x220"
	   hint.sbc.0.irq="5"
	   hint.sbc.0.drq="1"
	   hint.sbc.0.flags="0x15"

DESCRIPTION

     The snd_sbc bridge driver allows the generic audio driver sound(4) to attach to Creative Sound Blaster ISA (mostly SB16 or SB8, known as
     SoundBlaster Pro) compatible audio cards.

     The value of flags specifies the secondary DMA channel.  If the secondary DMA channel is C, set the flags to (C | 0x10).  For a sound card
     without the secondary DMA channel, the flags should be set to zero.

HARDWARE

     The snd_sbc driver supports the following sound cards:

     o	 Avance Asound 110
     o	 Avance Logic ALS100+
     o	 Avance Logic ALS120
     o	 Creative SB16
     o	 Creative SB32
     o	 Creative AWE64
     o	 Creative AWE64 Gold
     o	 Creative ViBRA16C
     o	 Creative ViBRA16X
     o	 ESS ES1681
     o	 ESS ES1688
     o	 ESS ES1868
     o	 ESS ES1869
     o	 ESS ES1878
     o	 ESS ES1879
     o	 ESS ES1888

DIAGNOSTICS

     sb_dspwr(XX) timed out.  A command to the DSP has timed out.  Check the I/O port configuration.

     bad irq XX (5/7/9/10 valid)  The IRQ given to the driver is not valid.

SEE ALSO

     sound(4)

HISTORY

     The snd_sbc device driver first appeared in FreeBSD 4.0.

AUTHORS

     Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp>

BSD
								 February 17, 2007							       BSD

Linux and UNIX Man Pages

gus(4) [netbsd man page]

Check Out this Related Man Page