EMUXKI(4) BSD Kernel Interfaces Manual EMUXKI(4)NAME
emuxki -- Creative Labs SBLive! and PCI 512 audio device driver
SYNOPSIS
emuxki* at pci? dev ? function ?
audio* at audiobus?
DESCRIPTION
The emuxki device driver supports Creative Sound Blaster Live! cards as well as the Sound Blaster PCI 512.
These Environmental Audio cards are based upon the programmable EMU10K1 digital-processing chip.
Hardware features:
o E-mu Systems, Inc. EMU10K1 music synthesis engine
o 64-voice hardware polyphony with E-mu's patented 8-point interpolation technology
o Up to 1024-voice polyphony with multi-timbre capability
o Support for real-time digital effects like reverb, chorus, flanger, pitch shifter, or distortion across any audio source
o User-selectable settings are optimized for headphones, two or four speakers
o Creative Multi Speaker Surround (CMSS) technology places any mono or stereo source in a 360 degree audio space
o Processes sample rates from 5kHz to 48kHz
o Hardware full duplex support enables simultaneous record and playback at 8 standard sample rates
o Allows multiple audio sources playback on the same speaker system
SEE ALSO ac97(4), audio(4), joy(4), pci(4)HISTORY
The emuxki device driver appeared in NetBSD 1.5.3.
AUTHORS
The emuxki driver was written by Yannick Montulet <yannick.montulet@epitech.net>.
BUGS
Currently, this driver does not support multiple source recording, MIDI nor the multi-voice capability.
BSD June 22, 2005 BSD
Check Out this Related Man Page
ESO(4) BSD Kernel Interfaces Manual ESO(4)NAME
eso -- ESS Technology Solo-1 PCI AudioDrive audio device driver
SYNOPSIS
eso* at pci? dev ? function ?
audio* at audiobus?
joy* at eso?
mpu* at eso?
opl* at eso?
DESCRIPTION
The eso device driver supports sound cards based on ESS Technology Solo-1 PCI AudioDrive chips (ES1938 and ES1946), e.g. the TerraTec 128i
PCI card.
DIAGNOSTICS
eso0: can't map Audio 1 DMA into I/O space PCI autoconfiguration did not map the first audio channel DMA controller into I/O space at a
suitable address, and the driver was not able map it by itself. In that case only playback functionality will be available.
eso0: reset timeout The device failed to acknowledge being reset.
eso0: RDR timeout The driver timed out reading data from a controller register.
eso0: WDR timeout The driver timed out waiting to send a command or writing to a controller register.
SEE ALSO audio(4), joy(4), mpu(4), opl(4), pci(4)HISTORY
The eso device driver appeared in NetBSD 1.5. The on-board gameport was first supported in NetBSD 1.6.
BSD June 22, 2005 BSD
Hi all,
My thanks in advance for reading and any posts.
Just wondering if anyone knows of anywhere where I can get a driver from for a creative zen sleek photo for redhad Fedora? I ordered it stupidly without making sure that it would work on Fedora, seems that it only works on WinXP. ... (2 Replies)