Re: spitz (zaurus sl-c3000) support

From: Richard Purdie
Date: Thu Oct 13 2005 - 03:34:42 EST

On Thu, 2005-10-13 at 01:39 +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.
> Is there chance to get preview version somewhere? 2.6-capable userland
> would be very nice (and zImage would help, too, just for a demo :-).

I'm no sure offical preview images exist but here's something I built
myself recently:

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.

I'm hoping these work - I'm not sure I've tried one of them... :)

> I was thinking about "huh, is this machine tosa or spitz", but it is
> labeled SL-C3000, so it should be spitz.

Correct. Tosa is SL-C6000.

> Wildly offtopic... I got poweradapter with spitz (with funny design)
> that says 100V (and lot of japanese letters).. I guess it would be
> very bad idea to try it at 240V?

Trust me, its a very bad idea...

> > This file should give you an idea of which patches to apply in what
> > order:
> >
> Quite a long list; what is $RPSRC -- that is where are those patches
> really placed?

Its declared in:

so $RPSRC =

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

> Yes, asm/arch/ohci.h seems to be missing... But I should probably do
> update, I'm at rc2 with my zaurus hacks now.

That's still a problem although a patch queued for 2.6.15 will add that
file so I'm in two minds as to what to do with it. There's also an issue
with struct pxafb_device which I've agreed a solution to, just need to
write the patch and I think a reference to the battery device sneaked
into mainline when it shouldn't have done.

> Is there some way I can help you (besides obviously testing)?

I'm open to any help in getting the none ipaq/tosa things merged with
mainline. Have a look through them patch series and see if there's
anything you fancy taking on. Most of them are simple fixes although
some are nasty hacks we need to find some way of doing nicely.

The biggest thing is the battery/power management patch. I've just
agreed some changes to enable it to stand a chance of making mainline.
It probably needs more coding style cleanup.

There's also sound to get working although so code arrived yesterday
which should help with that. The usb client code exists in's kernel26 cvs tree. We need to extract it, fix any bugs
and talk to the usb developers about it.

Its a shame you don't have a C1000 as there's a nasty bit of coding
someone with such a device needs to do to complete mainline 2.6 support
(I2C driver for its IO Expander to enable access to its extra GPIOs).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at