linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [suspend/resume] Re: userspace notification from module
Date: Sat, 16 Jan 2010 19:12:53 +0100	[thread overview]
Message-ID: <20100116181253.GC1603@ucw.cz> (raw)
In-Reply-To: <1263661258.6596.10.camel@utx.utx.cz>

On Sat 2010-01-16 18:00:58, Stanislav Brabec wrote:
> Eric Miao wrote:
> 
> > And the other way we may need to look into what API the current userland
> > apps on zaurus is depending on this 2.4 compatibility and make changes
> > slowly to those apps.
> 
> I guess that 2.4 compatibility is not an issue. Most modern Zaurus
> distributions are even unable to run Sharp ROM compatible binaries.
> 
> Distributions either stay on 2.4 kernel or use modern systems based on
> modern kernel 2.6 API.
> 
> Distributions that decided to migrate to kernel 2.6 are far from
> finished state. Any change that allows to use modern applications using
> standard kernel API is welcome.

There is no API involved. It is just ... if you leave zaurus in
 init=/bin/bash mode, it must not kill the battery. Smart and
 currently implemented way to do that is to suspend.

That's counterexample to rjw, but it does not matter -- reasonable
userland should never ever hit that, in a same way PCs should not hit
emergency power cut...
									Pavel

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

  reply	other threads:[~2010-01-16 18:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <686edb2c.6263643a.4b3f4a3b.b60b3@o2.pl>
     [not found] ` <201001022201.04281.rjw@sisk.pl>
     [not found]   ` <20100109103212.GA1429@ucw.cz>
     [not found]     ` <201001091440.46434.rjw@sisk.pl>
2010-01-15 20:03       ` [suspend/resume] Re: userspace notification from module Pavel Machek
2010-01-15 22:14         ` Rafael J. Wysocki
2010-01-16  3:00           ` Eric Miao
2010-01-16 17:00             ` Stanislav Brabec
2010-01-16 18:12               ` Pavel Machek [this message]
2010-01-16 22:05                 ` Rafael J. Wysocki
2010-01-16 22:19                   ` Pavel Machek
2010-01-16 22:25                     ` Pavel Machek
2010-01-16 22:31                       ` Rafael J. Wysocki
2010-01-16 22:26                     ` Rafael J. Wysocki
2010-01-17 13:07                       ` Pavel Machek
2010-01-17 13:26                         ` Russell King - ARM Linux
2010-01-19  5:15                           ` Pavel Machek
2010-01-16 22:32                   ` Russell King - ARM Linux
2010-01-16 18:12             ` Pavel Machek
2010-01-16 18:12           ` Pavel Machek
2010-01-16 22:07             ` Rafael J. Wysocki
2010-01-16 22:14               ` Pavel Machek
2010-01-16 22:21                 ` Rafael J. Wysocki

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=20100116181253.GC1603@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).