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
GUSPNP(4) BSD Kernel Interfaces Manual GUSPNP(4) NAME
guspnp -- Am78C201 audio device driver SYNOPSIS
guspnp* at isapnp? audio* at audiobus? There should be no limit caused by the driver on the number of drivers or cards active in the system. DESCRIPTION
The guspnp driver provides support for audio subsystems using the Interwave (Am78C20x) family of ICs, usually the Gravis Ultrasound Plug and Play. Unlike the gus driver guspnp driver does not require any local memory for the IC, but uses the codec for both playback and recording. The guspnp driver can simultaneously playback and record 8- and 16-bit samples at frequencies from 5.51kHz to 48kHz. The guspnp driver relies on isapnp to allocate suitable resources for it. This version of the driver only uses the first logical device of the five the Interwave IC has. The four unused logical devices are the ATAPI CD-ROM device, PnP Joystick device, legacy soundcard emulation device (SoundBlaster) and MIDI serial device. Support for at least ATAPI CD-ROM and Joystick is being worked on. This version of the driver will use 1 IRQ and 2 DRQs. HARDWARE
Cards supported by the guspnp driver include: Gravis Ultrasound PNP, and compatibles SEE ALSO
audio(4), gus(4), isapnp(4) REFERENCES
Interwave(tm) IC Am78C201/202 Programmer's Guide Rev. 2. 1996. Advanced Micro Devices. HISTORY
The guspnp driver appeared in NetBSD 1.3. AUTHORS
Kari Mettinen <Kari.Mettinen@helsinki.fi>, University of Helsinki. BUGS
Sometimes you can cause a hiss on either left or right channel, or both. You can usually make it disappear by playing random data, however this might not be a very nice thing to your audio equipment, but it is the only way I have found out to be effective. Only the Codec is used in this version of the driver, therefore only 2 channels are supported (left and right). Also sound quality is proba- bly worse at lower kHz compared to playing through the synthesizer which does interpolation. If the implementation has a 'bad' oscillator, using frequencies 44.8kHz and 38.4kHz will result in incorrect playback frequency. The author has a GUS PnP Pro which displays this behavior. Other members of the Interwave family have not been tested and don't have the glue needed to make them work. Should someone need to implement it, not many changes in the existing code are needed. Output voltage control in register CFIG2 [7] should be set differently for some other members of the family. Other architectures than i386 haven't been tested. The bus_space abstraction has been used from the beginning, so it should work. BSD
June 22, 2005 BSD