Jump to content

Build from source, kernel/aosp


Guest pajn

Recommended Posts

Ready.

How did you add .config file to the compiler?

I mean, how did you create the .config file what "make" uses?

cp arch/arm/configs/acer-q8k-a1-evt_defconfig

and then make manuconfig > save and exit

Link to comment
Share on other sites

cp arch/arm/configs/acer-q8k-a1-evt_defconfig

and then make manuconfig > save and exit

Ok, I did it different way, I don't known that your process is bad. I have just ask because I run into the same, when I used a wrong .compile file.

I run this from the kernel directory:

make ARCH=arm CROSS_COMPILE=~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- defconfig acer-q8k-a1-dvt_defconfig (OR evt)

Sure I copy the acer defconf file into the kernel directory instead add the full path.

This create for you the correct .config file in the kernel directory.

and run

make ARCH=arm CROSS_COMPILE=~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-

Hope that helps.

EDIT:

I forgot it sorry.

You need to edit makefile file in the kernel directory.

KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \

-fno-strict-aliasing -fno-common \

-Werror DELETE THIS!

-Werror-implicit-function-declaration

Edited by csics5
Link to comment
Share on other sites

Hmm, I can't understand what is going on:

In file included from /home/rasmus/Hämtningar/kernel/arch/arm/include/asm/page.h:26,

				 from include/linux/mm_types.h:14,

				 from include/linux/sched.h:61,

				 from arch/arm/kernel/asm-offsets.c:13:

/home/rasmus/Hämtningar/kernel/arch/arm/include/asm/glue.h:156:41: error: '#' is not followed by a macro parameter

make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1

make: *** [prepare0] Error 2

Link to comment
Share on other sites

Hmm, I can't understand what is going on:

In file included from /home/rasmus/Hämtningar/kernel/arch/arm/include/asm/page.h:26,

				 from include/linux/mm_types.h:14,

				 from include/linux/sched.h:61,

				 from arch/arm/kernel/asm-offsets.c:13:

/home/rasmus/Hämtningar/kernel/arch/arm/include/asm/glue.h:156:41: error: '#' is not followed by a macro parameter

make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1

make: *** [prepare0] Error 2

I'm sure you compiled wrong.

Link to comment
Share on other sites

@csics5 : is there a place where we could tchat together ?

I have somes questions.

Sure, but I'm not sure I could answer your questions. :)

Have you got Skype account?

Or advise any other solution. Online chat etc.

Edited by csics5
Link to comment
Share on other sites

i'm following all passages,nice work.. try to port a driver to enable multitouch on donut atm is very useful

As I can see the driver supports it but only reports one position because something higher cant handle it.

Link to comment
Share on other sites

As I can see the driver supports it but only reports one position because something higher cant handle it.

then? what are Consequentlyes? can we have multitouch in a futur? i really need it

what you mean about position?

Edited by erto90
Link to comment
Share on other sites

then? what are Consequentlyes? can we have multitouch in a futur? i really need it

what you mean about position?

Yes in the future (with android 2.0) we can have multitouch:

	/* coord[0]: finger1, coord[1]: finger2 */

	coord[0][0] = buf[0] + (buf[4]*256);

	coord[0][1] = buf[1] + (buf[5]*256);

	coord[1][0] = buf[2] + (buf[6]*256);

	coord[1][1] = buf[3] + (buf[7]*256);


	pressed = (coord[0][0]||coord[0][1]) ? 1 : 0;

	finger2_pressed = (coord[1][0]||coord[1][1]) ? 1: 0;


	if (!finger2_pressed) {

		/* No multitouch -- force width to zero */;

		width = 0;

		x = coord[0][0];

		y = coord[0][1];

	} else {

		/* (x,y) coords for multitouch are at midpt between fingers */

		x = (coord[0][0] + coord[1][0]) / 2;

		y = (coord[0][1] + coord[1][1]) / 2;


		/* Report the width according to the abs distance of x-axis */

		width = abs((coord[0][0] - coord[1][0]));

	}

The screen supports it but then it takes the midpoint and reports it to the os.

Link to comment
Share on other sites

Is it safe to use fastboot to boot the kernel?

If it won't boot is it possible to go to fastboot/recovery and flash a new rom?

PPl, i managed to compile with dvt dfconfig, added the cpu scalling of evt and compilled succefully, but the problem now is how to create a workinh boot.img with the new kernel..

Yesterday, I've been all night trying, and so far I only managed to unpack and repack the original boot.img (my nandroid backup) paul's superboot didn't worked, don't really know why (but i can try again)..

I'm getting pissed of with this, can someone please give some light... ?

EDIT: I guess that multitouch is not hard to implement, in a glance I think its easy, but first I need to create a f*ck*** working boot.img :S

Edited by disc0
Link to comment
Share on other sites

Guest maxisma
PPl, i managed to compile with dvt dfconfig, added the cpu scalling of evt and compilled succefully, but the problem now is how to create a workinh boot.img with the new kernel..

Yesterday, I've been all night trying, and so far I only managed to unpack and repack the original boot.img (my nandroid backup) paul's superboot didn't worked, don't really know why (but i can try again)..

I'm getting pissed of with this, can someone please give some light... ?

I did the same and had no success with it.

When I repacked with the stock Kernel it worked :) So it's a kernel issue.

Link to comment
Share on other sites

I did the same and had no success with it.

When I repacked with the stock Kernel it worked :) So it's a kernel issue.

Did you get errors compiling evt too?? Didn't look further because dvt worked straight foward..

I think acer don't want to give us proper config :\ ..

Link to comment
Share on other sites

Guest maxisma
Did you get errors compiling evt too?? Didn't look further because dvt worked straight foward..

I think acer don't want to give us proper config :\ ..

I tried dvt, as it's closer to what we have, pvt.

Had no errors on compiling dvt.

Link to comment
Share on other sites

I tried dvt, as it's closer to what we have, pvt.

Had no errors on compiling dvt.

dvt compilled well too, I only tried evt first because of cpu scalling..

Current .configs are dead ends, I'll dig a little...

Edited by disc0
Link to comment
Share on other sites

mmm acer acer,tried to send an email to know where are the problems?

what are pvt,evt and dvt????

Terminologies are not with me, but its the test/release stage order

evt -> dvt -> pvt !

@maxisma,

please tell if you have any success, I'm looking at touchscreen driver and already made some improvements to try multitouch...

Think I can solve it, but i need to dump some vars first...

Link to comment
Share on other sites

Terminologies are not with me, but its the test/release stage order

evt -> dvt -> pvt !

@maxisma,

please tell if you have any success, I'm looking at touchscreen driver and already made some improvements to try multitouch...

Think I can solve it, but i need to dump some vars first...

nice! also you a developer? I love this forum,you all are the best!!!

then pvt is the last release ( the most complete?)

Edited by erto90
Link to comment
Share on other sites

nice! also you a developer? I love this forum,you all are the best!!!

then pvt is the last release ( the most complete?)

pvt stands for production validation test, the final stage, and acer didn't include it on the kernel, maybe thats because we cant have a working kernel..

I don't even dare to flash the boot.img without testing it first, this is my only android phone and I'm trying to avoid to brick it at all cost! So can't do much before someone figures out what is wrong with the kernel/boot.img..

Edited by disc0
Link to comment
Share on other sites

pvt stands for production validation test, the final stage, and acer didn't include it on the kernel, maybe thats because we cant have a working kernel..

I don't even dare to flash the boot.img without testing it first, this is my only android phone and I'm trying to avoid to brick it at all cost! So can't do much before someone figures out what is wrong with the kernel/boot.img..

ok understood! i hope you will find a method to get rom working!

Edited by erto90
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.