cms(4) [netbsd man page]

CMS(4)							   BSD Kernel Interfaces Manual 						    CMS(4)

NAME

     cms -- Creative Music System device driver

SYNOPSIS

     cms0  at isa? port 0x220
     midi* at cms?

DESCRIPTION

     The cms driver provides support for the Creative Music System (C/MS).  These cards were developed by Creative Labs, the same people who
     designed the SoundBlaster cards.  Chips were available for the SoundBlaster to make them compatible with CMS.

     The CMS cards are only capable of playing basic notes and noises, making them suitable for playing midi, but not much else.  The output is
     stereo, but the cms driver doesn't support stereo control.  The cards have external volume control, line-output and speaker.

     The base I/O port address is usually jumper-selected to 0x220.  Valid jumper settings are for 0x210, 0x220, 0x230, 0x240, 0x250 and 0x260.
     There are no interrupt settings.

SEE ALSO

     isa(4), midi(4)

HISTORY

     The cms device driver appeared in NetBSD 1.5.

BSD
								  April 28, 2000							       BSD

EAP(4)							   BSD Kernel Interfaces Manual 						    EAP(4)

NAME

     eap -- AudioPCI audio device driver

SYNOPSIS

     eap*   at pci? dev ? function ?
     audio* at audiobus?
     joy*   at eap?
     midi*  at eap?
     options EAP_USE_BOTH_DACS

DESCRIPTION

     The eap driver provides support for the Ensoniq AudioPCI and Creative Labs SoundBlaster PCI series of audio cards.  All models based on the
     ES1370, ES1371, and ES1373 chips are supported.

     By specifying:

	   options EAP_USE_BOTH_DACS

     a second audio device is attached.  You can use it simply by directing audio output to it.  This way it is possible for two different pro-
     grams to use the "same" audio device simultaneously.

SEE ALSO

     ac97(4), audio(4), joy(4), midi(4), pci(4)

HISTORY

     The eap device driver appeared in NetBSD 1.4.

CAVEATS

     The joystick port hardware works by emulating a legacy isa(4) joystick port, bypassing the pci(4) bus method for address allocation.  This is
     unlikely to work on PCI busses other than the primary one.  There is also a possibility for conflicts with real ISA devices because the PCI
     bus is probed before ISA.	Use with caution.

BSD
								   July 22, 2006							       BSD