Opie on the 6000?

[usagi]

Does the OPIE work on the 6000?

[lpotter]

not yet. Work is being done on getting an openzaurus on the 6000, which is the first step in getting opie on it.

[duffman]

Do you know who is working on OZ for the 6000? If there\'s any guess when it\'ll be done? I hate to seem demanding, just anxious to try it out on my 6000

[DrWowe]

Do you know who is working on OZ for the 6000?

It could be you.  

[duffman]

It could be you.  

Hahah, I\'d love to, but I don\'t think my grasp of C/C++ (I\'m assuming that\'s the language it\'s written in?) is up to snuff.

[Mickeyl]

Hmm, I don\'t know why everyone assumes the need of C or C++ language to

 * use a build system which is made up of mostly small shell like build files
 * document
 * flash rootfs\'es and try to boot
 * debug packaging problems
 * etc.

Needed is interest, motivation, time, and common linux knowledge - nothing else. And if otherwise, given the first three necessities, you can learn everything, if you want.

[LilMikey]

You\'d need a Zaurus as well...

anyone care to help me out

[duffman]

Well sign me up then. I like to think I have a solid understanding of Linux and how it works, as far as programming goes, I have a foundation in perl and php and I do know some C/C++. As for time, that\'s a little more limited, but I definitly have the interest.

[palugeek]

Sign up where?  I would love to help.  I have only had my Zaurus for a month so I am a little behind the curve when it comes to all the software that was developed for the 5xxx\'s and flashing the ROM.  But I have more than 20 years experience with Unix / C programming and more than 10 years writing X server code.  I am particularly interested in the OPIE project because I want to run X windows on my 6000.

[lpotter]

i have a sl-6000 and am currently working on getting an openzaurus rom. It will probably be a buildroot package, as I have that working well and creating stable zaurus images.

[Mickeyl]

Feel free to work on OE to get an OZ for SL-6000. I already added the kernel, so it\'s just missing a few deviceisms.

I discourage people working on buildroot. It\'s outdated and unmaintained. It has no future and it won\'t help the OE project. On the contrary, if you manage to get it building oz images for sl6000 you will distract people from working on OE which means more fragmentation to the already pretty fragile OE community.

Yes, I can forsee your argument that you have to present anything working to your people asap, I know and I understand. Feel free to do that but please don\'t encourage potential volunteers to do the same.

[tonyb]

Mickey, I have a 6000L that I have been playing with.  Also been hanging and reading everything you guys haggle about at #oe.  Reminds me of my days at DARPA, hehe!

Latest oe building stuff fine for me.  Wondering if I could use the initrd.bin from 3.3.6-pre1 poodle, build a zaurus-pxa.conf  2.4 kernel with oe, then use updater.sh to burnit.  And have a fair chance of getting a login prompt!  Wondered if updater.sh, from poodle, would work with the 6000???

I\'d have to reconcile the lib/modules in initrd.bin, but that is easy for me since I can mount the jffs2 image fine in my devel system and update it, making sure I do not overflow it.  Then again, I could use the same poodle kernel?

That\'s all I need, cause I have my apps in 64MB CF, which I can mount at /mnt/CF

Thanks
TonyB (hufnus @ #oe)

[Mickeyl]

Disclaimer: I have no idea since I didn\'t touch this device yet.

The updater.sh looks for the code name, you have to add the tosa to it before you can use it to flash.
I have no idea how the mtd partitions are layed out on the NAND, so blindly using updater.sh calls for trouble.
You definitly can\'t use a poodle kernel, I have scanned through the tosa-patch and there are too much hardware differences,
it just won\'t work.
That said, an initrd.bin may work, but you won\'t have matching modules due to the different kernel.

[lpotter]

cat /proc/mtd:
dev:        size:              erasesize:        name:
mtd0:      006a0000      00020000       \"Filesystem\"
mtd1:      00700000      00004000       \"smf\"
mtd2:      01c00000      00004000        \"root\"
mtd3:      01d00000      00004000       \"home\"