UMIDI(4) BSD Kernel Interfaces Manual UMIDI(4)NAME
umidi -- USB support for MIDI devices
SYNOPSIS
umidi* at uhub?
midi* at umidi?
DESCRIPTION
The umidi driver supports USB MIDI devices that conform to the Universal Serial Bus Device Class Definition for MIDI Devices. Vendor-spe-
cific support is also included for the following:
Midiman devices
MidiSport 2x4
Roland and Edirol devices
Fantom-X
PC300
PCR
SC8820
SC8850
SCD70
SD20
SD80
SD90
SK500
SonicCell
U8
UA25
UA100
UA101
UA10F
UA4FX
UA700
UA1000
UM1
UM2
UM3
UM4
UM550
UM880N
XV5050
Yamaha devices
UX256 (product-specific support)
Others Other Yamaha MIDI devices will be attached and are expected to work also.
Devices supported by the umidi driver will appear as midi(4) devices.
SEE ALSO midi(4), usb(4)HISTORY
The umidi driver appeared in NetBSD 1.6.
BSD October 14, 2007 BSD
Check Out this Related Man Page
SND_UAUDIO(4) BSD Kernel Interfaces Manual SND_UAUDIO(4)NAME
snd_uaudio -- USB audio and MIDI device driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device sound
device usb
device snd_uaudio
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
snd_uaudio_load="YES"
DESCRIPTION
The snd_uaudio driver provides support for USB audio class devices and USB MIDI class devices.
A USB audio device consists of a number of components: input terminals (e.g. USB digital input), output terminals (e.g. speakers), and a num-
ber of units in between (e.g. volume control).
Refer to the 'USB Audio Class Specification' for more information.
SEE ALSO sound(4), usb(4)
USB Audio Class Specifications, http://www.usb.org/developers/devclass_docs/.
HISTORY
The snd_uaudio driver first appeared in FreeBSD 4.7.
AUTHORS
This manual page was adopted from NetBSD 1.6 and modified for FreeBSD by Hiten Pandya <hmp@FreeBSD.org>.
BUGS
The PCM framework in FreeBSD, as of this writing, does not handle device un-registrations in a properly abstracted manner, i.e., a detach
request is refused by the PCM framework if the device is in use. It is necessary to allow the device un-registration to complete success-
fully, otherwise the PCM layer will panic.
BSD February 24, 2011 BSD