>There are 3 standard PCM ioctls, and a driver could potentially support others >via its own ioctl function registered in the snd_pcm_ops_t structure. Could >anyone give me a hint regarding how an application could then call such >standard and other ioctls?
i'm not going to do that, but i will point you at the "hwdep" API, which exists specifically to provide a way to make hw-dependent operations available that don't map into the existing ALSA API. you create a hwdep device within the driver; apps can open it, and call whatever ioctl's you provide. its a bad idea for general purpose software, of course, since such s/w can't know about your specific ioctls, but it works well for writing h/w specific control apps. i have an app for the wavefront synth, for example, which has a whole bunch of operations that don't fit into any of the existing PCM, MIDI or Sequencer APIs. these are implemented via the hwdep API, such as it is. --p ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
