All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Stanislav Brabec <utx@penguin.cz>
Cc: Eric Miao <eric.y.miao@gmail.com>,
	Richard Purdie <rpurdie@rpsys.net>,
	lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>,
	Dirk@opfer-online.de, arminlitzel@web.de,
	Cyril Hrubis <metan@ucw.cz>,
	thommycheck@gmail.com,
	linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
	dbaryshkov@gmail.com, omegamoon@gmail.com, eric.miao@marvell.com,
	Andrea Adami <andrea.adami@gmail.com>
Subject: Re: Zaurus suspend saga
Date: Fri, 2 Oct 2009 06:13:46 +0200	[thread overview]
Message-ID: <20091002041346.GC1409@ucw.cz> (raw)
In-Reply-To: <1252323270.14911.20.camel@hammer.suse.cz>

On Mon 2009-09-07 13:34:29, Stanislav Brabec wrote:
> Pavel Machek wrote:
> 
> > Yep, zaurus is currently pretty broken; I don't think charging from
> > Linux works at all, so I simply power down back to bootloader for
> > charge.
> > 
> > Anyway, suspend/resume is currently more important for me than charge,
> > and I'd like to get at least that to work.
> > 
> > Could we apply the trivial patch from "zaurus c3000 aka spitz: fix
> > resume" , and preferably push it to linus for 2.6.31? One version
> > where kernel suspends/resumes would be good. 
> 
> I vote for applying Pavel's patch, as it fixes suspend/resume. Emergency
> suspend may happen later, when SPI will be fully resumed. If future
> fixes provide early SPI resume, then this patch may be reverted.
> 
> Tested-by: Stanislav Brabec <utx@penguin.cz>
> 
> ...
> 
> Remaining Zaurus SL-C3200 problems in the current vanilla (regressions
> are compared with 2.6.26-RP):

Yep :-(. More developers/testers needed. People breaking zaurus all
the time, probably because they don't have the hw.

Should I get listed as zaurus maintainer so that I get to see
zaurus-breaking patches before they hit the mainline?

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2009-10-02  7:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-06  5:26 Zaurus suspend saga Pavel Machek
2009-09-06 17:03 ` Rafael J. Wysocki
2009-09-06 18:01   ` Stanislav Brabec
2009-09-07 10:04   ` Pavel Machek
2009-09-06 22:29 ` Richard Purdie
2009-09-07  1:06   ` Eric Miao
2009-09-07 11:03     ` Pavel Machek
2009-09-07 11:34       ` Stanislav Brabec
2009-09-07 11:48         ` Russell King - ARM Linux
2009-09-16 12:25           ` Stanislav Brabec
2009-10-02  4:13         ` Pavel Machek [this message]
2009-10-02  7:36           ` Joe Perches
2009-09-07 12:05       ` Dmitry Eremin-Solenikov
2009-09-07 11:31   ` Pavel Machek
2009-09-07 13:10     ` Stanislav Brabec
2009-09-07 14:07       ` Richard Purdie
2009-09-07 14:52         ` Eric Miao
2009-09-07 20:36         ` Dmitry Eremin-Solenikov
2009-09-07 14:46       ` Eric Miao
2009-09-08 21:19       ` Pavel Machek
2009-09-08 21:53       ` Pavel Machek
2009-09-09  9:28         ` Stanislav Brabec

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=20091002041346.GC1409@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Dirk@opfer-online.de \
    --cc=andrea.adami@gmail.com \
    --cc=arminlitzel@web.de \
    --cc=dbaryshkov@gmail.com \
    --cc=eric.miao@marvell.com \
    --cc=eric.y.miao@gmail.com \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=metan@ucw.cz \
    --cc=omegamoon@gmail.com \
    --cc=rpurdie@rpsys.net \
    --cc=thommycheck@gmail.com \
    --cc=utx@penguin.cz \
    /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.