guspnp(4) [netbsd 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

MCD(4)							   BSD Kernel Interfaces Manual 						    MCD(4)

NAME

     mcd -- Mitsumi CD-ROM driver

SYNOPSIS

     device mcd

     In /boot/device.hints:
     hint.mcd.0.at="isa"
     hint.mcd.0.port="0x300"
     hint.mcd.0.irq="10"

DESCRIPTION

     The mcd driver provides a data and audio interface to the Mitsumi-brand CD-ROM player.  The CD-ROM player must be interfaced to the ISA bus
     through one of the Mitsumi proprietary controller boards.	The controller boards supported are the LU002S, LU005S, the FX001 and the quite
     common FX001D.

     The mcd driver responds to disk-specific ioctl() commands, namely the DIOCGDINFO, DIOCGPART, DIOCWDINFO, and DIOCSDINFO, commands.  Other
     disk-specific ioctl() commands will return an error.

     The mcd driver also responds to special CD-ROM ioctl() commands.  These commands control the CD-ROM player's audio features.  The commands
     are:

	   CDIOCREADSUBCHANNEL	get sub-channel information on current status of disc playing
	   CDIOCREADTOCHEADER	get table of contents header
	   CDIOCREADTOCENTRYS	gets all of the table of contents
	   CDIOCPLAYTRACKS	begins audio playing at location specified
	   CDIOCPLAYBLOCKS	fails with error EINVAL
	   CDIOCPLAYMSF 	begins audio playing at location specified
	   CDIOCRESUME		resumes playing a previously paused disc
	   CDIOCPAUSE		pauses a playing disc
	   CDIOCSTART		begins playing a disc
	   CDIOCSTOP		stops a previously playing disc
	   CDIOCEJECT		opens the disc tray (there is no support for a corresponding un-eject command).
	   CDIOCRESET		stops any play and resets the Mitsumi controller board
	   CDIOCSETDEBUG	cause the kernel to print debug messages to the console about the mcd driver
	   CDIOCCLRDEBUG	cause the kernel to quit printing debug messages about the mcd driver

     The ioctl() commands defined above are the only ones that the mcd driver supports.  There are other CD-ROM related ioctl() commands (such as
     CDIOCSETVOL and CDIOCSETSTERIO) which are available and may be supported by future versions of the driver.

FILES

     /dev/(r)mcd0a  accesses BSD partition on the disc.  Normally, there is only one file system on a CD-ROM disc.
     /dev/(r)mcd0c  accesses raw device.

NOTES

     The character-mode devices for the mcd driver should only be used for accessing the audio features of the CD-ROM player as the performance on
     data is abysmal.

     The current version of the driver uses neither the DMA or IRQ features of the interface board, although it has an interrupt handler for any
     IRQ requests that are generated.  Until the DMA features are supported, the only interrupts that the board generates are those that are not
     supported by the driver anyway.

SEE ALSO

     <sys/cdio.h>

HISTORY

     An mcd driver appeared in FreeBSD 1.0.

AUTHORS

     The driver was written by Holger Veit (data part) and Brian Moore (audio part).  Changes were provided by Gary Clark II, Andrew A. Chernov,
     and Jordan K. Hubbard.

BSD
								 December 8, 1994							       BSD