Guest daponte Posted June 6, 2011 Report Posted June 6, 2011 (edited) I wonder if it's possible to build kallt_kaffe's blade 2.6.32 kernel to work with our phone :D I feel a new experiment comming .... :D It doesn't even boot hehe. Oh well .. Edited June 6, 2011 by daponte
Guest cuttysark76 Posted June 7, 2011 Report Posted June 7, 2011 I wonder if it's possible to build kallt_kaffe's blade 2.6.32 kernel to work with our phone :D I feel a new experiment comming .... :D It doesn't even boot hehe. Oh well .. We need to fork is work... Change the boardconfig.mk and device.mk... change the name of files and specific drivers It has to boot! If we can boot original ROM's from Blade/Racer/Light etc... I've created a Github account and forked it... But no time or knowledge to proceed
Guest daponte Posted June 7, 2011 Report Posted June 7, 2011 Cool. If i create an account can i make changes to the files? I noticed our phone uses the same offsets as the Gen1 blade, gotta look into that. Ive been very busy too, hope I have vacations soon to learn more about this and do some new experiments :D
Guest cuttysark76 Posted June 7, 2011 Report Posted June 7, 2011 Cool. If i create an account can i make changes to the files? As far I understood, you need to install the Github app localy in your PC and change the files there, all changes will be synchronized. Create account > Fork > Install App localy > Download Fork > change and synchronize
Guest Sebastian404 Posted June 7, 2011 Report Posted June 7, 2011 We need to fork is work... Change the boardconfig.mk and device.mk... change the name of files and specific drivers Rather than modify the Blade's file, your better off duplicating the files for the joe and then modifiy those... have a look at the way I added support for the Racer to the Blade's kernel source and you should be able to see how that works... https://github.com/sebastian404/blade-kerne...603564487c6d586
Guest daponte Posted June 7, 2011 Report Posted June 7, 2011 (edited) Thanks Sebastian :D I will look into that when I get home. EDIT: Ufff, lots of errors comming from board-joe.c. I added this file to the blade-kernel, also board-joe-keypad.c and msm_usb_config.h. The error seems to come from around here lol. I'm a bit confused how are these errors occuring, since I'm using the same toolchain that I used for the 2.6.29 kernel. Maybe these files need to be declared elsewhere? arch/arm/mach-msm/board-joe.c:159: error: unknown field 'product_id' specified in initializer arch/arm/mach-msm/board-joe.c:160: error: unknown field 'functions' specified in initializer arch/arm/mach-msm/board-joe.c:160: warning: initialization makes pointer from integer without a cast arch/arm/mach-msm/board-joe.c:162: error: unknown field 'serial_number' specified in initializer arch/arm/mach-msm/board-joe.c:162: warning: initialization from incompatible pointer type arch/arm/mach-msm/board-joe.c:541: warning: initialization from incompatible pointer type arch/arm/mach-msm/board-joe.c: In function 'msm7x2x_init': arch/arm/mach-msm/board-joe.c:2422: error: 'struct kgsl_platform_data' has no member named 'max_axi_freq' arch/arm/mach-msm/board-joe.c:2482: error: implicit declaration of function 'rmt_storage_add_ramfs' arch/arm/mach-msm/board-joe.c:2491: error: too few arguments to function 'msm_pm_set_platform_data' arch/arm/mach-msm/board-joe.c:2493: error: too few arguments to function 'msm_pm_set_platform_data' make[1]: *** [arch/arm/mach-msm/board-joe.o] Error 1 make: *** [arch/arm/mach-msm] Error 2 make: *** Waiting for unfinished jobs.... Edited June 7, 2011 by daponte
Guest duranek Posted June 8, 2011 Report Posted June 8, 2011 Arkadaşlar googleandroid.gen.tr sitesinde uğraşıyoruz biz de romlarla kendi elimizden geldiğince. sizi de aramızda görmek isteriz hem hep beraber bu işi kotaracağımızı düşünüyorum..
Guest Sebastian404 Posted June 8, 2011 Report Posted June 8, 2011 Thanks Sebastian ;) I will look into that when I get home. EDIT: Ufff, lots of errors comming from board-joe.c. I added this file to the blade-kernel, also board-joe-keypad.c and msm_usb_config.h. The error seems to come from around here lol. I'm a bit confused how are these errors occuring, since I'm using the same toolchain that I used for the 2.6.29 kernel. Maybe these files need to be declared elsewhere? Where did you get board-joe.c from? The way I did it with the mooncake files was to the blades files, look at the source for the 2.6.29 device files and modify the blade ones based on that...
Guest Sebastian404 Posted June 8, 2011 Report Posted June 8, 2011 Looks like you guys get your own board.... http://android.modaco.com/category/535/vod...945-modaco-com/
Guest cuttysark76 Posted June 8, 2011 Report Posted June 8, 2011 Looks like you guys get your own board.... http://android.modaco.com/category/535/vod...945-modaco-com/ Great news! How do we migrate everything?
Guest daponte Posted June 8, 2011 Report Posted June 8, 2011 (edited) Where did you get board-joe.c from? The way I did it with the mooncake files was to the blades files, look at the source for the 2.6.29 device files and modify the blade ones based on that... I copied it from our 2.6.29 kernel, and I had to copy the board-joe-keypad.c and msm_usb_config.h too. Hummmm, so, you copied the blade board file and modified it for the racer, is that it? Cool, our own board ;) Free beers for everyone :P Edited June 8, 2011 by daponte
Guest cuttysark76 Posted June 8, 2011 Report Posted June 8, 2011 I copied it from our 2.6.29 kernel, and I had to copy the board-joe-keypad.c and msm_usb_config.h too. Hummmm, so, you copied the blade board file and modified it for the racer, is that it? Daponte, I would like cooperate with you... How can i help?
Guest daponte Posted June 8, 2011 Report Posted June 8, 2011 You could set up a build environment, then we can work through github, make changes to the code and try it and stuff ;)
Guest cuttysark76 Posted June 8, 2011 Report Posted June 8, 2011 You could set up a build environment, then we can work through github, make changes to the code and try it and stuff ;) I would like to replicate everything you have in order to reduce problems... Can you describe your build enviroment? Ubuntu? Version? Java? Google SDK? Virtual machine or Real? any Tutorial? I will set up it tonight! BR
Guest daponte Posted June 8, 2011 Report Posted June 8, 2011 (edited) I'm using Ubuntu 9.10 x64 on a virtual machine on my laptop. I have a full SDK sync on my disk, although I only used it to compile mkbootfs and mkbootimg so far. And I used the tutorial from AOSP page to install the required packages for the sdk to work. Then I downloaded the 2.6.29 kernel from ZTE's site, and added the modifications that Sebastian proposed. The touchscreen is unresponsive and camera doesn't work, but everything else is fine. On a side note, the 9.10 has a bug that prevents us to use the 4.4.3 toolchain, so I'm using the 4.4.0. I guess if you try another ubuntu distro it will not make much diference. If you need any help, just PM me or post here, I'll be following ;) BTW, I have java 6 (build 1.6.0_24-b07), should have 5, because 6 is for gingebread only. 5 is for froyo and older, but since I'm only currently compiling the kernel, I didn't changed that yet. Edited June 8, 2011 by daponte
Guest M.AkiF Posted June 8, 2011 Report Posted June 8, 2011 iyi iyi hadi bakam aslanlar çıkarın artık şu 2.2yi ;)
Guest Fadox Posted June 9, 2011 Report Posted June 9, 2011 Cuttysark76 and daponte, good luck on that job! Show those roms ;)
Guest ahmet__01 Posted June 9, 2011 Report Posted June 9, 2011 Cuttysark76 and daponte, good luck on that job! Show those roms :P +1 ;)
Guest cingibi Posted June 9, 2011 Report Posted June 9, 2011 I'm using Ubuntu 9.10 x64 on a virtual machine on my laptop. I have a full SDK sync on my disk, although I only used it to compile mkbootfs and mkbootimg so far. And I used the tutorial from AOSP page to install the required packages for the sdk to work. Then I downloaded the 2.6.29 kernel from ZTE's site, and added the modifications that Sebastian proposed. The touchscreen is unresponsive and camera doesn't work, but everything else is fine. On a side note, the 9.10 has a bug that prevents us to use the 4.4.3 toolchain, so I'm using the 4.4.0. I guess if you try another ubuntu distro it will not make much diference. If you need any help, just PM me or post here, I'll be following ;) BTW, I have java 6 (build 1.6.0_24-b07), should have 5, because 6 is for gingebread only. 5 is for froyo and older, but since I'm only currently compiling the kernel, I didn't changed that yet. ZTE JOE series-Eclair kernel(2.6.29) source code -- http://support.zte.com.cn/support/news/New...?newsId=1000382 its eclair source not froyo
Guest daponte Posted June 10, 2011 Report Posted June 10, 2011 Thanks for the support guys, but we're just learning this stuff, it could take a long time until we can make something. I did a few tests today again with the 2.6.32, managed to compile it, but it still doesn't boot.
Guest jyxrix Posted June 11, 2011 Report Posted June 11, 2011 it's MSM7227. So you could use wildfire repo of cm7 to compile a rom and inject your overlays. but you can also port any msm7227 rom w/o compiling. this its say bay neopeek user...
Guest jyxrix Posted June 12, 2011 Report Posted June 12, 2011 I asked for help in neopeek forum, and answered it .... Postby neopeek » Sun Jun 12, 2011 9:15 am which kernel do you use? Is 2,1 the maximum atm? or are there any 2.2/2.3 AOSP ROMs out? I am asking this regarding to a cm port... the link neopeek forum vodafone 945 "ZTE JOE"
Guest jyxrix Posted June 13, 2011 Report Posted June 13, 2011 Here you can find my bootable version of the ZTE N700 CDMA 2.2: joe_cdma_alpha_1 No touch screen Just for evaluation Dangerous Proceed carefully This site might help porting touchscreen drivers: http://lii-enac.fr/en/architecture/linux-i...roid-howto.html boa cuttysark76 eu como nao dou muito com o ingles, vou escrever em portugues... eu tive a ver a rom que alteraste para fazer boot e realmete funciona... e claro o touch screen nada. mas se reparares a primera vez aciona o laranja. mas nao faz mais nada. alterei isto no build.prop ro.sf.lcd_density=120 anteriormente tava assim ro.sf.lcd_density=160 ficou melhor a nivel de imagem... ;) ro.build.baseband_version=N606B01 ro.build.software_version=ZTE-C_N606V1.0.0B03 ro.build.sw_internal_version=N606V1.0.1B03 se repararmos aqui esta vercao e tirada do ZTE-C_N606 ja tem o android 2.2 de origem... por isso e que o touch screen nao deve funcionar...
Guest daponte Posted June 13, 2011 Report Posted June 13, 2011 Obrigado pelo link do forum, jyxrix, ja que tenho o ambiente para compilar o kernel vou la dar uma palavrinha:)
Guest jyxrix Posted June 13, 2011 Report Posted June 13, 2011 Obrigado pelo link do forum, jyxrix, ja que tenho o ambiente para compilar o kernel vou la dar uma palavrinha:) de nada.. eu tambem uso o vodafone 945, e parece ter grande potencial... e pena a vodafone nao dar assistencia, aos seu propios modelos...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now