mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Pavel Machek <pavel@ucw.cz>, Cyril Hrubi? <metan@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	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: Mon, 23 Feb 2009 15:21:23 +0000	[thread overview]
Message-ID: <1235402483.5386.39.camel@dax.rpnet.com> (raw)
In-Reply-To: <20090222142345.GA21948@flint.arm.linux.org.uk>

On Sun, 2009-02-22 at 14:23 +0000, Russell King wrote:
> On Sun, Feb 22, 2009 at 02:56:51PM +0100, Pavel Machek wrote:
> > 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.
> 
> Sounds like the on/off button isn't configured as a wakeup source.
> Without knowing anything about the platform (iow, where the on/off
> button is connected) it's hard to tell what could be the problem.

Its connected in through GPIO 0.

> Has the on/off button ever worked?

Yes, this always used to work fine for both suspending and resuming.

> > 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 :-(.
> 
> Really, what we need is for someone to step up to take on sorting out
> Zaurus.  Looking at this thread, it seems there's very few people here
> willing.  Also, I think Richard Purdie has moved on from Zaurus stuff.

Its really a time problem. I couldn't keep up with the PXA architecture
changes and give enough time to review and test them all effectively and
things have slipped from there. I've tried to provide input where I can
but would certainly welcome any help. My new employer means I'll be
doing less ARM work in general too for some reason...

Cheers,

Richard

-- 
Richard Purdie
Intel Open Source Technology Centre


  reply	other threads:[~2009-02-23 15:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 11:38 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
2009-02-22 14:23     ` Russell King
2009-02-23 15:21       ` Richard Purdie [this message]
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=1235402483.5386.39.camel@dax.rpnet.com \
    --to=rpurdie@rpsys.net \
    --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=pavel@ucw.cz \
    --cc=rmk+lkml@arm.linux.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®