linux-kernel - Re: 2.6.29-rc1 on zaurus (spitz)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Feb 2009 15:21:23 +0000
From:	Richard Purdie <rpurdie@...ys.net>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	Pavel Machek <pavel@....cz>, Cyril Hrubi? <metan@....cz>,
	kernel list <linux-kernel@...r.kernel.org>, lenz@...wisc.edu,
	Dirk@...er-online.de, arminlitzel@....de, pavel.urban@...cz,
	thommycheck@...il.com, milan@....cz
Subject: Re: 2.6.29-rc1 on zaurus (spitz)

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/