From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Cc: Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Subject: 2.6.26.[6|7] vs. rt11 vs. alsa (usb) midi
Date: Sat, 25 Oct 2008 19:46:27 -0700 [thread overview]
Message-ID: <1224989187.3706.7.camel@localhost.localdomain> (raw)
Hi... anyone out there also having problem with this combination?
2.6.26.7 or 2.6.26.6 with 2.6.26.6-rt11 and alsa MIDI
It looks to me like alsa midi is broken.
Probably an interaction with the realtime kernel patch. A Fedora kernel
based on 2.6.26.6 (2.6.26.6-49 on fc8) works fine, a very similarly
patched kernel that includes the realtime patch does not. The
configurations for both are almost the same (today I tried to change
some of the most obvious differences and rebuild, with the same
result).
No problems with 2.6.24.7-rt21.
Test: boot, login, plugin an external usb keyboard (Yamaha P250), it is
recognized, use qjackctl alsa patchbay to connect it to kmidimon,
kmidimon sees only _one_ midi message and that's it. Kmidimon can't be
killed after that.
-- Fernando
next reply other threads:[~2008-10-26 2:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 2:46 Fernando Lopez-Lezcano [this message]
2008-10-27 8:13 ` 2.6.26.[6|7] vs. rt11 vs. alsa (usb) midi Takashi Iwai
2008-10-27 8:13 ` [alsa-devel] " Takashi Iwai
2008-10-27 11:29 ` Josep Andreu
2008-10-28 21:35 ` Fernando Lopez-Lezcano
2008-10-28 21:35 ` [alsa-devel] " Fernando Lopez-Lezcano
2008-10-29 11:10 ` Takashi Iwai
2008-10-29 11:10 ` [alsa-devel] " Takashi Iwai
2008-11-03 6:52 ` Fernando Lopez-Lezcano
2008-11-03 6:52 ` [alsa-devel] " Fernando Lopez-Lezcano
2008-11-05 7:43 ` Takashi Iwai
2008-11-05 7:43 ` [alsa-devel] " Takashi Iwai
2008-11-06 22:53 ` Fernando Lopez-Lezcano
2008-11-06 22:53 ` [alsa-devel] " Fernando Lopez-Lezcano
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=1224989187.3706.7.camel@localhost.localdomain \
--to=nando@ccrma.stanford.edu \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.