From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Mack Subject: Re: How to add a new MIDI device to the usbaudio driver Date: Tue, 23 Aug 2011 11:22:52 +0200 Message-ID: References: <4E5234F0.8000502@amlie.name> <4E52401C.8030605@amlie.name> <4E53585D.9050004@amlie.name> <1314090212.3688.6.camel@mattotaupa> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail-yx0-f179.google.com (mail-yx0-f179.google.com [209.85.213.179]) by alsa0.perex.cz (Postfix) with ESMTP id 3138B1038FE for ; Tue, 23 Aug 2011 11:22:54 +0200 (CEST) Received: by yxk36 with SMTP id 36so2868386yxk.38 for ; Tue, 23 Aug 2011 02:22:53 -0700 (PDT) In-Reply-To: <1314090212.3688.6.camel@mattotaupa> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Paul Menzel Cc: Greg KH , alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On Tue, Aug 23, 2011 at 11:03 AM, Paul Menzel wrote: > Am Dienstag, den 23.08.2011, 10:43 +0200 schrieb Daniel Mack: >> On Tue, Aug 23, 2011 at 9:35 AM, Kristian Amlie wr= ote: >> > On 08/22/11 13:49, Daniel Mack wrote: >> >> It doesn't seem to be using a standard MIDI interface, but there's a >> >> chance that it accepts raw MIDI byte streams. Can you check the patch >> >> below? >> > >> > With that patch, the device shows up, but aseqdump does not report any >> > MIDI events after connecting to it. >> > >> > The Windows drivers are called "USB Serial Converter" and "USB Serial >> > Port", so maybe it's all wrapped in a different protocol. Does that na= me >> > ring a bell? >> >> That's possible, and it should be easy to support these type of >> devices in ALSA. However, some logic is neccessary to configure the >> hardware to its correct baud rate and hardware protocol. The easiest >> way to determine the setup sequence is certainly to sniff the Windows >> driver communication with some tool like usbsnoop. Can you give that a >> try? > > =85 and ask the manufacturer about GNU/Linux support. > > Something like, you bought the hardware and expect it to work > everywhere. Additionally they make money by selling the hardware and not > developing a driver, so they should publish the documentation and even > pay someone =96 like Daniel or Clemens ? =96 to write the support for the= ir > hardware. (Only when they say they do not have any money or something > like that, you can also tell them to donate/provide free hardware for > the developer and a contact address to their M$ Windows developer for > questions.) While I agree in general to your points, I think its not worth the effort in this particular case. It's probably very easy to add support for this by just sending one magic usb_control_msg up-front, and it's not complicated to sniff that value. From a customer standpoint, again, I'm sure the manufacturer will just state that they didn't promise any Linux support, and so you can't claim it. Daniel