Lars Doelle wrote:
> perhaps a GNU Vendor ID is due.
>
> The latest alsa usbmidi has added support for the proprietary Midisport
> protocol, which is (as any proprietary protocol) identified by the
> Vendor/Product ID. The devices downloads firmware over USB. This firmware
> then contains this particular ids. To make use of the protocol supported by
> the alsa driver, a proprietary binary firmware ripped-off or eaves-dropped
> from the windows driver is necessary.
Primarily, I wrote it for the USB Quattro which doesn't need (or even
support?) firmware downloading.
> Now i wrote a gpl'ed usb-midi complient firmware to do things the complient,
> freeware way, but used the same ids, hoping, the proprietary firmware would
> be contained in the windows world. But - now it happend.
>
> We finally have the case of a device which talks two different protocols,
> depending on the firmware loaded, and a driver which hooks in triggered by
> the v/p ids assuming proprietary protocol being talked.
No, the driver additionally checks for the interface class. With class
0xff ("vendor specific", Midiman's firmware), the proprietary protocol is
used. With class 1 (audio, your GPL firmware), the standard protocol is
used. I added the USB_DEVICE_VENDOR_SPEC macro specifically to avoid any
conflicts between the two firmware versions.
> Now i write to ask for your advice how to do things the right way. I fear that
> picking a GNU id would overdo and overcomplicate matters. I'm not even
> certain about the registration process or whether fee become due to usb.org.
<http://www.usb.org/developers/vendor.html>: $1500 for two years
> I'm also not clear how the vendor/product id has to be understood. Is it for
> the physical device (in which case it cannot be changed) or to the firmware?
It's for the firmware. There are different id's for Midisport devices with
and without firmware (have a look at the Windows driver .inf files).
HTH
Clemens
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
