Re: spitz (zaurus sl-c3000) support
From: Pavel Machek
Date: Sat Oct 22 2005 - 09:47:01 EST
> > > > 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
> 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
# # >
# # Quite a long list; what is $RPSRC -- that is where are those
# # really placed?
#Its declared in:
# You probably don't need the ipaq hx2750 or tosa patches, they're
# part of my tree. The top 15 patches have been merged since -rc1 came
# (they were in the process of being merged at the time).
for A in pxa_i2c_fixes-r0.patch pxa_ohci_platform-r1.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
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
.... but that's ather poor trick. Few patches broke the download (slow
line here), and few of them broke compilation later...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/