Porting Pdaxrom To C3000 ... Quite Close But ...

[terryleung83]

really great!
this is the greatest news for all 3k user
it has been a long waited port for the c3k

i really want to see the hardware supported list  can i?

[ThC]

I dont understand how could I make a supported hardware list even before building my kernel  ... btw I've activated the same options as other pdaXrom kernels so it should support the same hardware, so except most of the wifi b and bluetooth hardware to be suported as well as most usb devices ... -sorry I didn't found any supported hardware list for pdaXrom.

I can post my config file if you want btw so you can figure out if your hardware should be supported

A quick update as I would like to have some advices about some idea I'm not very sure :

I don't know if I'll keep the original hdimage1.tgz format or if I rework it as

1) hdimage1.tgz's format is a hassle to rebuild and it will be a hassle to include the building of this file in the pdaXbuilder (will only take more time btw)

2) Keeping the original format will force me to add another step in the pdaXrom's updater.sh script to handle formating the hdd2 part so it will be respawn at first boot without any additional user input (well ... even if I change it's format I'll have to rewrite the whole hdimage1.tgz file handling in the updater.sh script btw)

3) If I remake it the way I want, the installation process will be a little longer (will have to extract hdd1 and hdd2 content at the same time) but first boot will be faster (no need to uncompress hdd2 content during first boot any more) (btw I may also be able to achieve this one too with a little more scripting and keeping the original format)

4) If I remake it, it won't be compatible anymore with a "standard" updater.sh script (btw as for now it need the pdaXrom's updater.sh script to handle resizing of flash partitions but I'm still not sure if it will be needed in the final release)

any advice or other idea ?

[drnick]

I think that you should keep the hdimage1 the same as pdaX in so far as it would still be compatable with both existing pdaX apps, and considering allowances for the pdaX team to release new versions of pdaX easily for the c3000.  It shouldnt be a problem for the dev's to treat the c3000 as a supported model with your build scripts.

[ThC]

pdaX doesn't use any hdimage1.tgz at the moment as the c3000 is the only model that need it ... so in any case I have to add the hdimage1.tgz file generation in the pdaXbuilder so I can make it exactly as I want it to be ... the compatibility concern is with sharp's original updater.sh, not with pdaXrom's one (as I'll also submit my modified updater.sh script to pdaX team and it will be usable with any model)

[pyknite]

just one another question... about when can you realese the firste beta???

++

[ThC]

I really don't know as I still don't even have a working kernel .... so it will be "When It's Done"

I could already have released a kind of "beta" but it wouldn't be usable as it is now : kernel is not fully working with the rest of the system as it's not compilled using the same libc and I still have a few other configuration problems as I have to cope in the same time with kernel config/compilation , pdaXbuilder dev environment configuration/mods to add c3000 branch, c3000's system hacking to get sure I understood everything about the booting process, replying to people telling me they want to help and who then won't ever reply when I tell them what kind of help is needed ...
I do really need some help as Sashz is a very busy person and I sometimes have only questions that I'm asking to myself and need someone to help me make a decision but don't have anyone to rely on ... I tryed posting my questions here but people seems either not confident enough in themselves to answer or maybe sometimes just not knowing/understanding what I'm talking about (I can understand if some people here don't understand my english )

Btw, please understand that making a full rom alone is quite a long process so please be patient (especially if you can't help with dev)

PS : As I already told in this topic, I'll try my best to have a fully working beta out for christmas to make you all a nice present  ... btw, to be able to do so, I may need someone able to compile a kernel for me using pdaXbuilder as mine is still not fully set up (still have problems with toolchain for kernel), please contact me I'll send you the kernel config file for spitz

[ThC]

Quick status update : now have a working build environment and starting editing config files to add c3000 branch into pdaXbuilder ... I'll also try compilling a new kernel and will so hopefully be able to release a beta real soon  (btw don't expect it to be fully functionnal, it will be a REAL beta and I will need feedback and maybe solutions from it )

[pyknite]

yeah great news

sry for help, but i'm to noob in linux world to help you (my coding level is very basic  )

but for the beta, i can give you a feedback

++

ps: in the beta, the wireless will work?

[ThC]

It *should* work as everything else ... btw actually the kernel doesn't seem to compile well (lots of errors with ads7846_ts driver then make ends with error 2) ...

[someonehoi]

HI,ThC

What is your pdaxrom version that you tried to install in C3000?
Before i tried to install rc8 and 10 into C3000 with SharpRom/Pdaxrom Dual boot in hdd4(that divided from hdd3)
But rc8 and 10 didn't work.
Finally,i installed rc12,pdaxrom could run.
The problem is that each time before i start pdaxrom,
i must mount hdd4 and chroot.
If i dont mount hdd4, the pdaxrom will not start.
If i mount hdd4 and no chroot, the pdaxrom starts as Twm.
If i mount hdd4 and chroot, the pdaxrom starts as Matchbox.

I havent test the pdaxrom function in C3000 yet.

[juanitomaille]

ThC, I couldn't help you for developing, but I hope i will be able to help you with my feedback.
Et tant pis si ce n'est pas pret pour Noel, ne gâche pas tes fetes ;-)

Jean.

[ThC]

@someonehoi : I'm not trying just to "install" it using a chroot or whatever, I'm trying to make it install using an updater.sh and everything so it can work on anyone's Zaurus even those who don't even know what chroot is

@juanitomaille : t'en fais pas j'ai tout mon temps pour faire ce que je veux entre 2 compilations

status update : I compiled a kernel well but was unable to boot with it ... btw it seems  Iforgot one step with the builder so I'm rebuilding it ... so stay tuned for news as if it's work I'm making the beta overnight (well .. overnight here in france as it's 11.18PM ^^)

[elektron]

status update : I compiled a kernel well but was unable to boot with it ... btw it seems  Iforgot one step with the builder so I'm rebuilding it ... so stay tuned for news as if it's work I'm making the beta overnight (well .. overnight here in france as it's 11.18PM ^^)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=108142\"][{POST_SNAPBACK}][/a][/div]

/me jumps for joy !!!


will be around to test. :-)

[pyknite]

ahh tu parle francais.... ca va me faciliter la tache

t'aurais pas une traduction de ton tuto sur le dual boot par hasard???

++

[ThC]

quick status update : I've underestimated the compile time needed to rebuild a complete pdaXrom image so it's still compiling but it seems I got rid of all the compile errors/problems I had (thanks to Sashz being once again very helpfull correcting some of my config files)  So I'm crossing fingers the kernel will work well (well ... at least boot   ) so it can be ready very soon (once I have a working kernel it's just a matter to package it in the installer and find somewhere to upload it as everything else is ready for the beta  

@pyknite : j'en ai pas de prêt sous le coude mais tu peux me pm en français pour parler de ce qui te pose problème (je referrais eventuelement un tuto en fr qd j'aurais un peu plus de temps ^^)