Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lasse Kärkkäinen" <tronic+8nhy@trn.iki.fi>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Roland/Edirol M-16DX
Date: Wed, 27 May 2009 23:49:43 +0300	[thread overview]
Message-ID: <4A1DA767.1030909@trn.iki.fi> (raw)
In-Reply-To: <s5hsklerlsa.wl%tiwai@suse.de>

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.

> 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.

  reply	other threads:[~2009-05-27 20:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17  9:29 Roland/Edirol M-16DX Lasse Kärkkäinen
2008-07-24  8:17 ` Clemens Ladisch
2008-11-10  3:53   ` Lasse Kärkkäinen
     [not found]     ` <491C6E10.7090308@trn.iki.fi>
     [not found]       ` <1226624101.4836.95.camel@localhost>
2008-11-14  8:12         ` Clemens Ladisch
2009-03-15  2:06   ` Lasse Kärkkäinen
2009-03-16  7:04     ` Takashi Iwai
2009-05-27 20:49       ` Lasse Kärkkäinen [this message]
2009-05-27 21:08         ` Takashi Iwai
2009-05-28 11:03           ` Lasse Kärkkäinen
2009-05-29  6:35             ` Takashi Iwai
2009-05-29 10:53               ` Lasse Kärkkäinen
2009-06-01  9:11                 ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2008-07-24  2:17 Lasse Kärkkäinen
2008-07-24  2:38 ` Jon Smirl
2015-10-23  8:27 Ricard Wanderlof
2015-10-23 11:01 ` Clemens Ladisch
2015-10-23 14:44   ` Ricard Wanderlof
2015-10-23 15:08     ` Clemens Ladisch
2015-10-24  5:51       ` Ricard Wanderlof
2015-11-12  7:58   ` Ricard Wanderlof
2015-11-12 12:38     ` 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=4A1DA767.1030909@trn.iki.fi \
    --to=tronic+8nhy@trn.iki.fi \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox