[project]Port android to meizu M8

I dont get this funcking serial console to work man
Its not that i cat put in, i dont even get a prompt.
After start if initramfs /init shuld be started.
I just have #!/bin/sh and exec busybox --install -s and /bin/sh to get a console in there but kernel panic.
When i rename busybox zu init, or link it to init it starts. But not on serial line
*grmllassdasd*
How should i load drivers without console

[QUOTE=banxian;103418]I will finished moving today.
QUOTE]
So how do you like your new home?

Originally Posted by banxian

I think there may be no addon file required to support moviNand,
maybe directly treat it as MMC,

I was looking on more information about it, it seems that on xda dev they also had this issue but still did not find how they managed it
(a topic wih+100 pages ) but
i found this that could provide a clou:

Code:

s3c-linux.2.6.21 
---------------
To support movi-NAND 
-> drivers/mmc/mmc.c

and i found some other maybe interesting links :
Source Files for Android Development Environment
Community for ARM Evaluation Boards

r3wDy,
sorry i have no idea, the panic is a good sign since it show that the kernel works but why.. dunno.

Btw to the jtag thingie:
i was thinking on building a jtagfinder or buying an osciloscope
but then again it will be faster to desolder the chip from a broken device,
it would be more interestings since i can then desolder everything i want to test..
now it is just finding a broken m8..
SO IF ANYONE HASE A BROKEN M8 OR ONE TO DONATE PLEASE LET SOMETHING KNOW :-)

maybe i´m the only one...but i would donate 5-10 € for buying a device and finish your (great) work!

maybe you could set an paybal account where i can sent my money to!? maybe some others would give some money too?

let´s start a "support android" thread!?

Here we go:
http://www.meizume.com/modding-devel...tml#post103433

Hi,good guy
this is the M8_Android_portting_guide,it will help you!

M8_Android_portting_guide M8 ÒÆÖ²Ö¸ÄÏ,ÏÈ Äںˣ¬ÔÙ andorid Linux-Unix program 78ÍòÔ´´úÂëÏÂÔØ- www.pudn.com

s3c-linux.2.6.21
---------------
To support movi-NAND
-> drivers/mmc/mmc.c

Saw this one. if you look in the changelogs i postet there plenty of such texts which are leading to this. And if i look @ bootup of the kernel i see a nand driver from samsung loaded.

I talked to a co worker and we came to this: Windows maybe not on the movinand (the 8gb chip) but on another diskonchip device.
Dunno.
I first need to get busybox to work then i can see further.

When i start my m8 the kernel loads an then he most likely will start /init.
My busybox is linked to /sbin/sh and in my init script i just do exec /bin/busybox --install -s and /bin/sh to get it installed an to get a terminal. but this gives kernel panic. If i link my busybox direct to init so that bbox is called, i get a blinking cursor and no kernel panic..
Anyone with eneugh linux exp. to help out?

Hi,good guy
this is the meizu M8 Android portting guide,it will help you!
include drivers code
M8_Android_portting_guide M8 ÒÆÖ²Ö¸ÄÏ,ÏÈ Äںˣ¬ÔÙ andorid Linux-Unix program 78ÍòÔ´´úÂëÏÂÔØ- www.pudn.com

My email is yihui8@tom.com, if any question ,please contact my.

wtf porting guide.... id rather be carefull aboout this. i dont know if i would trust someone who has a file which all would need but no one found (till now)
and does such a spamin with this in the forums.... maybe someone who can download @ pudn could have a look in a virtual machine or sth what this actually is.
But id be carefull this is suspect to me

Originally Posted by bill

My email is yihui8@tom.com, if any question ,please contact my.

i remember that the one who uploaded the first android-M8 video on youku.com was "handsome-bill" ?!?!?! The video is gone now for some reason...but...

Are you the one? Is the work already done?

The files is 68kb in size, uploaded on 2009-09-17 and has never ben downloaded...
Maybe it has some good pointers but maybe it is just a copy of the Kandroid - Andoid porting guide

bill was so kind to email me this document. it really seems to be a porting guide. But its chinese
I hope banxian can have a look at this.

there is expleined how to configure a kernel and how to get the touchscreen,lcd and the flash chip device to work.
Most of these we have already done but the flash part could be very interesting.

So on the kernel side its not much more as we are right now (what more than a running android kernel could be there ), but there are very intersting clues init how we can get live easer and how we may get the flash chip to work.
if this helps and we could really access the flash chip we "just" had to ompile and install android.
On the files i saw uboot for m8 too maybe this could be interesting.

From this point on where we have a filesystem its explained how to get android up, this would be our next step then.

In that case i sincerely apologize to Bill!
Thank you for the Info

Originally Posted by r3wDy

bill was so kind to email me this document. it really seems to be a porting guide. But its chinese
I hope banxian can have a look at this.

there is expleined how to configure a kernel and how to get the touchscreen,lcd and the flash chip device to work.
Most of these we have already done but the flash part could be very interesting.

So on the kernel side its not much more as we are right now (what more than a running android kernel could be there ), but there are very intersting clues init how we can get live easer and how we may get the flash chip to work.
if this helps and we could really access the flash chip we "just" had to ompile and install android.
On the files i saw uboot for m8 too maybe this could be interesting.

From this point on where we have a filesystem its explained how to get android up, this would be our next step then.

sounds great :D may i ask what have to be done after android boots ?

I think after it boots there are stil many drivers that must be imported.
As far as i read in the guide i posted above Android devices are expected to have '5-way navigation with 5 application keys, power, camera and volume controls' which the M8 does not have, so that some of the keys need to be adapted to touchscreen input.
Also probably Sound drivers will be needed and who knows what Meizu did to the WLAN chipset on the SE version to suport WAPI, maybe that will need a specialized driver too.

hi bill,
i think you are new here, welcome.
Do you have experiences by yourself about android porting?
If so you could help a lot.

someone who can download @ pudn could have a look in a virtual machine or sth what this actually is.
But id be carefull this is suspect to me

i have an account, downloaded it.
so it contains indeed instructions but lots of them are in chinese(?),
no real proof of concept for m8 included
i think you should check it since it shows some info about Movinand, want me to upload it? It could be that bill has indeed working drivers for it..

Windows maybe not on the movinand (the 8gb chip) but on another diskonchip device.

not sure anymore, but i think i posted the same idea a while ago here.
My findings were that movienand is cut in 2 :
1 part /disk 1 part /windows
Since wince core is in NOR after flashing it loads it into ram + movinand while booting, with every restart /windows get formated...
Not sure ofcourse, that is why a test m8 would be usefull, we could desolder the movinand an hotwire it to a pc to dump content aswel...

Anyone with eneugh linux exp. to help out

enough experience, but not with busybox, i would say i will test it but my replacement m8 still needs to arrive
i must say that i think your kernel hangs while showing the blinking cursor, the panic means it is ok but something is missing, but what i can not say without testing it... i tried to load a normal xip in the m8 sdk emulator but it did not load, otherwise i could test it this way :@

video is gone now for some reason

i think Meizu launches take downs on everything that is not theirs, just like the fake fw 941 :P so maybe.. :P

edit :
please ignore some of my comments it seems that i needed to much time to post that you guys allready posted something else,
my apologies!

edit 2 :
pelase do not forget uboot is still tricky if we do not find the jtag..

movinand = SD card, mmc driver is OK

Windows maybe not on the movinand (the 8gb chip) but on another diskonchip device.

xip store all file as flat strcut, and use initobj.dat to build other directory n copy file into it.
you can call it norflash. Some rest of nor mounted as a `virtual` partition under ce, if you replace original files in windows, it get stock one inaccessible only.
My goal is dualboot, I don't think there is enough space / gap in side original xip(about 44~47M) to store our rootfs.
way1:
only M8TinyLoader injected into stock xip, both kernel/modules/rootfs/initramfs place on nand (with image or native file).
this may fit to normal user.
way2:
use the rest space in stock xip to store kernel/modules/initramfs, use entire nand as yaffs, and port yaffs support to windows ce.
this may useful to people which like to use android as primary os most times.
way3:
flash entire nor to android, we can use nand to store a DVD9 adult iso :P
@bill
do you have definations of Jtag? I think I must use Jlink to debug my loader for ripped touchscreen driver.

my thought about dualboot were just do it like we do with linux kernel. embedd nk.exe and linux kernel in nk exe. our code can decide where to jump.
Problem here would be get the nk.exe back in the stock fw

thx r3wDy. I have a look though on this guide. they maybe boot from power on jump, in other words can't flash back by power+music button.
this confilct my plan.
framebuffer porting is differnt from aesop one, too.
I must make a new usb cable with both usb pins/serial pins welded. because when I unplug / plug to check terminal / copy file, my cable get broken n repair n broken to death.

the jtag define is very helpful! thx bill, it saves our lots time/money to get it.

please let me ask a few questions:
(and please don´t get me wrong cause you´re doing a great job!!)

- why couldn´t we get the "finished-product" from bill if he is the one that loaded the videos up to youku? Android was running there if the video wasn´t a fake!?

- why is there a "port to m8 guide" and no android firmware leak to find out there?

- why do you have to work so hard? do you think that the one that writes the guide and took the videos has done the same work?