All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: lenz@cs.wisc.edu, zaurus@orca.cx,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: spitz (zaurus sl-c3000) support
Date: Sat, 22 Oct 2005 16:24:44 +0200	[thread overview]
Message-ID: <20051022142444.GA1531@elf.ucw.cz> (raw)
In-Reply-To: <1129989418.8349.16.camel@localhost.localdomain>

Hi!

> > > > Oh, okay, one more question. Do you trust your battery charging code
> > > > enough to leave spitz overnight in charger? I would hate to be awaken
> > > > by angry lithium ;-).
> > > 
> > > My spitz has been left plugged in all the time with my charging code and
> > > has yet to explode. ;-) Its very similar to the c7x0 code which people
> > > have happily been using for a while in OpenZaurus c7x0 2.6. Spitz does
> > > contain a charging chip which should prevent major damage to the
> > > battery. The software just tries to help it along...
> > 
> > Charge led does not go off, but pavouk (has c7x0) told me that's
> > pretty much normal. It made me a bit nervous.
> 
> The charge LED should go off but it won't if the device isn't suspended
> as when running, the device draws enough current to keep the charger
> active.
> 
> Help on improving the charging code is of course welcome ;-)

Of course :-). Question: is there some reasonable way to get the spitz
patches, or maybe to just get all of your patches? I was doing

#!/bin/bash
# # >
#http://www.rpsys.net/openzaurus/temp/linux-openzaurus_2.6.14-rc1.bb
# #
# # Quite a long list; what is $RPSRC -- that is where are those
#patches
# # really placed?
#
#Its declared in:
#http://www.rpsys.net/openzaurus/temp/linux-openzaurus.inc

RPSRC=http://www.rpsys.net/openzaurus/patches

# You probably don't need the ipaq hx2750 or tosa patches, they're
just
# part of my tree. The top 15 patches have been merged since -rc1 came
out
# (they were in the process of being merged at the time).

for A in pxa_i2c_fixes-r0.patch pxa_ohci_platform-r1.patch
pxa_ohci_suspend-r0.patch poodle_irda-r0.patch
ide_not_removable-r0.patch sharpsl_pm-r8.patch corgi_pm-r4.patch
spitz_base_extras-r2.patch spitz_pm-r4.patch spitz_kbd_fix1-r0.patch
spitzcf-r3.patch pxa_timerfix-r0.patch pxa_remove_static-r0.patch
pxa_irda-r4.patch corgi_irda-r3.patch pxa_rtc-r1.patch
input_power-r2.patch jffs2_longfilename-r0.patch
sharpsl_bl_kick-r1.patch corgi_snd-r10.patch pxa2xx-ir-dma-r0.patch
tc6393-device-r5.patch tc6393_nand-r6.patch pcmcia_dev_ids-r2.patch
mmc_timeout-r0.patch pxa_cf_initorder_hack-r1.patch; do
#       wget $RPSRC/$A
    cat /data/l/zaurus/spitz.patches/$A | cg-patch
    pshell
done

.... but that's ather poor trick. Few patches broke the download (slow
line here), and few of them broke compilation later...

								Pavel
-- 
Thanks, Sharp!

  reply	other threads:[~2005-10-22 14:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-12 22:30 spitz (zaurus sl-c3000) support Pavel Machek
2005-10-12 23:14 ` Richard Purdie
2005-10-12 23:39   ` Pavel Machek
2005-10-13  8:33     ` Richard Purdie
2005-10-13 22:44       ` Pavel Machek
2005-10-13 23:02         ` Richard Purdie
2005-10-18  8:15           ` Pavel Machek
2005-10-22 13:56             ` Richard Purdie
2005-10-22 14:24               ` Pavel Machek [this message]
     [not found]     ` <1129194049.8238.26.camel@localhost.localdomain>
     [not found]       ` <20051013190724.GC1876@elf.ucw.cz>
2005-11-10  0:57         ` [MTD patch] Make sharp.c compile Richard Purdie
     [not found] <4WXqB-7X5-35@gated-at.bofh.it>
     [not found] ` <4WY3e-vQ-17@gated-at.bofh.it>
     [not found]   ` <4WYwf-14j-9@gated-at.bofh.it>
     [not found]     ` <4X6Nd-4LV-29@gated-at.bofh.it>
     [not found]       ` <4Xk3R-8an-25@gated-at.bofh.it>
     [not found]         ` <4Xkn5-jl-5@gated-at.bofh.it>
     [not found]           ` <4YURv-1sX-1@gated-at.bofh.it>
     [not found]             ` <50s4O-7HJ-9@gated-at.bofh.it>
     [not found]               ` <50sxP-8vu-5@gated-at.bofh.it>
2005-10-22 18:27                 ` spitz (zaurus sl-c3000) support Bodo Eggert

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=20051022142444.GA1531@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=zaurus@orca.cx \
    /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.