WSS(4) BSD Kernel Interfaces Manual WSS(4)NAME
wss -- Windows Sound System hardware audio driver
SYNOPSIS
wss0 at isa? port 0x530 irq 10 drq 0 drq2 1
wss0 at isa? port 0x530 irq 10 drq 0 flags 1
wss* at acpi?
wss* at isapnp?
wss* at pnpbios? index ?
audio* at audiobus?
opl* at wss?
DESCRIPTION
The wss driver supports Microsoft's Windows Sound System, the MAD16 chip based hardware, and their clones.
The base I/O port is set by a jumper on the board; valid choices are 0x530, 0x604, 0xE80, or 0xF40. Both IRQ and DMA channels are software
programmable. The IRQ may be set to 7, 9, 10, or 11, and the DMA channel may be set to 0, 1, or 3.
The device flags must have bit 0 (value 1) set to enable the MAD16 support. This is to avoid potential conflicts with other devices when
probing the MAD16 because it requires use of extra I/O ports not in the base port range. Chips needing this flag include the OPTi 82C928,
82C929, 82C831, and the OAK OTI-601D. Setting bit 1 (value 2) in flags disables the joystick port on MAD16 hardware.
SEE ALSO acpi(4), audio(4), isa(4), isapnp(4), joy(4), opl(4), pnpbios(4)BSD June 22, 2005 BSD
Check Out this Related 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
Hi,
I am running a command this way
grep -l ` cat get_list_data.lst | awk '{ print $2 }' ` /wss/test/trans/*CASE*
What I am trying to do is, get the second field from the file get_list_data.lst and then grep it in the path /wss/test/trans/
But it says
grep: can't open... (3 Replies)
Hello,
I have develop a driver for my hardware and now, I need to handle a IRQ but I does not work.
As I can understand, to handle a irq, it is necessary to make a request_irq(). If the return value is zero, ok, no problem to handle irq.
Here is a easy example of my driver:
#include... (8 Replies)