Multitouch possible in theory?

[Guest totiadrenalin]

Didn't BigBearMDC say he got a dualtouch touchscreen driver, but the problem was the touch controller firmware that was not reporting the second point?

And you can find that DT driver in the fliblle's pulse source code on his github.

[Guest rulerofkaos]

And you can find that DT driver in the fliblle's pulse source code on his github.

I can't find the Pulse repository is it not public? I think I'll compare his driver with the one for the c8150, let's see :-)

edit: I found Bobo's driver in his github. It seems to do the same than TJ's mod. But I don't know enough about the touchcontroller firmware.

edit2: A strange thing is that Bobo is reporting the same pressure for finger1 and finger2 to the system.

Edited April 3, 2011 by rulerofkaos

[Guest totiadrenalin]

I can't find the Pulse repository is it not public? I think I'll compare his driver with the one for the c8150, let's see :-)

edit: I found Bobo's driver in his github. It seems to do the same than TJ's mod. But I don't know enough about the touchcontroller firmware.

edit2: A strange thing is that Bobo is reporting the same pressure for finger1 and finger2 to the system.

Take look at board-msm7x25.c file

Something strange here.

Compared with the pulse's source the same files are really different.

[Guest AntonioPT]

Take look at board-msm7x25.c file

Something strange here.

Compared with the pulse's source the same files are really different.

Don't forget the Pulse doesn't have a 7x25 board, it's a 7200A.

[Guest totiadrenalin]

Don't forget the Pulse doesn't have a 7x25 board, it's a 7200A.

So what is the file in the source for our board?

Let me take a look into the config.gz?

I hope that we could find the problem, because personally I think that our problem wasn't the firmware. I flash my touchcontroler with different firmware, but i get even worse response of the touchcontroller than with the pulse's original firmware.

That's why we fail.

[Guest totiadrenalin]

So what is the file in the source for our board?

Let me take a look into the config.gz?

I hope that we could find the problem, because personally I think that our problem wasn't the firmware. I flash my touchcontroler with different firmware, but i get even worse response of the touchcontroller than with the pulse's original firmware.

That's why we fail.

CONFIG_ARCH_MSM7X01A=y

So now should find the bourd or device msm7x01A

I hope that this could help you.

EDIT:

I found it.

In tjstyle's github source it's called devices-msm7x01a.c, and in your (AntonioTP) github source it's called just devices.c

And they are totally the same.

Edited April 3, 2011 by totiadrenalin

[Guest rulerofkaos]

I found it.

In tjstyle's github source it's called devices-msm7x01a.c, and in your (AntonioTP) github source it's called just devices.c

Cool! So now we need to know what TJStyle changed in the board driver.

[Guest BigBearMDC]

Hey guys,

sorry I've really been busy :D The driver from my repo is messed up - just a brief testversion. I wanted to check if the second touchpoint is even recognized by Android. In short, I tried everything - even patching the I2C driver but I couldn't get it working B)

Best regards,

BoBo

[Guest totiadrenalin]

I found this in TJStyle's github board-msm7x25.c driver.

 }


	return pname;

}


int board_surport_fingers(bool * is_surport_fingers)

{

	int result = 0;


	if (is_surport_fingers == NULL)

	{

		 return -ENOMEM;

	}

//----------------------------------------------

//Return true for all devices

//----------------------------------------------

		 *is_surport_fingers = true;


	return result;

}

int board_use_tssc_touch(bool * use_touch_key)

{

	int result = 0;


	if (use_touch_key == NULL)

	{

		 return -ENOMEM;

	}

Could this be the patch that you perform TJSyle?

Or m'i wrong?

Edited April 3, 2011 by totiadrenalin

[Guest AntonioPT]

I found this in TJStyle's github board-msm7x25.c driver.

 }


	return pname;

}


int board_surport_fingers(bool * is_surport_fingers)

{

	int result = 0;


	if (is_surport_fingers == NULL)

	{

		 return -ENOMEM;

	}

//----------------------------------------------

//Return true for all devices

//----------------------------------------------

		 *is_surport_fingers = true;


	return result;

}

int board_use_tssc_touch(bool * use_touch_key)

{

	int result = 0;


	if (use_touch_key == NULL)

	{

		 return -ENOMEM;

	}

Could this be the patch that you perform TJSyle?

Or m'i wrong?

You can see exactly what he patched right here: https://github.com/tjstyle/Huawei-Kernel/co...e7c95116f7f6eda

[Guest rulerofkaos]

You can see exactly what he patched right here: https://github.com/tjstyle/Huawei-Kernel/co...e7c95116f7f6eda

OK, but we must definitly write a modded synaptics_ts_work_func function, because our file doesn't contain multitouch support.

[Guest TJ Style]

sorry for late answer, in the board msm7225. I just patch for the variable will always report true for fingers input that needed by synaptic driver.

i make the comment in source code of multitouch patch in my github, so will be easy to see the different. just see in my commit.

[Guest TJ Style]

I found this in TJStyle's github board-msm7x25.c driver.

 }


	return pname;

}


int board_surport_fingers(bool * is_surport_fingers)

{

	int result = 0;


	if (is_surport_fingers == NULL)

	{

		 return -ENOMEM;

	}

//----------------------------------------------

//Return true for all devices

//----------------------------------------------

		 *is_surport_fingers = true;


	return result;

}

int board_use_tssc_touch(bool * use_touch_key)

{

	int result = 0;


	if (use_touch_key == NULL)

	{

		 return -ENOMEM;

	}

Could this be the patch that you perform TJSyle?

Or m'i wrong?

yup, I modify to always true for all board.

[Guest rulerofkaos]

So what files need to be modded?

- / arch / arm / mach-msm / devices.c

- / drivers / input / touchscreen / synaptics_i2c_rmi_tm1319.c (here I think only the synaptics_ts_work_func)

The first one should be easy, but I don't understand the second one.

Edited April 4, 2011 by rulerofkaos

[Guest BigBearMDC]

So what files need to be modded?jo

- / arch / arm / mach-msm / devices.c

- / drivers / input / touchscreen / synaptics_i2c_rmi_tm1319.c (here I think only the synaptics_ts_work_func)

The first one should be easy, but I don't understand the second one.

The second one isn't that difficult, just merge in the changes of the ts_work_func of the original synaptics_i2c_rmi driver.

Best regards,

BB

[Guest rulerofkaos]

The second one isn't that difficult, just merge in the changes of the ts_work_func of the original synaptics_i2c_rmi driver.

Best regards,

BB

The problem is the buf array. There is the position data stored. But our is different to the c8150 one, so I don't know where is the second finger in this array.

Edited April 4, 2011 by rulerofkaos

[Guest BigBearMDC]

You might also add some printk()'s into the ts_work_func to display the coords (that's what I did). Makes debugging alot easier -> cat kmsg.

[Guest BigBearMDC]

The problem is the buf array. There is the position data stored. But our is different to the c8150 one, so I don't know where is the second finger in this array.

Yeah that's the problem. That's why I output every field of the array using printk.

Best regards,

BB

[Guest belorussian]

Any news?

[Guest rulerofkaos]

Any news?

I don't think so, unless we get a documentation of the touchscreen firmware and/or driver.

[Guest Rickardy]

I don't think so, unless we get a documentation of the touchscreen firmware and/or driver.

You are in this one year.

So many time.

[Guest Rickardy]

BB, i discovered a video that could help you, just go to youtibe and search for ''Droid Incredible Multitouch Video''.

In top left corner there is x1= y1=

x2= y2=

I can't send the video link because i have discovered the video on Huawei U8230.

I hope that can help you.

Sory for my bad english, i'm portuguese.

I don't understend nothing of kernels, but i know there needs to be two points to have multitouch.

I've ben fallowing since February 2010.

I really hope that can help you.

I'm a noob.

[Guest jeddy1]

BB, i discovered a video that could help you, just go to youtibe and search for ''Droid Incredible Multitouch Video''.

In top left corner there is x1= y1=

x2= y2=

I can't send the video link because i have discovered the video on Huawei U8230.

I hope that can help you.

Sory for my bad english, i'm portuguese.

I don't understend nothing of kernels, but i know there needs to be two points to have multitouch.

I've ben fallowing since February 2010.

I really hope that can help you.

I'm a noob.

i am sure he already knew that :).but thanks for any information.

Edited April 19, 2011 by jeddy1

[Guest Rickardy]

I really hope they can do it anyway :)

[Guest Rickardy]

Who can contact BB send it this:

h**p://www.rbgrn.net/content/367-source-code-to-multitouch-visible-test

I don't understand nothing of that but i think it can help.