From: Ismael Valladolid Torres <ismael@sambara.org>
To: "Michel Dänzer" <daenzer@debian.org>
Cc: linux-audio-dev@music.columbia.edu,
linux-audio-user@music.columbia.edu,
alsa-devel@lists.sourceforge.net,
alsa-user@lists.sourceforge.net, debian-powerpc@lists.debian.org
Subject: Re: Measuring latency on my Apple G3
Date: Tue, 22 Jul 2003 13:32:55 +0200 [thread overview]
Message-ID: <3F1D20E7.6090002@sambara.org> (raw)
In-Reply-To: <1058833379.3754.71.camel@thor.holligenstrasse29.lan>
Michel Dänzer escribio el 22/07/03 02:22:
> Probably a GTK bug, not related to this thread.
I know, I know... ;)
> Which isn't very surprising, as they can use parts of the graphics chip
> that we don't have specs for, for one.
Sure. Only I remember having installed Mandrake 9.1, and I think video
performance was somewhat better. Maybe I am wrong and memory cheats...
> Beware that at least the low latency patch needs fiddling with
> arch/ppc/config.in to actually be enabled (check with grep LOLAT
> .config), and that the preempt patch (which I assume you mean by R.
> Love's) actually made things worse for me when I tried it on PPC a while
> ago. This may have been fixed in the meantime though.
You're right! First line in the patch file says:
arch/i386/config.in | 3 +
So the patch to the config.in file is only applied automatically for the
i386 architecture. Indeed CONFIG_LOLAT_SYSCTL was not in my .config, so
should I paste this manually into arch/ppc/config.in? Would this be enough?
And about the preempt, patch, well, it seems I still have enough tests
to perform so I can spend my holydays safely.
> YMMV
IJLUW (indeed, just like using Windows!) ;)
Regards, Ismael
prev parent reply other threads:[~2003-07-22 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 9:58 Measuring latency on my Apple G3 Ismael Valladolid Torres
2003-07-21 11:09 ` Michel Dänzer
2003-07-21 11:46 ` Ismael Valladolid Torres
2003-07-22 0:22 ` Michel Dänzer
2003-07-22 11:32 ` Ismael Valladolid Torres [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=3F1D20E7.6090002@sambara.org \
--to=ismael@sambara.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=daenzer@debian.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linux-audio-dev@music.columbia.edu \
--cc=linux-audio-user@music.columbia.edu \
/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.