linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: "Ramón Rey Vicente󮠒" <retes_simbad@yahoo.es>
Cc: Andrew Morton <akpm@osdl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: 2.6.0-test1-mm1
Date: Wed, 16 Jul 2003 19:56:40 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0307161950000.32541@montezuma.mastecende.com> (raw)
In-Reply-To: <1058397925.1794.4.camel@debian>

On Wed, 17 Jul 2003, Ramón Rey [UTF-8] Vicente[UTF-8] ó® ^R wrote:

> > > Well, my desktop experience with this is good. But the music playing
> > > problems (aka mp3/ogg playing problems) still there. Its better, and I
> > > feel the problems are near to be solved, but the player still jumps..
> > 
> > How fast is your processor?
> 
> My system:
> 
> k6-2 450MHz
> 256 MB SDRAM pc100
> ide udma33
> aty rage fury pro 64 MB 
> running Xfree86 4.3 +  gnome2.2 all the time :)
> 
> This problems with mp3/ogg playing is not reproducible with 2.4.x and
> 2.2 series, only have it with 2.5.x and 2.6.0-test1

Your system looks fine, but slower boxes seem to be suffering a bit more, 
i get somewhat bad skipping on most my boxes which are in the 400-600MHz 
range although all of them have > 512MB of RAM and at least UDMA33

-- 
function.linuxpower.ca

  reply	other threads:[~2003-07-16 23:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16  5:56 2.6.0-test1-mm1 Andrew Morton
2003-07-16  6:16 ` 2.6.0-test1-mm1 Joshua Kwan
2003-07-16  6:22   ` 2.6.0-test1-mm1 Andrew Morton
2003-07-16  8:07 ` 2.6.0-test1-mm1 Sean Neakums
2003-07-16  8:55   ` 2.6.0-test1-mm1 Ingo Molnar
2003-07-16 10:19     ` 2.6.0-test1-mm1 Antonio Vargas
2003-07-16 13:37       ` 2.6.0-test1-mm1 Helge Hafting
2003-07-16 14:24         ` 2.6.0-test1-mm1 Antonio Vargas
2003-07-16  9:15   ` 2.6.0-test1-mm1 Con Kolivas
2003-07-16 10:44 ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 10:58   ` 2.6.0-test1-mm1 Andrew Morton
2003-07-16 12:24     ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 14:32       ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 14:41         ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 15:02           ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 15:09             ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 16:38               ` 2.6.0-test1-mm1 Andrew Morton
2003-07-16 14:03     ` 2.6.0-test1-mm1 Barry K. Nathan
2003-07-16 12:53 ` 2.6.0-test1-mm1 Philippe Gramoullé
2003-07-16 17:21 ` 2.6.0-test1-mm1 Ramón Rey Vicente󮠒
2003-07-16 19:01   ` 2.6.0-test1-mm1 Zwane Mwaikambo
2003-07-16 23:25     ` 2.6.0-test1-mm1 Ramón Rey Vicente󮠒
2003-07-16 23:56       ` Zwane Mwaikambo [this message]
2003-07-16 22:02 ` 2.6.0-test1-mm1 Mike Fedyk
2003-07-16 22:08   ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 22:17     ` 2.6.0-test1-mm1 Mike Fedyk
2003-07-16 22:36   ` 2.6.0-test1-mm1 William Lee Irwin III
2003-07-16 22:56     ` 2.6.0-test1-mm1 Mike Fedyk
2003-07-17 11:57 2.6.0-test1-mm1 Downing, Thomas
2003-07-20 18:50 2.6.0-test1-mm1 Downing, Thomas

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=Pine.LNX.4.53.0307161950000.32541@montezuma.mastecende.com \
    --to=zwane@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=retes_simbad@yahoo.es \
    /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).