Originally Posted by Alfred

Okay, let's say there were 3 versions of Thumb2 CSSU so far. when i installed 1st when i already had CSSU-T a few things got messed up (like i had only 4 desktops), but i didn't pay much attentions to that, because phone got responsiver and fast in overall. Then i updated and n900 bricked, so i did a clean install of the 2. version, without preinstalling CSSU-Testing. That went all well, and even "fixed" desktops and other little bugs. After that i updated to the last version, and phone slowed down say... 10 to 20 percent. But i will do a reflash today, and do another clean install of the last version available. Therefore i have a qusetion, do You think a eMMC reflash in this case is usefull, or shud i just reflash with a COMBINED image?

Keep in mind i didn't overclock in any of the cases...

Originally Posted by ivgalvez

A good proof of concept, apart from the already mentioned MicroB (browserd always loaded in memory) and Firefox, could be building Python with Thumb2.

Originally Posted by freemangordon

I will appreciate anyone willing to contribute, it is just not possible for me to recompile all of the packages in repos in a week . If anyone is willing to compile and test something specific, I can provide some guidance on how to setup SB with gcc 4.6.2 (it is really easy, a matter of setting up a new target)

Originally Posted by pablocrossa

Could you please provide a quick how-to and where to obtain the target files, much appreciated

Originally Posted by hxka

@szopin, not all of files in rootfs are ELFs.
It's bit tricky to count size of all ELFs in rootfs, I've ended up with this:

Code:

Nokia-N900:~# cat iself.sh 
#!/bin/sh
file "$1" | grep ": ELF" 2>&1 >/dev/null && echo "$1"
Nokia-N900:~# du -ch $(find / -xdev -type f -exec sh iself.sh {} \;) | tail -1
191.2M	total

And 30-40% is a reduction of code size, not resulting code size.
So, 345.6−191.2⋅0.4=269.12. Too much, even if not to take into account that not all of them are open source and can be recompiled, that partition size is 251.25 MB, not 256 and that filesystem iteslf require some space to store inodes and other stuff.

Originally Posted by szopin

freemangordon: Please open up a wikipage with detailed instructions for noobs on how to help out (list of parts that still need compilation...), the more step-by-step the better. I'm sure quite a few people would be willing to help the effort. EDIT: even if general steps, will be happy to update with what WFMed once I get to setting it up.

Originally Posted by XeonDead

even better than speedpatch