Re: Roland/Edirol M-16DX

From: Takashi Iwai <tiwai@suse.de>
To: "Lasse Kärkkäinen" <tronic+8nhy@trn.iki.fi>
Cc: alsa-devel@alsa-project.org
Subject: Re: Roland/Edirol M-16DX
Date: Wed, 27 May 2009 23:08:12 +0200	[thread overview]
Message-ID: <s5hr5ya1cg3.wl%tiwai@suse.de> (raw)
In-Reply-To: <4A1DA767.1030909@trn.iki.fi>

At Wed, 27 May 2009 23:49:43 +0300,
Lasse Kärkkäinen wrote:
> 
> This is still missing in 1.0.20.
> 
> >>>> This device doesn't seem to be supported yet. Does Roland make the
> >>>> specifications available, etc? The device is not compatible with USB
> >>>> Audio, but rather uses Vendor Specific Class.
> >>> It appears to have most of the audio class descriptors, so it should be
> >>> possible to tell the driver to just use it.
> >>>
> >>> Please try to add the following entry somewhere in sound/usb/usbquirks.h
> >>> and to recompile the driver:
> >>>
> >>>
> >>> {
> >>> 	/* Edirol M-16DX */
> >>> 	USB_DEVICE(0x0582, 0x00c4),
> >>> 	.driver_info = (unsigned long) & (const struct snd_usb_audio_quirk) {
> >>> 		.ifnum = QUIRK_ANY_INTERFACE,
> >>> 		.type = QUIRK_COMPOSITE,
> >>> 		.data = (const struct snd_usb_audio_quirk[]) {
> >>> 			{
> >>> 				.ifnum = 0,
> >>> 				.type = QUIRK_AUDIO_STANDARD_INTERFACE
> >>> 			},
> >>> 			{
> >>> 				.ifnum = 1,
> >>> 				.type = QUIRK_AUDIO_STANDARD_INTERFACE
> >>> 			},
> >>> 			{
> >>> 				.ifnum = 2,
> >>> 				.type = QUIRK_MIDI_FIXED_ENDPOINT,
> >>> 				.data = & (const struct snd_usb_midi_endpoint_info) {
> >>> 					.out_cables = 0x0001,
> >>> 					.in_cables  = 0x0001
> >>> 				}
> >>> 			},
> >>> 			{
> >>> 				.ifnum = -1
> >>> 			}
> >>> 		}
> >>> 	}
> >>> },
> >> Could you add this quirk to the alsa-driver distribution as well? I'm 
> >> getting tired of patching it myself for every new release :)
> > 
> > I didn't get any response about the patch, so I couldn't apply it...
> 
> Perhaps you missed the entire thread that was going on about this in 
> 2008? The one where I reported my results and other people also 
> participated in the analysis.

Wasn't it on alsa-devel ML?
I've never seen any reply / follow up on this on ML, at least.
(I checked my archive again, and couldn't found any.)

> > Seriously, without the response from testers, the development can
> > never go on.  It'd be helpful if you give back the result precisely
> > and soon at the next time...
> 
> Are you still expecting some feedback? You didn't suggest so in your 
> last message, so I didn't see the need to answer.

Well, your previous post says nothing useful, whether the patch works
or not, so I assumed that it's just a dead end without any answer.

If it's a positive result, then please give the precise information
again.  No information came out on alsa-devel ML yet, unfortunately
(at least it didn't reach to me).

thanks,

Takashi