From: Pavel Machek <pavel@ucw.cz>
To: Cyril Hrubi? <metan@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>,
rpurdie@rpsys.net, lenz@cs.wisc.edu, Dirk@opfer-online.de,
arminlitzel@web.de, pavel.urban@ct.cz, thommycheck@gmail.com,
milan@ucw.cz
Subject: Re: 2.6.29-rc1 on zaurus (spitz)
Date: Sun, 22 Feb 2009 14:56:51 +0100 [thread overview]
Message-ID: <20090222135651.GD1387@ucw.cz> (raw)
In-Reply-To: <dc2200690902121322l4e16cf84h25d2871ca80c37a3@mail.gmail.com>
On Thu 2009-02-12 22:22:37, Cyril Hrubi? wrote:
> Hi,
> 2.6.29-rc4 boots on spitz and looks overall good but framebuffer
> redraws some lines terribly slow. When I'm editing text in bash from
> the middle in some cases I can see redrawing the text pixel by pixel.
> And suspend to ram on pressing On/Off button does nothing now (some
> missing config option?).
Hmm, it gets worse: echo mem > /sys/power/state sleeps 2.6.28, but
there's no way to resume it.
About hda timeouts... I remember seeing them under older kernels, too,
under loads such as kernel compile... plus keypresses tend to get lost
under high loads :-(.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-02-22 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 11:38 2.6.29-rc1 on zaurus (spitz) Pavel Machek
2009-01-28 19:47 ` Russell King
2009-01-30 20:49 ` Pavel Machek
2009-02-12 22:20 ` Cyril Hrubiš
2009-02-12 21:22 ` Cyril Hrubiš
2009-02-22 13:24 ` Pavel Machek
2009-02-22 13:56 ` Pavel Machek [this message]
2009-02-22 14:23 ` Russell King
2009-02-23 15:21 ` Richard Purdie
2009-03-14 16:24 ` Pavel Machek
2009-03-17 19:19 ` Russell King
2009-03-29 11:11 ` Pavel Machek
2009-03-17 19:22 ` Russell King
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=20090222135651.GD1387@ucw.cz \
--to=pavel@ucw.cz \
--cc=Dirk@opfer-online.de \
--cc=arminlitzel@web.de \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=milan@ucw.cz \
--cc=pavel.urban@ct.cz \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.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.