The kernel modules are located in build_modules directory. There are only 2 kernel modules: gspca_main.ko (video driver) and scsi_wait_scan.ko.

I cannot give it a try now, as I haven’t received the hardware yet. The other thing I would like to get before hacking CX-01 mini PC is a recovery firmware, and the eventual tools to recover the device when something bad happens. I’ve contacted PandaWill to try to get it. The bootloader code would also be nice, but not an absolute must. However, I believe it’s unlikely we’ll get the bootloader source code since Telechips does not appear to have released it for the older versions of its TCC processors.

@ max
I’m not exactly sure, but I think the AllWinner A10 kernel source has never been officially released. Instead, it has been made available through leaks, and lateron by manufacturers releasing the GPL part of the source. All tools and documentation have been either leaked or hacked/provided by the community.

Hi did anyone test the kernel yet after the firmware is released? My device seems to be clocked at 1008Mhz according to Overclock tools and Antutu as opposed to other peoples posts, where it says 808Mhz (http://www.androidtablets.net/forum/mcbub-com/41411-new-arrival-cx-01-c77-mini-android-pc-android-tv-box-android-4-0-cortex-a5-hdmi.html).
Anyway, I think this higher clock makes my device very unstable, so HDMI output is often lost 20 min after boot up, also my Antutu score isn’t really better.
My Rom Version is the same as all the others V1.0 20120710
So maybe I could use the kernel you compiled to make the device more stable or is there any other possibility to change the CPU frequency?

@groovey2k
You could try to build the kernel, root your device, and replace uImage (zImage?) in the NAND flash. Make sure you also download the firmware in case something goes wrong.

@Klaus
I’ve received 6 new devices/boards in the last 30 days, so I don’t know what to work on now, and end-up doing (almost) nothing :p. Just trying the kernel would probably not improve anything (I assume they use that one), but I (or somebody else) would have to look into it to see what can be improved. There seems to be a lot of interest about TCC8925 kernel, so maybe I should try it out.

@cnxsoft
Hi I tried to compile the kernel (716,5 Mhz version) unfortunately I don’t get a uimage after the process. There are a lot of warnings (functions and variables not used or wrong variable type) during the compilation. Did you have the same warnings during compilation?

@groovey2k
That means the build failed. If you used the -j12 option, the error message should be way up.

I’ve tried to locate the kernel in the Flash, and it appears to be in /dev/block/mtdblock0 (10MB partition), but it’s not in a file system, and this partition starts with “4e41 5244″ which seems related to fastboot, but I haven’t found a way to handle this. It might be possible to brick the device by changing this partition (not sure).

I finally managed to build the kernel with another ubuntu version (but it might be that the path was to deep using “telechips-linux” as name).
Anyway after building the zImage I tried to boot it using fastboot. “adb reboot bootloader” usually starts the fastboot mode where you could temporarily boot an zImage and try it and afterwards flash it permanent (you must have android sdk installed to do that).
Anyway the “adb reboot bootloader” command did restart the device in a special mode and it asked for driver installation. I installed the adb drivers again. But after that the device doesn’t react to the fastboot commands.
So I wasn’t able to flash the kernel. Maybe we need special fastboot drivers.
Also if you send “adb reboot recovery” it boots in the recovery mode but I don’t know if this helps with anything. All adb commands work in this mode.
I’m already on the newer firmware you mentioned. But for some reason quadrant still tells me that my device is clocked at 1008mhz amd it’s still unstable. I don’t know why, maybe it’s a hardware failure.