From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@suse.cz>
Cc: lenz@cs.wisc.edu, zaurus@orca.cx,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: spitz (zaurus sl-c3000) support
Date: Fri, 14 Oct 2005 00:02:26 +0100 [thread overview]
Message-ID: <1129244547.8238.100.camel@localhost.localdomain> (raw)
In-Reply-To: <20051013224419.GF1876@elf.ucw.cz>
On Fri, 2005-10-14 at 00:44 +0200, Pavel Machek wrote:
> Thanks. Kernel works, even with 3.5.3 opie. [But touchscreen gets
> extremely interesting, you have to click top-right corner to get it to
> register click in bottom-left].
Yes, there's a bug in the opie (qte specifically) calibration code which
is fixed in 3.5.4 (I fixed it). I ended up replacing qte's algorithm
with a decent 5 point one.
> > Rename the gpe or opie file "hdimage1.tgz" to flash depending on what
> > flavoured image you'd like. You need the other files including gnu-tar.
> > You don't need an initrd.bin file as under 2.6 we can boot directly from
> > the microdrive.
>
> You mean I should place tar binary on flashcard, because updater.sh
> needs it? [What is updater.sh anyway, xor 0x5e encrypted shell
> script?!]
Yes, place the file as gnu.tar on the flashcard with updater.sh.
updater.sh is indeed an "encrypted" shell script! There are tools around
to decode/encode it.
> 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...
Cheers,
Richard
next prev parent reply other threads:[~2005-10-13 23:03 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 [this message]
2005-10-18 8:15 ` Pavel Machek
2005-10-22 13:56 ` Richard Purdie
2005-10-22 14:24 ` Pavel Machek
[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=1129244547.8238.100.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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.