public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: lenz@cs.wisc.edu, zaurus@orca.cx,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: spitz (zaurus sl-c3000) support
Date: Thu, 13 Oct 2005 00:14:24 +0100	[thread overview]
Message-ID: <1129158864.8340.20.camel@localhost.localdomain> (raw)
In-Reply-To: <20051012223036.GA3610@elf.ucw.cz>

On Thu, 2005-10-13 at 00:30 +0200, Pavel Machek wrote:
> 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.

oz 3.5.4 is due for release soon and will hopefully have a 2.6 option
for spitz.

> 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...

Its outdated now.

> Is there simple way to tell spitz and tosa apart (like without opening
> the machine)?

At what level? machine_is_spitz() and machine_is_tosa()? There are some
checks in the sharpsl head file to auto detect all the Zaurus machines
and set the machine numbers. For those two machines the difference is
the presence of the tc6393 chip in tosa. See head-sharpsl.S

> 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?

I got a spitz recently which moved 2.6 for it forwards a lot. Have a
look at:

http://www.rpsys.net/openzaurus/

This file should give you an idea of which patches to apply in what
order:
http://www.rpsys.net/openzaurus/temp/linux-openzaurus_2.6.14-rc1.bb

With my patch series applied, we're missing usb client (usb host works)
and sound support.

Mainline is missing power management and currently fails to compile
without my patch series but I'm working on that.

Richard


  reply	other threads:[~2005-10-12 23:14 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 [this message]
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=1129158864.8340.20.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox