Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sb(4) [netbsd man page]

SB(4)							   BSD Kernel Interfaces Manual 						     SB(4)

NAME
sb -- SoundBlaster family (and compatible) audio device driver SYNOPSIS
sb0 at isa? port 0x220 irq 5 drq 1 drq2 5 sb1 at isa? port 0x240 irq 7 drq 1 flags 1 sb* at isapnp? sb* at pnpbios? index ? audio* at audiobus? midi* at sb? mpu* at sb? opl* at sb? DESCRIPTION
The sb driver provides support for the SoundBlaster, SoundBlaster Pro, SoundBlaster 16, Jazz 16, SoundBlaster AWE 32, SoundBlaster AWE 64, and hardware register-level compatible audio cards. The SoundBlaster series are half-duplex cards, capable of 8- and 16-bit audio sample recording and playback at rates up to 44.1kHz (depending on the particular model). The base I/O port address is usually jumper-selected to either 0x220 or 0x240 (newer cards may provide software configuration, but this driver does not directly support them--you must configure the card for its I/O addresses with other software). The SoundBlaster takes 16 I/O ports. For the SoundBlaster and SoundBlaster Pro, the IRQ and DRQ channels are jumper-selected. For the SoundBlaster 16, the IRQ and DRQ channels are set by this driver to the values specified in the config file. The IRQ must be selected from the set {5,7,9,10}. The configuration file must use 1 flags specification to enable the Jazz16 support. This is to avoid potential conflicts with other devices when probing the Jazz 16 because it requires use of extra I/O ports not in the base port range. With a SoundBlaster 16 card the device is full duplex, but it can only sensibly handle a precision of 8 bits. It does so by extending the output 8 bit samples to 16 bits and using the 8 bit DMA channel for input and the 16 bit channel for output. The joystick interface (if enabled by a jumper) is handled by the joy(4) driver, and the optional SCSI CD-ROM interface is handled by the aic(4) driver. SoundBlaster 16 cards have MPU401 emulation and can use the mpu attachment, older cards have a different way to generate MIDI and has a midi device attached directly to the sb. SEE ALSO
aic(4), audio(4), isa(4), isapnp(4), joy(4), midi(4), mpu(4), opl(4), pnpbios(4) HISTORY
The sb device driver appeared in NetBSD 1.0. BUGS
Non-SCSI CD-ROM interfaces are not supported. The MIDI interface on the SB hardware is braindead, and the driver needs to busy wait while writing MIDI data. This will consume a lot of system time. BSD
June 22, 2005 BSD

Check Out this Related 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
Man Page