[alsa-devel] USB MIDI Regression? - - Was: Small Regression in midi for M-Audio Fast Track Ultra.
zonque at gmail.com
Sat Apr 23 11:09:53 CEST 2011
On Mon, Apr 18, 2011 at 10:37 AM, Felix Homann <linuxaudio at showlabor.de> wrote:
> Am 16.04.2011 04:29, schrieb Grant Diffey:
>> In 2.6.33/34 when support originally was put in alsa mainline the MIDI ports
>> were functional today they're not for me and I get the following in the
>> kernel log when using this card. (Audio all works acceptably.)
> I can confirm Grant's issue.
> They are not related to any code specific to the M-Audio Fast Track
> Ultra (FTU) series:
> Even after removing the FTU patches from current ALSA (git) the MIDI
> ports of the device will not be recognized.
> Switching back to my oldest installed kernel (2.6.32) the FTU will be
> recognized as a MIDI interface (but as expected the PCM ports will not
> be recognized.)
Hmm, between these version, there was my huge refactoring of the
usb-audio code, so this could indeed be related. However, most of my
patches were for the audio part, and not for MIDI.
> Just to make sure, that I'm not missing anything:
> * I've used 'amidi - l' to look for MIDI ports
> * Due to the deprecation of OSS in the kernel my Alsa configure line now
> includes '--with-oss=no --with-pcm-oss-plugins=no' which shouldn't have
> an effect but I mention it anyway
I would rather start off with two source trees of the kernel (one for
2.6.32 and one for any newer version that doesn't work anymore) and
then put lots of printk() lines to trace the functions. If you build
the driver as modules in both cases, you can easily add more debug
output on the fly without rebooting (some sort of "sudo rmmod ...;
make SUBDIRS=sound/usb; sudo insmod ..." is what I usually do).
I would like to help more, but it's difficult without access to the
hardware. Please let me know if you find out anything.
More information about the Alsa-devel