23/Sep: Kernel Source

[Guest Paul]

The ZTE Blade kernel source is available here:

http://support.zte.com.cn/support/news/New...?newsId=1000322

(thanks flibblesan)

P

[Guest Paul]

Has anyone compiled it yet?

My first quick go at compiling with the config from the device itself b0rked...

P

[Guest Paul]

  CC	  drivers/input/touchscreen/synaptics_i2c_rmi.o

drivers/input/touchscreen/synaptics_i2c_rmi.c:27:1: error: "swap" redefined

In file included from include/linux/cache.h:4,

				 from include/linux/time.h:7,

				 from include/linux/stat.h:60,

				 from include/linux/module.h:10,

				 from drivers/input/touchscreen/synaptics_i2c_rmi.c:16:

include/linux/kernel.h:483:1: error: this is the location of the previous definition

make[3]: *** [drivers/input/touchscreen/synaptics_i2c_rmi.o] Error 1

make[2]: *** [drivers/input/touchscreen] Error 2

make[1]: *** [drivers/input] Error 2

make: *** [drivers] Error 2[/code]

Bleh. Will look into it when I have more time. :lol:


P

[Guest rjm2k]

There's something fishy about the kernel sources, if you look at the news section they have released the kernel source for 3 phones, the blade, the sf and an N something or other, each one points to the same source. It might just be that they are doing a good job and having the same source for all phones, or it might not be the correct source

[Guest Simon O]

There's something fishy about the kernel sources, if you look at the news section they have released the kernel source for 3 phones, the blade, the sf and an N something or other, each one points to the same source. It might just be that they are doing a good job and having the same source for all phones, or it might not be the correct source

Nothing fishy as they are all basically the same phone.

We had problems compiling the code for the Pulse when the 1.5 code was released, but that was soon fixed.

[Guest rjm2k]

did you find that the config from your sf didn't match the options in the kernel so you were asked about new ones? just answered N to all, trying the build now

[Guest Simon O]

did you find that the config from your sf didn't match the options in the kernel so you were asked about new ones? just answered N to all, trying the build now

Yeah, same for me. But I didn't try building by saying no.

[Guest rjm2k]

Yeah, same for me. But I didn't try building by saying no.

did your build work? I assumed that the new values were for new phones, there seemed to be alternatives already set to y in the blade config

[Guest Simon O]

did your build work? I assumed that the new values were for new phones, there seemed to be alternatives already set to y in the blade config

I haven't tried compiling again. I'll do it later.

[Guest rjm2k]

I haven't tried compiling again. I'll do it later.

not finished compiling yet but I just commented out the duplicate definition of swap

[Guest rjm2k]

not finished compiling yet but I just commented out the duplicate definition of swap

hmmm

CC net/ipv6/af_inet6.o

net/ipv6/af_inet6.c: In function 'current_has_network':

net/ipv6/af_inet6.c:93: error: 'struct task_struct' has no member named 'euid'

make[2]: *** [net/ipv6/af_inet6.o] Error 1

make[1]: *** [net/ipv6] Error 2

make: *** [net] Error 2

rob@ubuntu:~/android/blade/kernel/kernel$

OK, changed Only allow certain groups to create sockets (ANDROID_PARANOID_NETWORK) to N in config

continuing...

Edited September 30, 2010 by rjm2k

[Guest rjm2k]

ok looks like the last step....

CC init/version.o

LD init/built-in.o

LD .tmp_vmlinux1

/home/rob/android/android-2.2.1_r1/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: no machine record defined

/home/rob/android/android-2.2.1_r1/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: no machine record defined

make: *** [.tmp_vmlinux1] Error 1

rob@ubuntu:~/android/blade/kernel/kernel$

any ideas?

[Guest Simon O]

ok looks like the last step....

CC init/version.o

LD init/built-in.o

LD .tmp_vmlinux1

/home/rob/android/android-2.2.1_r1/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: no machine record defined

/home/rob/android/android-2.2.1_r1/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-ld: no machine record defined

make: *** [.tmp_vmlinux1] Error 1

rob@ubuntu:~/android/blade/kernel/kernel$

any ideas?

Try http://android.modaco.com/index.php?s=&amp...t&p=1174778

[Guest rjm2k]

Will have a look, just compiled the Huawei 2.1 source with no problems at all so it's not my environment.

Might be worth firing an email off to ZTE letting them know the source they released doesn't work.

Edit

Oh dear, contacted them and got the usual useless response with them passing onto UK repair centre rather than their developers...

Dear customer, Thank you for contacting ZTE.

Regarding your inquiry, we would recommend that you'd better contact ourlocal service center in UK to get help.

The website:http://www.repairmob.com ;Tel：0800 028 0833 ;

Should you require any further assistance, please do not hesitate tocontact us!

Best Regards

Sincerely yours

Edited October 1, 2010 by rjm2k

[Guest BigBearMDC]

I had a look at the kernel source. It should be easy to overclock it once the kernel source compiles :lol:

Best regards,

BB

[Guest rjm2k]

Ok, I've managed to get the kernel to compile...

*1. Extract kernel source and cd to the directory

*2. Pull config from phone to .config, edit and unset anrdoid_parnoid_network (this gets rid of a build error)

*3. Edit ./Makefile, remove -Werror and -Werror from KBUILD_CFLAGS (note that the pulse makefile has these in and it

compiles ok, however these settings prevent board-msm7x27.c from compiling with an warning treated as an error error

about msm_camera and also a warning about a duplicate swap macro definition elsewhere)

*4. Edit ./arch/arm/mach-msm/Makefile , you need to uncomment the msm7x27 line!! suggests this kernel source is not

for the sf/blade

5. run make , you will be offered new config options,

answer

client side rpc Y

MT9T11X_Qtech N

WQVGA Y

I tried fastboot boot zImage but it didn't work so maybe more to do

[Guest Sebastian404]

Ok, I've managed to get the kernel to compile...

You JUST beat me to posting the same thing, however I have a diffreent step, that included copying the drivers/input/touchscreen/synaptics_i2c_rmi.c and /arch/arm/mach-msm/Makefile files from the HERO kernel...

but my kernel did not work either :lol:

Edited October 2, 2010 by Sebastian404

[Guest rjm2k]

not getting anywhere with ZTE, in response to my response to their response telling me to contact a UK phone repair company (for kernel source!) they have responded again telling me to contact the repair company. I do wonder how this world manages to work when there are so many incompetent people doing jobs!

[Guest Sebastian404]

not getting anywhere with ZTE, in response to my response to their response telling me to contact a UK phone repair company (for kernel source!) they have responded again telling me to contact the repair company. I do wonder how this world manages to work when there are so many incompetent people doing jobs!

Its more likely that the problem is lack of understanding... you could try contacting the UK phone repair company, if you can get your point across to them, they might bump it back up 2nd/3rd line support...

Or if you know someone Technically competent who speaks Chinese to explain it to them....

[Guest sorrowuk]

Its more likely that the problem is lack of understanding... you could try contacting the UK phone repair company, if you can get your point across to them, they might bump it back up 2nd/3rd line support...

Or if you know someone Technically competent who speaks Chinese to explain it to them....

How did paul make his custom rom, did he not have to compile this ?

[Guest Sebastian404]

I tried fastboot boot zImage but it didn't work so maybe more to do

I was double checking my environment, and I've found out that I cant do ' fastboot boot ' with the stock kernel/ramdisk......

you might want to check that's not your problem...

[Guest Paul]

Good work peeps, might be a little moot if we move to a .32 Froyo kernel!

P

[Guest Sebastian404]

I was double checking my environment, and I've found out that I cant do ' fastboot boot ' with the stock kernel/ramdisk......

you might want to check that's not your problem...

I've just been testing it, I can extra and rebuild and reflash the boot image from my droid with no problems... but following the same process on my Blade... it wont boot... interesting...

[Guest Paul]

Hmmm, got a kernel built, device won't boot tho... I wonder if this is the right kernel source!

P

[Guest rjm2k]

Hmmm, got a kernel built, device won't boot tho... I wonder if this is the right kernel source!

P

considering that the platform for the sf was commented out, I doubt it! I think we may need to rely on someone creating a kernel from aosp/cyanogen/aurora etc :)