Kernel used in CWM

[Guest t0mm13b]

Curiousity got the better of me and did some digging on the latest Clockwork and noticed a few things:

• Kernel was last built in January, after I extracted the kernel configuration

  # Sun Jan 30 22:51:44 2011

  :blink:
  

• There's no confirmed source to it - the configuration files does not match up with any source out there - TomG's, KK's, even the old kernel that was out by ZTE in early days of January. It is not even present in CyanogenMod's github either! :huh:
  
  
  This is leading me to wonder:
  
  

1. 
   
2. Where is the exact kernel source and why the configuration file layout different to the other versions of the source?
   
3. Would this be perceived as GPL violation if there's no sources? From what I've been rooting around, the source to the exact kernel version in which the configuration file can match up with, is, quite simply, not there!
   

And before anyone jumps to conclusion and point out TomG's, KK's or any other source, that is already there, I'd like to add that I have already tried to make it work with the CWM source which resulted in booting into recovery getting stuck, which has lead me to the conclusion that the exact version used in the CWM appears to work rather than any other source!

FWIW, I've gleaned in on it - its VMSPLIT2G, limited number of drivers (why wifi/tcpip compiled in or sound even which I do not understand why as its not practical in the context of Recovery)

If anyone knows where the exact version is please do drop the linky here as I'm curious to "optimize" the kernel :)

Edited August 20, 2011 by t0mm13b

[Guest t0mm13b]

To follow up on this:

Using the existing kernel config on any of existing kernel sources TomG's, KK, ZTE's own, when built, the zImage gets copied into device/zte/blade/recovery_kernel.

And the cm7's make recoveryimage command, then flashing it via fastboot, causes the recovery to get stuck, furthermore, shoving in the USB cable into it causes the handset to completely power down! :huh:

So what gives? Hence my posting!

Edited August 20, 2011 by t0mm13b

[Guest Simon O]

As I said on Twitter, Sebastian404 is your man. He compiles the recoveries at http://android.podtwo.com/recovery.php?device=blade

https://github.com/sebastian404/android_device_zte_blade is his github.

Kernel should be https://github.com/sebastian404/blade-kernel

the blade config in his repo is newer so I assume that the two kernel blobs in the device folder haven't been updated for a while.

[Guest t0mm13b]

As I said on Twitter, Sebastian404 is your man. He compiles the recoveries at http://android.podtwo.com/recovery.php?device=blade

https://github.com/sebastian404/android_device_zte_blade is his github.

Kernel should be https://github.com/sebastian404/blade-kernel

the blade config in his repo is newer so I assume that the two kernel blobs in the device folder haven't been updated for a while.

Ahh Cool!

Cheers for the linkys....

Speaking of which ... there should be a centralized topic listing of all kernels/sources as the search on this is awful!

Thanks again B)

[Guest Tom G]

Curiousity got the better of me and did some digging on the latest Clockwork and noticed a few things:

• Kernel was last built in January, after I extracted the kernel configuration

  # Sun Jan 30 22:51:44 2011

  :blink:
  

• There's no confirmed source to it - the configuration files does not match up with any source out there - TomG's, KK's, even the old kernel that was out by ZTE in early days of January. It is not even present in CyanogenMod's github either! :huh:
  
  
  This is leading me to wonder:
  
  

1. 
   
2. Where is the exact kernel source and why the configuration file layout different to the other versions of the source?
   
3. Would this be perceived as GPL violation if there's no sources? From what I've been rooting around, the source to the exact kernel version in which the configuration file can match up with, is, quite simply, not there!
   

And before anyone jumps to conclusion and point out TomG's, KK's or any other source, that is already there, I'd like to add that I have already tried to make it work with the CWM source which resulted in booting into recovery getting stuck, which has lead me to the conclusion that the exact version used in the CWM appears to work rather than any other source!

FWIW, I've gleaned in on it - its VMSPLIT2G, limited number of drivers (why wifi/tcpip compiled in or sound even which I do not understand why as its not practical in the context of Recovery)

If anyone knows where the exact version is please do drop the linky here as I'm curious to "optimize" the kernel :)

The CWM kernel in the CM7 source is built from my source (using the old branch). I'm not sure why the config date is incorrect, but the build date correctly shows "Tue Apr 12 18:07:13 PDT 2011".

[Guest t0mm13b]

The CWM kernel in the CM7 source is built from my source (using the old branch). I'm not sure why the config date is incorrect, but the build date correctly shows "Tue Apr 12 18:07:13 PDT 2011".

:huh:

@TomG:

Uhmmm I think you're getting mixed up - I am talking about the kernel used for the clockworkmod recovery... if you insist on saying that the CWM's own kernel is based on your old branch, then something is amiss - is it Sebastian's kernel source or yours?

[Guest wbaw]

:huh:

@TomG:

Uhmmm I think you're getting mixed up - I am talking about the kernel used for the clockworkmod recovery... if you insist on saying that the CWM's own kernel is based on your old branch, then something is amiss - is it Sebastian's kernel source or yours?

There are two different builds of cwm for the blade, the official cyanogen version available through Rom Manager, which uses Tom G's source & sebastian404's version which uses sebastian404's kernel.

Edited August 21, 2011 by wbaw

[Guest hecatae]

t0mm13b is trying to strip unnecessary drivers out of the recovery kernel to bring the size down, gets weird stuff happen when he does this, like:

have tried to optimize the cwm kernel by taking out wifi/sound

<t0mm13b> and used this command

<t0mm13b> mkbootimg --base 0x2600000 --kernel zImage --ramdisk recovery-clockwork-4.0.1.4-blade-gen2.img-ramdisk.gz --output newcwm.img

<t0mm13b> and flash that it gets stucked

and

and pluggin in the usb cable causes the handset to power off

the recovery kernel looks like it is 2g vmsplit.

[Guest t0mm13b]

To add my further opinion on this: the structure and cohesion of CM7 and the CWM recovery is very inconsistent. By default, cm7 code is 3g split.

So in order to get everything in harmony with a 2g split kernel, which means:

TARGET_USES_2G_VMSPLIT := true

I have to add the above to the BoardConfig.mk

And recompile the ENTIRE cm7 source ...like hello... why the inconsistency! :huh:

That IMHO sucks donkey balls.... :blink:

[Guest wbaw]

To add my further opinion on this: the structure and cohesion of CM7 and the CWM recovery is very inconsistent. By default, cm7 code is 3g split.

So in order to get everything in harmony with a 2g split kernel, which means:

TARGET_USES_2G_VMSPLIT := true

I have to add the above to the BoardConfig.mk

And recompile the ENTIRE cm7 source ...like hello... why the inconsistency! :huh:

That IMHO sucks donkey balls.... :blink:

I think it's because you're using the wrong version (sebastian's).

[Guest hecatae]

I think it's because you're using the wrong version (sebastian's).

hi,

repo sync -j16

lunch blade

make recoveryimage

from cm sources

then split the recovery.img using splitboot.img.pl

replace the kernel with a new 2g or 3g vmsplit kernel, rebuild recovery image, same issues occur here that t0mm13b has.

sorry wbaw there is nothing here that is sebastians version

[Guest sej7278]

There are two different builds of cwm for the blade, the official cyanogen version available through Rom Manager, which uses Tom G's source & sebastian404's version which uses sebastian404's kernel.

isn't that backwards - the rommanager version is koush's cwm 3.0.2.7, its not cyanogenmod's version.

i assume the cm7 cwm is sebastian404's as when you build it from cm7 sources its cwm-based 4.0.1.5 - which seems to still get commits from koush, but is a fork, but does seem to use tom_g's kernel

Edited August 21, 2011 by sej7278

[Guest Tom G]

isn't that backwards - the rommanager version is koush's cwm 3.0.2.7, its not cyanogenmod's version.

i assume the cm7 cwm is sebastian404's as when you build it from cm7 sources its cwm-based 4.0.1.5 - which seems to still get commits from koush, but is a fork, but does seem to use tom_g's kernel

The rommanager version is built from the cyanogenmod source, but the rommanager rom does not update automatically. It probably hasn't been updated since we moved to gen2 since nothing has really changed. I'll ask koush to update it.

I had trouble with sebastian's source back when I started playing with the blade, so I re-did the porting of cwm. There may be some minor differences between them but shouldn't be much. The recovery kernel in CM is built from my source.

[Guest sej7278]

The rommanager version is built from the cyanogenmod source, but the rommanager rom does not update automatically. It probably hasn't been updated since we moved to gen2 since nothing has really changed. I'll ask koush to update it.

that's interesting and may explain why when i installed cwm-based 4.0.1.5 from cm7 source over the top of cwm 3.0.2.7, rommanager on first install said i had no cwm installed and proceeded to install 3.0.2.7 (which it lists as the latest available).

[Guest Sebastian404]

I don't really use this forum as much as I used to....

but the kernel I use in my builds of clockwork mod has a bunch of stuff it dont need stripped out.. networking, wifi, camera, etc, etc...

There used to be a forum post that linked all the configs and stuff I used to build all of them, but Im not sure how to find it in the all new modaco...

But the source code I used from right off ZTE's website, totally untouched, and then KK's patches to get it to build for gen2 devices..

.config

arch/arm/mach-msm/board-zte-blade.c

arch/arm/mach-msm/Kconfig

arch/arm/mach-msm/Makefile.boot

I'm working on building a website for all my stuff, its slow going but I'm getting there, I'll include a post for the kernel info, mostly because your right about the GPL stuff...

[Guest Sebastian404]

I should also add, the kernel source on my github was more aimed at getting it working on other ZTE devices, not really that much use now...

And I've also officaly nothing to do with the 'offical' release of Clockwork Mod.. tho I did notice someone contributed 50% of my flipped screen fix to it... Applying the other 50% of the fix is in my versions build script.

I only really keep updating the blade version since I automated the build process and I support other devices that are not supported in the 'offical' offical releases.

At somepoint if I ever get time I'd like to work out how to port CM to other devices since I've got a pile of cheap android devices now that are lacking.... just never really get as much free time as I'd like :(