From: Pavel Machek <pavel@ucw.cz>
To: rpurdie@rpsys.net, lenz@cs.wisc.edu, zaurus@orca.cx,
kernel list <linux-kernel@vger.kernel.org>
Subject: spitz (zaurus sl-c3000) support
Date: Thu, 13 Oct 2005 00:30:36 +0200 [thread overview]
Message-ID: <20051012223036.GA3610@elf.ucw.cz> (raw)
Hi!
I got spitz machine today. I thought oz3.5.3 for spitz would be
2.6-based, but found out that I'm not _that_ fortunate.
What's the status of spitz? I see log from 2.6.12-rc boot, and pages
at http://www.orca.cx/zaurus/ seem to be old...
Is there simple way to tell spitz and tosa apart (like without opening
the machine)?
Aha, I realized that spitz support came into 2.6.14-rc2, so something
definitely _is_ happening. Are there newer patches than orca.cx
somewhere?
Pavel
--
Thanks, Sharp!
next reply other threads:[~2005-10-12 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 22:30 Pavel Machek [this message]
2005-10-12 23:14 ` spitz (zaurus sl-c3000) support 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
[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=20051012223036.GA3610@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.