--- DJ Sisolak <dsisolak@xxxxxxxxxxxxxxxxxxxxxx> schrieb: > Hello Jerry, > > Responses to: > > 1) Not sure what you are after. Being that the > driver is KS based, it is > impossible to get away from the KS style when > addressing the driver > directly. There is the mixer API to address any > audio device, though I > can see where that might fall short for addressing > all possible > properties. This is perfectly okay, even if the whole interface is hell of bureaucratic stuff. > > 2) I will make measurements on the driver and stack > once the new driver > is complete. his would be nice, but since for example the USBMIDI standard does not support timestamping there is still a need for a "own" protocol. also I may want to trigger other things (okay, these things could be handled as HID devices). > > 3) The USB Audio specification allows for a > "SET_MEM" and "GET_MEM" > request to the device. Would this suffice if the > driver would pass this > type of request through? In this case I think it's easier to give the device a different device id that just starts a "loader driver" and afterwards the device resets (as it is in the cypress parts). Cypress has also a demo of this in its sdk.. thanks for listening doc schnipp __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.de/