Build from source, kernel/aosp

[Guest blc]

With the new kernel?? Jave you tweeked the configuration??

Yes with DVT defconfig, using PVT as board type and few other that were missing (CPU freqs for example). But this is a bit hard because I can't get any output from adb.

[Guest Seth Cold]

is the kernel the same is just spotted since yesterday here?: ftp://ftp.acer-euro.com/smartphone/s100/source%20code/

[Guest disc0]

Yes with DVT defconfig, using PVT as board type and few other that were missing (CPU freqs for example). But this is a bit hard because I can't get any output from adb.

Ye, did the same.. I compiled the bootlogo to ensure it was the new kernel bootinh and appear the pinguin in top corner, but then just reboots and cant read notginh..

You cannot get output from adb maybe because the ramdisk was not yet accessed and adbd is in ramdisik /sbin/adbd

Just a hint:

cat /dev/zero > /dev/mtd/mtd2

because when using "fastboot boot ...", when it fails and reboots, it goes directly for internal memory, and this way it will go to bootloader, saving some time, and some confusion...

Edited February 2, 2010 by disc0

[Guest disc0]

is the kernel the same is just spotted since yesterday here?: ftp://ftp.acer-euro.com/smartphone/s100/source%20code/

downloading to see...

Unfortunately the same

md5sum kernel.zip App.\ Guide_Acer_1.0_A_A.zip

8ca5ff0c08a5c68a3f9b0bc2b148bde2  kernel.zip

8ca5ff0c08a5c68a3f9b0bc2b148bde2  App. Guide_Acer_1.0_A_A.zip

Edited February 2, 2010 by disc0

[Guest disc0]

Don't know what happened, but now I cannot boot from "fastboot boot", even if boot.img is fine and says booting linux. It reboots and returns to fastboot because I zero'd the mt2 part. If I have flashed a working boot.img to the mtd2 it ignores the fastboot boot and just boots from the mtd2 :s

Now I'm confused if fastboot boot ever worked correctly, or if is some sort of protection from the acer bootloader :s ..

EDIT:

Now it works, kind of :| .. fastboot boot works with an image that I created and not with liquid.superboot.img.. Just weird :S

EDIT:

can't find a way to stop the f**kin kernel to reboot, and cannot grab nothing of those messages that i truly need to read..! I really don't want to read source code to find where it makes the reboot and "cripple" it because it would be an impossible task :\ ..

Edited February 3, 2010 by disc0

[Guest vache]

ftp://ftp.acer-euro.com/smartphone/s100/

Seems like kernel source are different here.

Edit : OOps didn't see disc0's post.

Edited February 3, 2010 by vache

[Guest solarw]

IHHHHHHAAAAAA!

Working compiled kernel!

but no battery status(

so phone asks charging

Edited February 3, 2010 by solarw

[Guest liquid_it]

Working compiled kernel!

Nice nice work man. Why don't you share some info? ;)

[Guest amdnikos]

IHHHHHHAAAAAA!

Working compiled kernel!

but no battery status(

so phone asks charging

my respect! give some info on how you did that.

[Guest vache]

IHHHHHHAAAAAA!

Working compiled kernel!

but no battery status(

so phone asks charging

Wow great man !

[Guest maxisma]

yea I agree.. please publish your .config ;)

[Guest wc326]

Wow great man !

SO does this mean 1ghz and multitouch in the future?

[Guest vache]

acpuclock-8x50.c

struct clkctl_acpu_speed acpu_freq_tbl[] = {

	{ 0, 19200, ACPU_PLL_TCXO, 0, 0, 0, 0, 14000, 0, 0, 1000},

	{ 0, 48000, ACPU_PLL_1, 1, 0xF, 0, 0, 14000, 0, 0, 1000},

	{ 0, 64000, ACPU_PLL_1, 1, 0xB, 0, 0, 14000, 0, 0, 1000},

	{ 0, 96000, ACPU_PLL_1, 1, 7, 0, 0, 14000, 0, 0, 1000},

	{ 0, 128000, ACPU_PLL_1, 1, 5, 0, 0, 14000, 2, 0, 1000},

	{ 0, 192000, ACPU_PLL_1, 1, 3, 0, 0, 14000, 0, 0, 1000},

	/* 235.93 on CDMA only. */

	{ 1, 245000, ACPU_PLL_0, 4, 0, 0, 0, 29000, 0, 0, 1000},

	{ 0, 256000, ACPU_PLL_1, 1, 2, 0, 0, 29000, 0, 0, 1000},

	{ 1, 384000, ACPU_PLL_3, 0, 0, 0, 0, 58000, 1, 0xA, 1000},

	{ 0, 422400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xB, 1000},

	{ 0, 460800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xC, 1000},

	{ 0, 499200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xD, 1025},

	{ 0, 537600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xE, 1050},

	{ 1, 576000, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xF, 1050},

	{ 0, 614400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x10, 1075},

	{ 0, 652800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x11, 1100},

	{ 0, 691200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x12, 1125},

	{ 0, 729600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x13, 1150},

	{ 1, 768000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x14, 1150},

	{ 0, 806400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x15, 1175},

	{ 0, 844800, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x16, 1200},

	{ 0, 883200, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x17, 1225},

	{ 0, 921600, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x18, 1250},

	{ 0, 960000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x19, 1250},

	{ 1, 998400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x1A, 1250},

	{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0},

};

Seems like the kernel is already compiling with 1Ghz support.

[Guest CedricGatay]

I've seen this, but it seems that the Cpu freq limit is elsewhere in the kernel, via a constant defined only, easy to bypass (I don't remember the file name)

[Guest Roter_Flieger]

I renamed it acermkbootimg.

disc0, mind to release your modified source of mkbootimg?

[Guest vache]

It's on page 4 or 5. Search a bit...

[Guest Roter_Flieger]

It's on page 4 or 5. Search a bit...

That is a binary, compiled for Linux. I was asking for the source code...

By the way: did you notice that the Acer stock boot.img's have an extra 20 bytes in front of the ANDROID! magic in the header?

0x 61 63 65 72 62 6f 74 ce 1c aa 27 a6 57 6b de 40 20 24 00

First eight bytes read "acerboot"...

[Guest disc0]

IHHHHHHAAAAAA!

Working compiled kernel!

but no battery status(

so phone asks charging

Can you share your .config please?

That is a binary, compiled for Linux. I was asking for the source code...

By the way: did you notice that the Acer stock boot.img's have an extra 20 bytes in front of the ANDROID! magic in the header?

0x 61 63 65 72 62 6f 74 ce 1c aa 27 a6 57 6b de 40 20 24 00

First eight bytes read "acerboot"...

Will be soon here, let me upload it

As for that header, is only used by acer tool, already stated that a few posts earlier..

[Guest solarw]

How to build kernel from source.

1. kernel image in boot.img is started with 2048 zeroes, then normal zImage goes

2. kernel image size must be equal 2193408 bytes!

3. boot.img must be started with magic 12 bytes.

4. choose dvt_defconfig as .config. set CONFIG_MSM_N_WAY_SMSM=n

5. compile kernel with gcc 4.2.1 from android repository.

6. combine new boot.img with new kernel with 2048 zeroes in front and size equal 2193408 and ram fs from liquid superboot.

7. flash new boot.img with fastboot, run new boot.img with fastboot

troubles. in this case battery status not working. android became unstable. but working.

for developers:

kernel with default dvt config goes reboot because smem_alloc in pm_init in arch/arm/mach-msm/pm2.c returns Null pointer, so kernel goes fault.

function smem_find (same as smem_alloc) - is intresting point of many bugs in this kernel, it defined in smd.c

Edited February 3, 2010 by solarw

[Guest disc0]

How to build kernel from source.

1. kernel image in boot.img is started with 2048 zeroes, then normal zImage goes

2. kernel image size must be equal 2193408 bytes!

3. boot.img must be started with magic 12 bytes.

4. choose dvt_defconfig as .config. set CONFIG_MSM_N_WAY_SMSM=n

5. compile kernel with gcc 4.2.1 from android repository.

6. combine new boot.img with new kernel with 2048 zeroes in front and size equal 2193408 and ram fs from liquid superboot.

7. flash new boot.img with fastboot, run new boot.img with fastboot

troubles. in this case battery status not working. android became unstable. but working.

for developers:

kernel with default dvt config goes reboot because smem_alloc in pm_init in arch/arm/mach-msm/pm2.c returns Null pointer, so kernel goes fault.

function smem_find (same as smem_alloc) - is intresting point of many bugs in this kernel, it defined in smd.c

I'm compilling now.. BTW, how did you stop the kernel from rebooting and readed the log??

F**ing finnaly, it f**kin booted ;) .. Thanks solarw, i was tired of knock my heade yesterday.. Before got sleep I had searched the internet and was making my shopping list to buy the needed parts to make the same usb 2 serial that was made for the G1 and test it on liquid (I was 99% shore it would not work) .. Glad I don't need it know :D

Edited February 3, 2010 by disc0

[Guest CedricGatay]

Thanks a lot solarw

[Guest solarw]

I'm compilling now.. BTW, how did you stop the kernel from rebooting and readed the log??

F**ing finnaly, it f**king booted ;) .. Thanks solarw

compile kernel with CONFIG_BOOT_PRINTK_DELAY=y

and pass kernel option "boot_delay=500"

this will slowdown kernel boot log output.

[Guest disc0]

compile kernel with CONFIG_BOOT_PRINTK_DELAY=y

and pass kernel option "boot_delay=500"

this will slowdown kernel boot log output.

CONFIG_BOOT_PRINTK_DELAY=y i did that,

but didn't found anywhere where to delay (:

Whel, lets try to fix the freakin battery

But first I'll test my beta multitouch rom ;D

Edited February 3, 2010 by disc0

[Guest erto90]

CONFIG_BOOT_PRINTK_DELAY=y i did that,

but didn't found anywhere where to delay (:

Whel, lets try to fix the freakin battery

then is done? rom compiled with kernel working? now is only question to fix bugs or something missed?

[Guest pajn]

@solarw you are awesome!

Will try that later, hope I can get some time today.