14 Sep
2005
14 Sep
'05
12:16 p.m.
On Wed, 14 Sep 2005 at 16:09 +0200, Florian Schmidt wrote:
On Wed, 14 Sep 2005 16:01:12 +0200
Florian Schmidt <mista.tapas(a)gmx.net> wrote:
Oops, hit send too early. I didn't mean "undefined". I actually meant
"out of range". When the pri is "undefined" as in "not specified
by
user", of course the default should be used.
BTW: i think it would make sense to raise the default prio to 70, which
would make jackd work better out of the box with RP kernels (which make
the prio of the irq handlers all around 50). Only thing left for the
user would then be to raise the soundcard irq handler prio.
That's good to know about, thanks. I googled and found your page
http://tapas.affenbande.org/?page_id=6 which shows me how to set the irq
handler prio, however my soundcard seems to be sharing with my video
card. Do you know a way to set which IRQs are used for devices? I have a
cs46xx card as well.
--
Hans Fugal | If more of us valued food and cheer and
http://hans.fugal.net/ | song above hoarded gold, it would be a
http://gdmxml.fugal.net/ | merrier world.
| -- J.R.R. Tolkien
---------------------------------------------------------------------
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460
Ok, I
understand that. So I take it if you set qjackctl priority to 0,
it will not specify it and therefore use the JACK default which is >=2?
I tried setting -P to 2 in qjackctl, and it works fine.
I suppose jackd should exit with an error when the prio is undefined. What