From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: M-Audio Sonica support Date: Mon, 02 Sep 2002 19:27:53 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <000601c25299$6e8ec740$0500a8c0@shwxp> <3D739EBE.91D0D608@ladisch.de> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <3D739EBE.91D0D608@ladisch.de> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Clemens Ladisch Cc: Stephen Hassard , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Mon, 02 Sep 2002 19:24:14 +0200, Clemens Ladisch wrote: > > Takashi Iwai wrote: > > Stephen Hassard wrote: > > > Interface Descriptor: > > > bLength 9 > > > bDescriptorType 4 > > > bInterfaceNumber 0 > > > bAlternateSetting 0 > > > bNumEndpoints 0 > > > bInterfaceClass 254 > > > bInterfaceSubClass 1 > > > bInterfaceProtocol 0 > > > iInterface 3 RAM > > > unknown descriptor type: 07 21 05 00 01 40 00 > > > > hmm, the descriptor is apprently broken. > > usually you'll see the list of interfaces, terminals, formats, > > etc. there. > > the device might be non-standard one. if so, the current driver > > doesn't support it, unfortuantely. > > bInterfaceClass 254 = "Application-Specific" > bInterfaceSubClass 1 = "Device Firmware Update" > > And they bothered to give the interface a name ("RAM"). :-) yep :) > If it were a broken descriptor, it would be easy to make the correct > information available with a quirk. In this case, however, we need the > firmware and a loader. > > The download protocol is described in the "USB Device Firmware > Upgrade Specification". A loader might already exist, or is (relatively) > easy to write. > > For the firmware, we could _try_ to ask Midiman. this is not bad idea - midiman / m-audio has been enough friendly to us, so far... > But I think a USB snoop log from the Windows driver would have a higher > probability of success. or, a higher rate of success :) > (Unfortunately, the bmAttributes field in the > DFU functional descriptor indicates that the device is only capable > of downloading, not uploading.) > If we have luck, the firmware is stored in a DFU file (not necessarily > with that name). Stephen, could you check whether any possible file eixsts on windows? ciao, Takashi ------------------------------------------------------- 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