From: Clemens Ladisch <clemens@ladisch.de>
To: Krzysztof Foltman <wdev@foltman.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: proposed MPD16 latency workaround
Date: Tue, 21 Sep 2010 13:22:32 +0200 [thread overview]
Message-ID: <4C989578.3030009@ladisch.de> (raw)
In-Reply-To: <4C988281.4010700@foltman.com>
Krzysztof Foltman wrote:
> Checked it yesterday. The data input works, however, the trying to
> output some sysex data with amidi prints the "bad dma" messages from the
> UHCI driver,
Never heard of that message.
> Also, either on disconnection or rmmod it OOPSes (can't tell which of
> them, it came up in the dmesg output but I couldn't do proper tests yet).
Might be the same problem with some DMA buffer ...
> That aside, why do you need URB_NO_FSBR flag for the URBs?
It's optional, so it isn't really needed. I'm using it for control
input transfers because those aren't latency sensitive, and using less
polling might help with the latency problem on the data input endpoint.
> I'll try to write a patch for all JACKs to blacklist the control device,
> that should take care of the JACK incompatibility.
In theory, Jack should never open any MIDI port that isn't actually used.
Regards,
Clemens
prev parent reply other threads:[~2010-09-21 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 23:21 proposed MPD16 latency workaround Krzysztof Foltman
2010-09-16 9:02 ` Clemens Ladisch
2010-09-16 13:37 ` Krzysztof Foltman
2010-09-20 7:23 ` Clemens Ladisch
2010-09-21 10:01 ` Krzysztof Foltman
2010-09-21 11:22 ` Clemens Ladisch [this message]
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=4C989578.3030009@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=wdev@foltman.com \
/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.