From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@suse.cz>
Cc: John Lenz <lenz@cs.wisc.edu>,
kernel list <linux-kernel@vger.kernel.org>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [patch] Add suspend/resume support to locomo.c
Date: Sat, 10 Sep 2005 23:53:15 +0100 [thread overview]
Message-ID: <1126392795.8221.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20050910223805.GC1836@elf.ucw.cz>
On Sun, 2005-09-11 at 00:38 +0200, Pavel Machek wrote:
> [I have just came back from 3 days horse trip... you'll get replies to
> other mails later.]
>
> There's git tree at www.kernel.org/git ... its called linux-z. It
> worked for before I got to 2.6.13, but it is now broken (IIRC, maybe
> its okay). PCMCIA never worked for me. linux-z is probably good start
> for new work. It should have all your patches IIRC.
>
> I started work on battery control, and it does something, but I do not
> dare enabling charging juts yet.
It might be worth looking at:
http://www.rpsys.net/openzaurus/patches/sharpsl_pm-r8.patch
This is a more general and much cleaned up version of the Sharp power
management code. I've not studied the collie specifics so I don't know
how adaptable this would be for your uses. Examples of machine specific
support code are:
http://www.rpsys.net/openzaurus/patches/spitz_pm-r3.patch
http://www.rpsys.net/openzaurus/patches/corgi_pm-r3.patch
I'm still cleaning this up but its getting there...
Richard
next prev parent reply other threads:[~2005-09-10 22:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 5:25 Pavel Machek
2005-09-04 10:36 ` Russell King
2005-09-06 7:58 ` Pavel Machek
2005-09-08 13:42 ` Russell King
2005-09-08 23:29 ` John Lenz
2005-09-10 22:38 ` Pavel Machek
2005-09-10 22:53 ` Richard Purdie [this message]
2005-09-11 20:34 ` Pavel Machek
2005-09-11 22:51 ` Pavel Machek
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=1126392795.8221.13.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rmk+lkml@arm.linux.org.uk \
/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®