From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Stephen Hassard <steve@hassard.net>, alsa-devel@lists.sourceforge.net
Subject: Re: M-Audio Sonica support
Date: Mon, 02 Sep 2002 19:27:53 +0200 [thread overview]
Message-ID: <s5hadn0e1ye.wl@alsa2.suse.de> (raw)
In-Reply-To: <3D739EBE.91D0D608@ladisch.de>
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
next prev parent reply other threads:[~2002-09-02 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 14:33 M-Audio Sonica support Stephen Hassard
2002-09-02 10:37 ` Takashi Iwai
[not found] ` <000601c25299$6e8ec740$0500a8c0@shwxp>
2002-09-02 16:03 ` Takashi Iwai
2002-09-02 17:24 ` Clemens Ladisch
2002-09-02 17:27 ` Takashi Iwai [this message]
2002-09-02 19:35 ` Stephen Hassard
2002-09-03 8:22 ` Clemens Ladisch
2002-09-04 8:11 ` Clemens Ladisch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hadn0e1ye.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=steve@hassard.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.