The problem is that if I design a class-compliant driver, and two identical devices are attached, there is no way to distinguish between the two devices? At least that is what I heard from companies who started writing their own drivers after trying to design the device class-compliant. > -----Original Message----- > From: wdmaudiodev-bounce@xxxxxxxxxxxxx > [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of timr@xxxxxxxxx > Sent: maandag 22 november 2004 3:41 > To: wdmaudiodev@xxxxxxxxxxxxx > Cc: Tim Roberts > Subject: [wdmaudiodev] Re: USB midi driver? > > > On Sat, Nov 20, 2004 at 09:39:00AM +0100, Olivier Roblin wrote: > > > > You should export your device to the system, so that it can > recognize > > it > > as a MIDI device. You can only do that in kernel mode. You > should use a > > Port/Miniport filter architecture (IMiniportMidi) to define > the MIDI > > interface and send data received onto Usb... > > Doesn't USBAUDIO.SYS handle all of that automatically? The > whole point of designing a class-compliant device is that one > can skip the painful step of creating a driver. > -- > - Tim Roberts, timr@xxxxxxxxx > Providenza & Boeklheide, Inc. > ****************** > > 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/ > ****************** 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/
