Lines Matching full:legacy
9 more fine controls over the legacy MIDI 1.0. The fundamental changes
14 - Transparent conversions between UMP and legacy MIDI 1.0 byte stream
59 support for the legacy raw MIDI device for UMP Endpoints.
84 legacy applications accessing mistakenly to UMP devices.
106 (0-based) UMP Group. Legacy applications can access to the specified
175 either the legacy, UMP MIDI 1.0 or UMP MIDI 2.0 device, respectively.
176 The first, legacy client is the one that sends/receives the old
185 is treated as a legacy event as it was (with max 12 byte data
198 Client 14 : "Midi Through" [Kernel Legacy]
213 Here you can find two types of kernel clients, "Legacy" for client 14,
238 only between the legacy and the UMP MIDI 1.0/2.0 types, but also
240 `aseqdump` program on the ProtoZOA Main port in the legacy mode will
296 * The legacy rawmidi device number is found in the new `tied_device`
299 `tied_device` field of the legacy rawmidi info, too.
301 * Each substream of the legacy rawmidi may be enabled / disabled
305 the legacy rawmidi info.
313 `SNDRV_CTL_IOCTL_RAWMIDI_NEXT_DEVICE` queries only the legacy
341 to have a larger payload of 16 bytes instead of the legacy 12
570 legacy MIDI 1.0 rawmidi devices corresponding to both EP 0 and EP 1.