From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Giuliano Pochini <pochini@denise.shiny.it>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Sound skips
Date: Mon, 26 Mar 2001 05:30:18 +0100 [thread overview]
Message-ID: <20010326043028.A162C2F090@apollo.valhalla.net> (raw)
>> there are a variety of things that can block for between 16 & 300 ms (not
>> necessarily IRQs).
>>
>> what size fragments are you using?
>
> 2K. I have to rise it to 8KB to work fine. My friend with the G4 still have
> very few interruptions even with 8KB.
OK.... if you can't do with such large fragments ....
You might want to try Andrew Morton's Low-Latency patch (URL:
http://www.uow.edu.au/~andrewm/linux/schedlat.html#downloads )
it makes things quite a lot better - but we still have a way to go on PPC
before we can achieve sub-ms block-free operation. Another thing on the
audio TODO list ;-)
let me/us know how you do if you try it (last time I did, the patches
applied cleanly to the PPC BK tree) - you (could at the time) ignore the
x86-specific mods to head.S.
HTH,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-03-26 4:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 4:30 Iain Sandoe [this message]
2001-03-26 7:17 ` Sound skips Giuliano Pochini
-- strict thread matches above, loose matches on Subject: below --
2001-04-09 9:34 Iain Sandoe
2001-04-08 14:52 Iain Sandoe
2001-04-09 7:56 ` Giuliano Pochini
2001-03-29 8:52 Iain Sandoe
2001-03-29 15:39 ` Giuliano Pochini
2001-04-07 20:39 ` Giuliano Pochini
2001-03-26 11:51 Iain Sandoe
2001-03-26 16:23 ` Geert Uytterhoeven
2001-03-26 8:56 Iain Sandoe
2001-03-26 10:34 ` Giuliano Pochini
2001-03-28 20:33 ` Giuliano Pochini
2001-03-24 19:45 Iain Sandoe
2001-03-25 19:41 ` Giuliano Pochini
2001-03-24 15:39 Giuliano Pochini
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=20010326043028.A162C2F090@apollo.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@denise.shiny.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).