Lineo's 2.4.20 Kernel Mess

[albertr]

Anyone knows what's the list of patches which lineo applied on top of 2.4.20 for thier c3000/c1000 releases?

I'm trying to figure out what are hardware-specific changes for c3000/c1000, but it looks like besides that, lineo took a freedom of applying  a zillion of non-hardware specific patches, that makes it a whole lot harder to see...
-albertr

[Mickeyl]

My guess is 2.4.18-rmk7-pxa3-embedix-<sl6000> + mainline diff 2.4.18->2.4.20.

It's ugly. Please don't waste too much time with it but instead help us to recruit someone porting the 2.6.11 C7x0 Zaurus support to the CXK models.

[guylhem]

I second mickeyl suggestion.
Been there, done that. Lost time. Albertr - just don't.

[albertr]

My guess is 2.4.18-rmk7-pxa3-embedix-<sl6000> + mainline diff 2.4.18->2.4.20.

Well, guess this path would make sense for Lineo, eh?

I'm not sure that I'm good enough to be able to do something useful for 2.6 - I didn't follow linux kernel development for years, and now a way behind on all recent changes. However, since I'll be getting a c1000 soon, I'll try to visit this forum more often, and hopefully would be able to contribute in sharing technical information on c1000 and related matters...
-albertr

[ciro]

My guess is 2.4.18-rmk7-pxa3-embedix-<sl6000> + mainline diff 2.4.18->2.4.20.

It's ugly. Please don't waste too much time with it but instead help us to recruit someone porting the 2.6.11 C7x0 Zaurus support to the CXK models.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=76753\"][{POST_SNAPBACK}][/a][/div]

Is 2.6 already able to boot on C3K?

[Mickeyl]

Is 2.6 already able to boot on C3K?

No. There's a lot of common Zaurus code in mainline, however machine support belongs to the few parts which has to be done specifically for every board. To my knowledge, no one started with supporting CXK* yet.

* I'm pretty confident that we are able to support both the Akita and the Spitz with the same kernel - like we do with the C7x0 kernel which supports all three corgi, shepherd, husky, and *cough* boxer.

[ciro]

Is 2.6 already able to boot on C3K?

No. There's a lot of common Zaurus code in mainline, however machine support belongs to the few parts which has to be done specifically for every board. To my knowledge, no one started with supporting CXK* yet.

* I'm pretty confident that we are able to support both the Akita and the Spitz with the same kernel - like we do with the C7x0 kernel which supports all three corgi, shepherd, husky, and *cough* boxer.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=76766\"][{POST_SNAPBACK}][/a][/div]

I think I'll be able to port some drivers, but I'm not ready to start with non-booting kernel. Do you have kdb or kgdb working on C7x0 models?

[Da_Blitz]

I would love to see 2.6.11 for the c3000, but i hate programing, i plan to build a distro around it when someone ports it

i am part of the axim x30 porting group (on www.handhelds.org) and we just recently modified the code for the x3 frame buffer to work for the x30's framebuffer (which uses the pxa frambuffer like the c3000) so thats done, all you have to do is change some setup registers for the lcd screen in the code and recompile, these can be dumped from linux as sharp nicly set the regesters up so we can see what the os is doing

looking over the hardware the design is nearly identical, the biggest hurdle for me is bricking my c3000 because as far as i can tell you need a working kernel to update the flash

so framebuffer driver is done, pcmcia works out of the box (built in drivers) i suppose the only things we should be concerned about is the sound (not a problem if its an ac97 codec) and touch screen? and perhaps the usb client/host and how to switch between them

i get the felling that the x30 and c3000 were designed by the same people (HTC)

[albertr]

looking over the hardware the design is nearly identical, the biggest hurdle for me is bricking my c3000 because as far as i can tell you need a working kernel to update the flash

so framebuffer driver is done, pcmcia works out of the box (built in drivers) i suppose the only things we should be concerned about is the sound (not a problem if its an ac97 codec) and touch screen? and perhaps the usb client/host and how to switch between them

i get the felling that the x30 and c3000 were designed by the same people (HTC)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=76897\"][{POST_SNAPBACK}][/a][/div]

There're quite a few different things among Sharp Zaurus SL-Cx000 and Dell Axim. Having the same CPU doesn't make them equal. And AFAIK Sharp does thier own hardware design, why wouldn't they?

The updater is located on a different NAND partition, and of course it's a different linux kernel. Unless you screw this partition, you should be able to boot it and then restore from there.
-albertr

[Mickeyl]

IIRC the maintenance area is duplicated in NOR, isn't it? That'd mean you can't brick your Zaurus per software at all.

[Da_Blitz]

so basiaclly the bootloader boots a protected (from erasure) kernel that boots anothe kernel (the one thats copied using updater.sh) if this is the case and i cant rewrite the first kernel then i will start testing tonight (can any one confirm this)

as for the hardware, after looking at the pictures you are right i should have genrelised and said nearly all pxa270 are neraly the same in terms of hardware and that thier is enogh in comman to be able to reuse code from other projects instead of rewirteing them from scratch

plus anyone made it to the mantince area, whats the key combo as i have tried parcticly everything to get it up and it doesnt work (i am talking about the manu that allows you to back up the flash not do a hard reset)

[lpotter]

plus anyone made it to the mantince area, whats the key combo as i have tried parcticly everything to get it up and it doesnt work (i am talking about the manu that allows you to back up the flash not do a hard reset)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=77017\"][{POST_SNAPBACK}][/a][/div]

m+d and hit the reset button in the battery compartment at the same time.

clear it from the 'extra menu' in the diag menu.