From: "M. Nentwig" <nentwig@users.sourceforge.net>
To: paul@linuxaudiosystems.com
Cc: alsa-devel@lists.sourceforge.net
Subject: Hammerfall DSP: Midi-related audio dropouts workaround / question
Date: Fri, 15 Nov 2002 08:45:33 +0200 [thread overview]
Message-ID: <3DD4980D.8C70735B@users.sourceforge.net> (raw)
Hello,
a couple of days I wrote about audio dropouts caused by MIDI data.
Now I found a workaround: Unloading the uhci (USB) driver, loading the
hammerfall driver, reloading the uhci driver gets rid of the dropouts.
Also plugging in a USB device helps. Both USB controller and hdsp share
the same interrupt on my laptop.
Before I found this workaround, I spent some time hacking the hdsp
driver. I created a new thread, that sleeps
('interruptible_sleep_on(sth)'), until the MIDI interrupt wakes it
('wake_up'(sth)). As long as it's doing no real work (just counting MIDI
events for example), everything works fine.
But as soon as I take the MIDI processing out of the interrupt (or
remove it completely), the machine locks up. Probably during the
interrupt - even the 'magic sysrq key' is dead. And I don't understand
this at all. Does the hardware crash, if I don't empty the MIDI FIFO
queue in time?
The crash occurs also, when MIDI processing is removed from a vanilla
hdsp driver.
Some related observations:
- The dropouts disappear, if I disable MIDI interrupts. But then MIDI in
is unreliable, big surprise.
- The dropouts don't get any better, if I don't submit the received data
to alsa at the end of the MIDI-in processing.
Regards
Markus
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
reply other threads:[~2002-11-15 6:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DD4980D.8C70735B@users.sourceforge.net \
--to=nentwig@users.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.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.