From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kristian Amlie Subject: Re: How to add a new MIDI device to the usbaudio driver Date: Tue, 23 Aug 2011 12:07:37 +0200 Message-ID: <4E537BE9.4050004@amlie.name> References: <4E5234F0.8000502@amlie.name> <4E52401C.8030605@amlie.name> <4E537524.9010303@ladisch.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by alsa0.perex.cz (Postfix) with SMTP id E5EF52462C for ; Tue, 23 Aug 2011 12:08:03 +0200 (CEST) In-Reply-To: <4E537524.9010303@ladisch.de> 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: Clemens Ladisch Cc: alsa-devel@alsa-project.org, Daniel Mack List-Id: alsa-devel@alsa-project.org On 08/23/11 11:38, Clemens Ladisch wrote: > Kristian Amlie wrote: >> idVendor 0x0403 Future Technology Devices International, Ltd >> idProduct 0xb8d8 > > There is a kernel driver for this chipset; try > "modprobe ftdi_sio product=0xb8d8". This will give you a serial port > which you can try to configure for the correct baud rate and see whether > MIDI bytes come out. (There is currently no mechanism to make a MIDI > device from such a serial port; this would require extending or creating > a driver.) Forgive me, I'm not very well acquainted with how serial drivers work in Linux. The driver did give me a new device, so here is what I tried: $ setserial /dev/ttyUSB0 spd_normal uart 16550A $ cat /dev/ttyUSB0 > dump I was not able to get any output from the serial device, however, while cat was running and I was pressing buttons on the instrument, it spontaneously changed program on me (MIDI program change), so *something* goes across the wire. -- Kristian