[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[terrystorm23]

Hi Anguel

I too have the same problem. I have a LCD4 and a LCD7 and both do the same 
thing.
I suspect since the 4D Systems displays use the same drivers the 4DCAPE-43T 
does the same thing, so it doesn't seem to be hardware related at all since 
they use different brand touch screens.

Have you had any reply out of CircuitCo?
Does CircuitCo actually write the drivers or is it someone else?
Can anyone help and point us to someone who wrote the drivers that we can 
discuss this with?

I know a number of other people who have these displays and experience the 
exact same thing, so it is not just isolated to us 2 people.

Please can someone point us in the right direction?

Thanks
Terry

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Anguel]

Hi Terry,

Nice to know that I am not the only one who cares about the touchscreen. 
Neither CircuitCo nor 4D Systems seem to really care about the problem. 
They sell the displays but don't reply to my e-mails anymore. I also 
reported the problem on Beaglebone IRC but did not receive any help there. 
I even tried tweaking a bit in the kernel but without success. I just don't 
have the experience to dig deeper in the ADC drivers and chase for the bug.

The latest patches were actually submitted by Zubair Lutfullah, he seems to 
adapt them (from the TI driver developers who write them for the older 
kernel afaik). Zubair told me that he already knew about the jitter problem 
and gave me the following reply: "The touchscreen driver that was patched 
in the linux kernel was different compared to the old patches in the 
beaglebone tree. And we try to keep the beaglebone tree close to the 
mainline. The old 3.8 patches were ok. The mainlined ones introduced this 
problem.. A fix would require a comparison of the two drivers to figure out 
what went wrong and upload a patch to the mainline.. It would require 
time.."

Unfortunately, Zubair is very busy right now. He also mailed his reply to 
Koen Kooi, one of the main Angstrom developers (also works at CircuitCo 
according to his Google+ profile). I am afraid that Koen is also very busy 
and won't have the time to look into the issue. So we can just hope that 
someone with more experience can fix the issue in the near future.

Regards,
Anguel


On Monday, September 23, 2013 7:08:36 AM UTC+2, terrys...@gmail.com wrote:
>
> Hi Anguel
>
> I too have the same problem. I have a LCD4 and a LCD7 and both do the same 
> thing.
> I suspect since the 4D Systems displays use the same drivers the 
> 4DCAPE-43T does the same thing, so it doesn't seem to be hardware related 
> at all since they use different brand touch screens.
>
> Have you had any reply out of CircuitCo?
> Does CircuitCo actually write the drivers or is it someone else?
> Can anyone help and point us to someone who wrote the drivers that we can 
> discuss this with?
>
> I know a number of other people who have these displays and experience the 
> exact same thing, so it is not just isolated to us 2 people.
>
> Please can someone point us in the right direction?
>
> Thanks
> Terry
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[terrystorm23]

Hi Anguel

Probably a little harsh to say CircuitCo and 4D Systems don't care about 
the problem. If you look at what 4D Systems claims, they state the software 
is not written or supported by them and they are essentially supplying 
hardware only, so they are actually unable to do anything about it even if 
they wanted to. I am still confused about what role CircuitCo plays, if 
they are just a hardware supplier or do software too. Beaglebone.org and 
beagleboardtoys.org along with TI and all the other players, I really have 
no idea who does what.

I do hope however we can get to the bottom of it.

Hi Gerald

Being a beginner with Linux, I don't even know what the X11 is. I have 
tried the latest Angstrom release for the BBB and the touch issue is still 
present, or are you meaning something else?
It does seem a little disappointing how the software does not work 
correctly for the hardware. I have a friend who was building an industrial 
product with the LCD4 and BBB, yet due to the touch issues the product was 
useless, so he ended up using a different solution entirely. I am sure 
there are many others who fall into this camp too.

I do hope we can find a solution

Regards
Terry

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Terry Storm]

Has there been any progress made by anyone about this touch screen 
jitter/jumping issue with the LCD Capes?

I now have a 4DCAPE-43T, 4DCAPE-70T, LCD4 and LCD7 and they all exhibit the 
exact same behaviour, even using the latest version of Angstrom listed on 
this site.

When loaded with the TI Android 4.2.2 Image, touch works perfectly. Can 
launch draw programs and there are no issues at all, everything runs 
smoothly. All the menus can be accessed without issue, so there really is 
an issue with the released versions of Angstrom and the drivers they use.

Are there any capable people out there working on this?

Thanks

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Anguel]

I have given up with all LCD capes, there are driver bugs in the 3.8 kernel as 
stated before (see my previous postings). Afaik Android uses the old 3.2 kernel 
an therefore works ok.
Also, I have the impression that Angstrom development for the BBB is completely 
abandoned now.
Just hope that the Buildroot people will soon have full support for the BBB...

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Terry Storm]

Hmm,

There are 2 Android builds that I know of, one from TI which is the 3.2 
Kernel which does work fine 
http://downloads.ti.com/sitara_android/esd/TI_Android_DevKit/TI_Android_JB_4_2_2_DevKit_4_1_1/index_FDS.html,
 
and then this one which uses 3.8 which also works fine 
http://icculus.org/~hendersa/android/

Both work correctly for touch...

I didn't realise Angstrom was abandoned, that is not good.
So what is the new most supported distribution for the BBB and LCD capes?

The touch problem is incredibly frustrating.

Thanks for the info

On Monday, 16 December 2013 19:56:40 UTC+13, Anguel wrote:
>
> I have given up with all LCD capes, there are driver bugs in the 3.8 
> kernel as stated before (see my previous postings). Afaik Android uses the 
> old 3.2 kernel an therefore works ok.
> Also, I have the impression that Angstrom development for the BBB is 
> completely abandoned now.
> Just hope that the Buildroot people will soon have full support for the 
> BBB...

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Ian Kidd]

Hi, Terry.  I see you got the touchscreen working in Android.  I'm using 
the Anderson image, and while I can get swipe scrolling to work, it doesn't 
seem to be calibrated for the point of touch.  Any particular utility that 
you use to calibrate the touch on Android.

Also, what was the screen rotation utility you mentioned?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Terry Storm]

Hi Ian

Did you try the TI image instead of the Anderson image?
The TI one seems to be more stable and the buttons are actually mapped to 
suit Android, which isn't the case on the Anderson image. Anderson Image is 
Kernel 3.8 however, but also does support the Hardware Graphics like the TI 
one, so the TI one is quite a bit faster too.
I haven't had to calibrate, both just worked for me.
Screen rotation utility was just from the App Store, just some free 
rotation app. Cant remember what it was called off the top of my head.

Try and TI image and report back.
Terry

On Wednesday, 18 December 2013 12:38:01 UTC+13, Ian Kidd wrote:
>
> Hi, Terry.  I see you got the touchscreen working in Android.  I'm using 
> the Anderson image, and while I can get swipe scrolling to work, it doesn't 
> seem to be calibrated for the point of touch.  Any particular utility that 
> you use to calibrate the touch on Android.
>
> Also, what was the screen rotation utility you mentioned?
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Terry Storm]

Should read

"but does not support the Hardware Graphics like the TI one"

above.

On Wednesday, 18 December 2013 13:27:18 UTC+13, Terry Storm wrote:
>
> Hi Ian
>
> Did you try the TI image instead of the Anderson image?
> The TI one seems to be more stable and the buttons are actually mapped to 
> suit Android, which isn't the case on the Anderson image. Anderson Image is 
> Kernel 3.8 however, but also does support the Hardware Graphics like the TI 
> one, so the TI one is quite a bit faster too.
> I haven't had to calibrate, both just worked for me.
> Screen rotation utility was just from the App Store, just some free 
> rotation app. Cant remember what it was called off the top of my head.
>
> Try and TI image and report back.
> Terry
>
> On Wednesday, 18 December 2013 12:38:01 UTC+13, Ian Kidd wrote:
>>
>> Hi, Terry.  I see you got the touchscreen working in Android.  I'm using 
>> the Anderson image, and while I can get swipe scrolling to work, it doesn't 
>> seem to be calibrated for the point of touch.  Any particular utility that 
>> you use to calibrate the touch on Android.
>>
>> Also, what was the screen rotation utility you mentioned?
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Ian Kidd]

I figured.  I'll give that a shot.  Be nice to have an App Store on that TI 
image.

On Tuesday, December 17, 2013 9:19:22 PM UTC-7, Terry Storm wrote:
>
> Should read
>
> "but does not support the Hardware Graphics like the TI one"
>
> above.
>
> On Wednesday, 18 December 2013 13:27:18 UTC+13, Terry Storm wrote:
>>
>> Hi Ian
>>
>> Did you try the TI image instead of the Anderson image?
>> The TI one seems to be more stable and the buttons are actually mapped to 
>> suit Android, which isn't the case on the Anderson image. Anderson Image is 
>> Kernel 3.8 however, but also does support the Hardware Graphics like the TI 
>> one, so the TI one is quite a bit faster too.
>> I haven't had to calibrate, both just worked for me.
>> Screen rotation utility was just from the App Store, just some free 
>> rotation app. Cant remember what it was called off the top of my head.
>>
>> Try and TI image and report back.
>> Terry
>>
>> On Wednesday, 18 December 2013 12:38:01 UTC+13, Ian Kidd wrote:
>>>
>>> Hi, Terry.  I see you got the touchscreen working in Android.  I'm using 
>>> the Anderson image, and while I can get swipe scrolling to work, it doesn't 
>>> seem to be calibrated for the point of touch.  Any particular utility that 
>>> you use to calibrate the touch on Android.
>>>
>>> Also, what was the screen rotation utility you mentioned?
>>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[eric . zaluzec]

This forum thread saved my ti touch screen device. Thanks all! My 
touchscreen was having the exact symptoms mentioned in the first few posts. 
A drop in 'touch' pressure would cause the x-coordinates to drastically 
deviate from where I was touching. This made functionality of something, 
like a UI scroll-bar, useless.

I was using a v3.12 linux kernel, but was still able to modify the 
ti_am335x_tsc.c from the v3.8 patch that was listed here.

For future users, if you need a patch for the 3.12 kernel, you can find it 
here.
https://github.com/EricZaluzec/ti_am335x_tsc/blob/master/remove-pressure-jitter.patch

Cheers.
-Ez

On Tuesday, September 3, 2013 at 6:47:44 AM UTC-5, Anguel wrote:
>
> Hi!
>
> I have a 4DCAPE-43T LCD and tested it with Beaglebone Black and the latest 
> Angstrom image (2013.08.21). Unfortunately, I am experiencing input jitter 
> / jumping. I use TSlib's ts_calibrate for calibration and ts_test for 
> testing. In Gnome's calibration tools the same problem appeared: Instead of 
> clicking, I often have some dragging or even random jumping of the pointer. 
> The problem appears especially if the pressure applied to the touchscreen 
> is lower.
>
> I wrote 4D SYSTEMS support regarding the touchscreen jitter and got the 
> following reply:
> "The 4D Cape 43T LCD has been based on the LCD4 from Circuitco and uses 
> the same drivers written for the LCD4 on the Angstrom. Upon testing and 
> verification, the problem of jitter is evident as well on the LCD4 display 
> of Circuitco using the Angstrom 2013.06.20 and 2013.08.21 images so in 
> effect this has nothing to do with the hardware but it’s a software 
> problem."
>
> Actually, I found a video on Youtube with LCD7 where a similar jump / 
> jitter problem can be seen:
> http://www.youtube.com/watch?v=vEfnwL-Jxgw   @ min 2:00
>
> Any idea how the problem can be solved?
>
> Thanks in advance,
> Anguel
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[michcior]

Hi, 

I step in as everybody looking to find solutions for TS issues. Actually, 
I'm still working on solving it. However, I have some tips and 
"discoveries" I'd like to share, meby someone will find it useful.

1) I have just external TS, no cape at all, the TS is 10 inch. 

2) I found "after many hours :(" that ti_am335x_tsc driver can not be build 
in, and must be loaded as a module after the cape for TSC is loaded. That's 
because I use "overlay-ed" cape for TSC. Even though it is set to be loaded 
in uEnv.txt!

3) Big touch screen has bigger capacity, it results in permanent 
"auto-touch"  event generation, driving me nuts since LCD7 TS works nicely. 
I have discovered, that adjusting delays in driver is the solution!!!  
There are "open-delay", "sample-delay", "charging-delay" defined in 
ti_am335x_tscad.h file. They have fundamental influence on this effect. 
Someone has mentioned that "hardware issue" was observed as a few 
"auto-touch" glitches. That is exactly this, just in case of a smaller TS, 
it is not so evident.  

So, concluding, now I'm focusing on adjusting delays. I'll let you know my 
setting for this 10inch TS.

Regards, 
Piotr 


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Piotr Murawski]

There is a part in the driver (ti_am335x_tsc.c):

config = STEPCONFIG_MODE_HWSYNC |
STEPCONFIG_AVG_16 | ts_dev->bit_yp |
ts_dev->bit_xn | STEPCONFIG_INM_ADCREFM |
STEPCONFIG_INP(ts_dev->inp_xp);
titsc_writel(ts_dev, REG_STEPCONFIG(end_step), config);
titsc_writel(ts_dev, REG_STEPDELAY(end_step),
STEPCONFIG_OPENDLY);

end_step++;
*config |= STEPCONFIG_INP(ts_dev->inp_yn);*

There is possible bug, with using "OR". It does not show up when XP -> AN0 
and YN -> AN3 because 0 is ORed to 3 (fortunately). With other X/Y plate 
connections, z2 might be totally wrong. 

Regards, 
Piotr.



  


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[roop]

I have been playing with touchscreens for the last couple weeks. I noticed 
the following:

For both 4.3" and 7" resistive touchscreens I have, the jitter is 
significantly better in the default Angstrom versus Debian. Angstrom 
jitters with around 5pixels of the touched point, Debian is >20pixels

Looking at Debian, it seems to have a much newer version of the touchscreen 
driver than Angstrom does. I believe this is the revision angstrom uses:

Last time steps_to_configure was available:
https://github.com/torvalds/linux/commit/af9c2fe3740fe8dac05eede8805d9aaa45972cb6

Change from steps_to_configure to coordinate_readouts:
https://github.com/torvalds/linux/commit/0396310b0eba71595c1151ce7c8fde7a9f33f719


Angstrom's DTC files for touchscreen refer to 'steps-to-configure' where 
Debian's has the newer 'coordinate-readouts'.

I would be happy if the quality of touch input that I get from Angstrom 
existed in Debian, so I'll try to compile the old driver, then recompile my 
DTC files and use steps_to_configure and report back.


On Friday, 14 March 2014 15:19:28 UTC-7, Piotr Murawski wrote:
>
> There is a part in the driver (ti_am335x_tsc.c):
>
> config = STEPCONFIG_MODE_HWSYNC |
> STEPCONFIG_AVG_16 | ts_dev->bit_yp |
> ts_dev->bit_xn | STEPCONFIG_INM_ADCREFM |
> STEPCONFIG_INP(ts_dev->inp_xp);
> titsc_writel(ts_dev, REG_STEPCONFIG(end_step), config);
> titsc_writel(ts_dev, REG_STEPDELAY(end_step),
> STEPCONFIG_OPENDLY);
>
> end_step++;
> *&*
> ...

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[freddy12120]

El martes, 3 de septiembre de 2013 06:47:44 UTC-5, Anguel escribió:
>
> Hi!
>
> I have a 4DCAPE-43T LCD and tested it with Beaglebone Black and the latest 
> Angstrom image (2013.08.21). Unfortunately, I am experiencing input jitter 
> / jumping. I use TSlib's ts_calibrate for calibration and ts_test for 
> testing. In Gnome's calibration tools the same problem appeared: Instead of 
> clicking, I often have some dragging or even random jumping of the pointer. 
> The problem appears especially if the pressure applied to the touchscreen 
> is lower.
>
> I wrote 4D SYSTEMS support regarding the touchscreen jitter and got the 
> following reply:
> "The 4D Cape 43T LCD has been based on the LCD4 from Circuitco and uses 
> the same drivers written for the LCD4 on the Angstrom. Upon testing and 
> verification, the problem of jitter is evident as well on the LCD4 display 
> of Circuitco using the Angstrom 2013.06.20 and 2013.08.21 images so in 
> effect this has nothing to do with the hardware but it’s a software 
> problem."
>
> Actually, I found a video on Youtube with LCD7 where a similar jump / 
> jitter problem can be seen:
> http://www.youtube.com/watch?v=vEfnwL-Jxgw   @ min 2:00
>
> Any idea how the problem can be solved?
>
> Thanks in advance,
> Anguel
>

El martes, 3 de septiembre de 2013 06:47:44 UTC-5, Anguel escribió:
>
> Hi!
>
> I have a 4DCAPE-43T LCD and tested it with Beaglebone Black and the latest 
> Angstrom image (2013.08.21). Unfortunately, I am experiencing input jitter 
> / jumping. I use TSlib's ts_calibrate for calibration and ts_test for 
> testing. In Gnome's calibration tools the same problem appeared: Instead of 
> clicking, I often have some dragging or even random jumping of the pointer. 
> The problem appears especially if the pressure applied to the touchscreen 
> is lower.
>
> I wrote 4D SYSTEMS support regarding the touchscreen jitter and got the 
> following reply:
> "The 4D Cape 43T LCD has been based on the LCD4 from Circuitco and uses 
> the same drivers written for the LCD4 on the Angstrom. Upon testing and 
> verification, the problem of jitter is evident as well on the LCD4 display 
> of Circuitco using the Angstrom 2013.06.20 and 2013.08.21 images so in 
> effect this has nothing to do with the hardware but it’s a software 
> problem."
>
> Actually, I found a video on Youtube with LCD7 where a similar jump / 
> jitter problem can be seen:
> http://www.youtube.com/watch?v=vEfnwL-Jxgw   @ min 2:00
>
> Any idea how the problem can be solved?
>
> Thanks in advance,
> Anguel
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Olivier B.]

Hello!

Having same kind of issues with the 7" 4D systems cape, even with Robert 
Nelson's patched driver, I resolved the issue by increasing SEQ_SETTLE 
value to 1023 in ti_am335x_tsc.c .

Hoping it could help someone.

Olivier



Le mardi 3 septembre 2013 13:47:44 UTC+2, Anguel a écrit :
>
> Hi!
>
> I have a 4DCAPE-43T LCD and tested it with Beaglebone Black and the latest 
> Angstrom image (2013.08.21). Unfortunately, I am experiencing input jitter 
> / jumping. I use TSlib's ts_calibrate for calibration and ts_test for 
> testing. In Gnome's calibration tools the same problem appeared: Instead of 
> clicking, I often have some dragging or even random jumping of the pointer. 
> The problem appears especially if the pressure applied to the touchscreen 
> is lower.
>
> I wrote 4D SYSTEMS support regarding the touchscreen jitter and got the 
> following reply:
> "The 4D Cape 43T LCD has been based on the LCD4 from Circuitco and uses 
> the same drivers written for the LCD4 on the Angstrom. Upon testing and 
> verification, the problem of jitter is evident as well on the LCD4 display 
> of Circuitco using the Angstrom 2013.06.20 and 2013.08.21 images so in 
> effect this has nothing to do with the hardware but it’s a software 
> problem."
>
> Actually, I found a video on Youtube with LCD7 where a similar jump / 
> jitter problem can be seen:
> http://www.youtube.com/watch?v=vEfnwL-Jxgw   @ min 2:00
>
> Any idea how the problem can be solved?
>
> Thanks in advance,
> Anguel
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[p3feb83]

Hello Terry,
 I am working on Beaglebone Black interfaced with a custom 
made LCD.The driver of the touchscreen is XWC959.I am not able to find the 
drivers for it.Can u help me here...I know the post is a little old but 
urgent help required.


Regards
Polash

On Monday, December 16, 2013 2:03:25 PM UTC+5:30, Terry Storm wrote:
>
> Hmm,
>
> There are 2 Android builds that I know of, one from TI which is the 3.2 
> Kernel which does work fine 
> http://downloads.ti.com/sitara_android/esd/TI_Android_DevKit/TI_Android_JB_4_2_2_DevKit_4_1_1/index_FDS.html,
>  
> and then this one which uses 3.8 which also works fine 
> http://icculus.org/~hendersa/android/
>
> Both work correctly for touch...
>
> I didn't realise Angstrom was abandoned, that is not good.
> So what is the new most supported distribution for the BBB and LCD capes?
>
> The touch problem is incredibly frustrating.
>
> Thanks for the info
>
> On Monday, 16 December 2013 19:56:40 UTC+13, Anguel wrote:
>>
>> I have given up with all LCD capes, there are driver bugs in the 3.8 
>> kernel as stated before (see my previous postings). Afaik Android uses the 
>> old 3.2 kernel an therefore works ok.
>> Also, I have the impression that Angstrom development for the BBB is 
>> completely abandoned now.
>> Just hope that the Buildroot people will soon have full support for the 
>> BBB...
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Gerald Coley]

As was previously indicated to you, this is an issue with X11, a bug. If
you will fix the X11 it should work fine. Or just use the latest Angstrom
build.

This is you decision as to how you handle it.

Gerald



On Mon, Sep 23, 2013 at 11:00 AM, Anguel  wrote:

> Hi Terry,
>
> Nice to know that I am not the only one who cares about the touchscreen.
> Neither CircuitCo nor 4D Systems seem to really care about the problem.
> They sell the displays but don't reply to my e-mails anymore. I also
> reported the problem on Beaglebone IRC but did not receive any help there.
> I even tried tweaking a bit in the kernel but without success. I just don't
> have the experience to dig deeper in the ADC drivers and chase for the bug.
>
> The latest patches were actually submitted by Zubair Lutfullah, he seems
> to adapt them (from the TI driver developers who write them for the older
> kernel afaik). Zubair told me that he already knew about the jitter problem
> and gave me the following reply: "The touchscreen driver that was patched
> in the linux kernel was different compared to the old patches in the
> beaglebone tree. And we try to keep the beaglebone tree close to the
> mainline. The old 3.8 patches were ok. The mainlined ones introduced this
> problem.. A fix would require a comparison of the two drivers to figure out
> what went wrong and upload a patch to the mainline.. It would require
> time.."
>
> Unfortunately, Zubair is very busy right now. He also mailed his reply to
> Koen Kooi, one of the main Angstrom developers (also works at CircuitCo
> according to his Google+ profile). I am afraid that Koen is also very busy
> and won't have the time to look into the issue. So we can just hope that
> someone with more experience can fix the issue in the near future.
>
> Regards,
> Anguel
>
>
>
> On Monday, September 23, 2013 7:08:36 AM UTC+2, terrys...@gmail.com wrote:
>>
>> Hi Anguel
>>
>> I too have the same problem. I have a LCD4 and a LCD7 and both do the
>> same thing.
>> I suspect since the 4D Systems displays use the same drivers the
>> 4DCAPE-43T does the same thing, so it doesn't seem to be hardware related
>> at all since they use different brand touch screens.
>>
>> Have you had any reply out of CircuitCo?
>> Does CircuitCo actually write the drivers or is it someone else?
>> Can anyone help and point us to someone who wrote the drivers that we can
>> discuss this with?
>>
>> I know a number of other people who have these displays and experience
>> the exact same thing, so it is not just isolated to us 2 people.
>>
>> Please can someone point us in the right direction?
>>
>> Thanks
>> Terry
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Gerald Coley]

When things change upstream and break, it can take time to get fixes
created, tested, verified, and back upstream so it works out of the box. A
lot of things changed in the 3.8 Kernel. But, only the owners can fix it,
unless someone wants to create a patch to make it work. Then again, by the
time one would create that, the owner would have fixed it.

Linux changes all the time. If you want full SW support for these displays
then you would need to add $500 to the cost of each of them. The concept
here is the people that buy them, know how Linux works and can get things
going themselves and make what ever tweaks are required. Supporting all the
different kernel versions and distributions, that is no feasible.

Gerald



On Mon, Sep 23, 2013 at 4:46 PM,  wrote:

> Hi Anguel
>
> Probably a little harsh to say CircuitCo and 4D Systems don't care about
> the problem. If you look at what 4D Systems claims, they state the software
> is not written or supported by them and they are essentially supplying
> hardware only, so they are actually unable to do anything about it even if
> they wanted to. I am still confused about what role CircuitCo plays, if
> they are just a hardware supplier or do software too. Beaglebone.org and
> beagleboardtoys.org along with TI and all the other players, I really
> have no idea who does what.
>
> I do hope however we can get to the bottom of it.
>
> Hi Gerald
>
> Being a beginner with Linux, I don't even know what the X11 is. I have
> tried the latest Angstrom release for the BBB and the touch issue is still
> present, or are you meaning something else?
> It does seem a little disappointing how the software does not work
> correctly for the hardware. I have a friend who was building an industrial
> product with the LCD4 and BBB, yet due to the touch issues the product was
> useless, so he ended up using a different solution entirely. I am sure
> there are many others who fall into this camp too.
>
> I do hope we can find a solution
>
> Regards
> Terry
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[terrystorm23]

Just downloaded the TI Android 4.2.2 release, which works for the LCD4 so 
should work for the 4DCAPE-43T also.
No touch issues. Installed a few drawing apps and it performs nicely. 
Installed a screen rotation utility and that enables portrait or landscape 
mode so that works nicely too.
Played some videos and that works nicely.
Overall rather happy. Proves its not the hardware.

Terry


On Tuesday, 24 September 2013 11:41:24 UTC+12, Gerald wrote:
>
> When things change upstream and break, it can take time to get fixes 
> created, tested, verified, and back upstream so it works out of the box. A 
> lot of things changed in the 3.8 Kernel. But, only the owners can fix it, 
> unless someone wants to create a patch to make it work. Then again, by the 
> time one would create that, the owner would have fixed it.
>
> Linux changes all the time. If you want full SW support for 
> these displays  then you would need to add $500 to the cost of each of 
> them. The concept here is the people that buy them, know how Linux works 
> and can get things going themselves and make what ever tweaks are 
> required. Supporting all the different kernel versions and distributions, 
> that is no feasible.
>
> Gerald
>
>
>
> On Mon, Sep 23, 2013 at 4:46 PM, >wrote:
>
>> Hi Anguel
>>
>> Probably a little harsh to say CircuitCo and 4D Systems don't care about 
>> the problem. If you look at what 4D Systems claims, they state the software 
>> is not written or supported by them and they are essentially supplying 
>> hardware only, so they are actually unable to do anything about it even if 
>> they wanted to. I am still confused about what role CircuitCo plays, if 
>> they are just a hardware supplier or do software too. Beaglebone.org and 
>> beagleboardtoys.org along with TI and all the other players, I really 
>> have no idea who does what.
>>
>> I do hope however we can get to the bottom of it.
>>
>> Hi Gerald
>>
>> Being a beginner with Linux, I don't even know what the X11 is. I have 
>> tried the latest Angstrom release for the BBB and the touch issue is still 
>> present, or are you meaning something else?
>> It does seem a little disappointing how the software does not work 
>> correctly for the hardware. I have a friend who was building an industrial 
>> product with the LCD4 and BBB, yet due to the touch issues the product was 
>> useless, so he ended up using a different solution entirely. I am sure 
>> there are many others who fall into this camp too.
>>
>> I do hope we can find a solution
>>
>> Regards
>> Terry
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Anguel]

How do you know this is a X11 bug? I see the same bug with TS_LIB. It is 
somewhere deep in the driver.


On Monday, September 23, 2013 9:04:12 PM UTC+2, Gerald wrote:
> As was previously indicated to you, this is an issue with X11, a bug. If you 
> will fix the X11 it should work fine. Or just use the latest Angstrom build.
> 
> 
> This is you decision as to how you handle it.
> 
> 
> 
> Gerald
> 
> 
> 
> 
> 
> On Mon, Sep 23, 2013 at 11:00 AM, Anguel  wrote:
> 
> 
> Hi Terry,
> 
> Nice to know that I am not the only one who cares about the touchscreen. 
> Neither CircuitCo nor 4D Systems seem to really care about the problem. They 
> sell the displays but don't reply to my e-mails anymore. I also reported the 
> problem on Beaglebone IRC but did not receive any help there. I even tried 
> tweaking a bit in the kernel but without success. I just don't have the 
> experience to dig deeper in the ADC drivers and chase for the bug.
> 
> 
> The latest patches were actually submitted by Zubair Lutfullah, he seems to 
> adapt them (from the TI driver developers who write them for the older kernel 
> afaik). Zubair told me that he already knew about the jitter problem and gave 
> me the following reply: "The touchscreen driver that was patched in the linux 
> kernel
> was different compared to the old patches in the beaglebone
> tree. And we try to keep the beaglebone tree close to the
> mainline. The old 3.8 patches were ok. The
> mainlined ones introduced this problem.. A fix would require a 
> comparison of the two drivers to
> figure out what went wrong and upload a patch to the
> mainline.. It would require time.."
> 
> Unfortunately, Zubair is very busy right now. He also mailed his reply to 
> Koen Kooi, one of the main Angstrom developers (also works at CircuitCo 
> according to his Google+ profile). I am afraid that Koen is also very busy 
> and won't have the time to look into the issue. So we can just hope that 
> someone with more experience can fix the issue in the near future.
> 
> 
> Regards,
> Anguel
> 
> 
> 
> 
> On Monday, September 23, 2013 7:08:36 AM UTC+2, terrys...@gmail.com wrote:
> 
> Hi Anguel
> 
> 
> I too have the same problem. I have a LCD4 and a LCD7 and both do the same 
> thing.
> I suspect since the 4D Systems displays use the same drivers the 4DCAPE-43T 
> does the same thing, so it doesn't seem to be hardware related at all since 
> they use different brand touch screens.
> 
> 
> 
> Have you had any reply out of CircuitCo?
> Does CircuitCo actually write the drivers or is it someone else?
> Can anyone help and point us to someone who wrote the drivers that we can 
> discuss this with?
> 
> 
> 
> I know a number of other people who have these displays and experience the 
> exact same thing, so it is not just isolated to us 2 people.
> 
> 
> Please can someone point us in the right direction?
> 
> 
> 
> Thanks
> Terry
> 
> 
> 
> 
> 
> 
> -- 
> 
> For more options, visit http://beagleboard.org/discuss
> 
> --- 
> 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> 
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard...@googlegroups.com.
> 
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Anguel]

Gerald,


> Linux changes all the time. If you want full SW support for 
> these displays  then you would need to add $500 to the cost of each of them.
>

That's an interesting calculation, I wonder how you have calculated that 
price. The CircuitCo LCD prices are actually very high for what they offer. 
So please don't tell me that they do not make any profit and do it only 
because they like the Linux community.
 

> The concept here is the people that buy them, know how Linux works and can 
> get things going themselves and make what ever tweaks are 
> required. Supporting all the different kernel versions and distributions, 
> that is no feasible.
>

Probably this is the nice business concept used by TI, CircuitCo, etc. Sell 
chips and boards, make money, but let the open source community write the 
software and support everything for free. Just make a product, label it to 
be "for developers" and sell it without any support. This seems to be a 
very nice buisiness model. Those boards and capes are not made by students 
in a garage and sold in low quantities, they are professionally distributed 
through Digikey, Mouser, etc. and TI and CircuitCo do profit from the 
sales. You say that every developer who uses the boards is supposed to be 
able to rewrite and patch low level Linux kernel drivers? He is supposed to 
have the time, knowledge and ressources to fix bugs that would cost the 
manufacturers hundreds of thousands of dollars? Here I am just referring to 
your $500 price tag! And if someone fixes the bugs for free this just means 
that CircuitCo, TI, etc. can sell even more "development boards" and chips. 
Nice concept...

Who is actually behind Beagleboard.org? It is TI and CircuitCo as far as I 
see. Refering to your other post, pointing me to "just use the latest 
Angstrom" I wonder if you have not read my previous posts. Nobody has ever 
pointed me to any X11 bug (which IMHO is not the problem at all). Zubair, 
one of the driver developers, has clearly stated that the bug is known and 
is caused by the drivers which are in the kernel. If I am not mistaken, you 
are responsible for beagleboard.org, you are a TI employee and you are 
responsible for quality assurance. I still wonder why it is still not 
written in big red letters on the LCD pages of CircuitCo (and 4D Systems 
should then copy and paste that) that NONE of their displays work with the 
latest Angstrom images. Please update that information so people can think 
again if they should buy those boards and capes for their projects.

Regards,

Anguel



>
>
> On Mon, Sep 23, 2013 at 4:46 PM, >wrote:
>
>> Hi Anguel
>>
>> Probably a little harsh to say CircuitCo and 4D Systems don't care about 
>> the problem. If you look at what 4D Systems claims, they state the software 
>> is not written or supported by them and they are essentially supplying 
>> hardware only, so they are actually unable to do anything about it even if 
>> they wanted to. I am still confused about what role CircuitCo plays, if 
>> they are just a hardware supplier or do software too. Beaglebone.org and 
>> beagleboardtoys.org along with TI and all the other players, I really 
>> have no idea who does what.
>>
>> I do hope however we can get to the bottom of it.
>>
>> Hi Gerald
>>
>> Being a beginner with Linux, I don't even know what the X11 is. I have 
>> tried the latest Angstrom release for the BBB and the touch issue is still 
>> present, or are you meaning something else?
>> It does seem a little disappointing how the software does not work 
>> correctly for the hardware. I have a friend who was building an industrial 
>> product with the LCD4 and BBB, yet due to the touch issues the product was 
>> useless, so he ended up using a different solution entirely. I am sure 
>> there are many others who fall into this camp too.
>>
>> I do hope we can find a solution
>>
>> Regards
>> Terry
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Gerald Coley]

That is what I was told by Circuitco.

Gerald


On Tue, Sep 24, 2013 at 12:55 AM, Anguel  wrote:

> How do you know this is a X11 bug? I see the same bug with TS_LIB. It is
> somewhere deep in the driver.
>
>
> On Monday, September 23, 2013 9:04:12 PM UTC+2, Gerald wrote:
> > As was previously indicated to you, this is an issue with X11, a bug. If
> you will fix the X11 it should work fine. Or just use the latest Angstrom
> build.
> >
> >
> > This is you decision as to how you handle it.
> >
> >
> >
> > Gerald
> >
> >
> >
> >
> >
> > On Mon, Sep 23, 2013 at 11:00 AM, Anguel  wrote:
> >
> >
> > Hi Terry,
> >
> > Nice to know that I am not the only one who cares about the touchscreen.
> Neither CircuitCo nor 4D Systems seem to really care about the problem.
> They sell the displays but don't reply to my e-mails anymore. I also
> reported the problem on Beaglebone IRC but did not receive any help there.
> I even tried tweaking a bit in the kernel but without success. I just don't
> have the experience to dig deeper in the ADC drivers and chase for the bug.
> >
> >
> > The latest patches were actually submitted by Zubair Lutfullah, he seems
> to adapt them (from the TI driver developers who write them for the older
> kernel afaik). Zubair told me that he already knew about the jitter problem
> and gave me the following reply: "The touchscreen driver that was patched
> in the linux kernel
> > was different compared to the old patches in the beaglebone
> > tree. And we try to keep the beaglebone tree close to the
> > mainline. The old 3.8 patches were ok. The
> > mainlined ones introduced this problem.. A fix would require
> a comparison of the two drivers to
> > figure out what went wrong and upload a patch to the
> > mainline.. It would require time.."
> >
> > Unfortunately, Zubair is very busy right now. He also mailed his reply
> to Koen Kooi, one of the main Angstrom developers (also works at CircuitCo
> according to his Google+ profile). I am afraid that Koen is also very busy
> and won't have the time to look into the issue. So we can just hope that
> someone with more experience can fix the issue in the near future.
> >
> >
> > Regards,
> > Anguel
> >
> >
> >
> >
> > On Monday, September 23, 2013 7:08:36 AM UTC+2, terrys...@gmail.comwrote:
> >
> > Hi Anguel
> >
> >
> > I too have the same problem. I have a LCD4 and a LCD7 and both do the
> same thing.
> > I suspect since the 4D Systems displays use the same drivers the
> 4DCAPE-43T does the same thing, so it doesn't seem to be hardware related
> at all since they use different brand touch screens.
> >
> >
> >
> > Have you had any reply out of CircuitCo?
> > Does CircuitCo actually write the drivers or is it someone else?
> > Can anyone help and point us to someone who wrote the drivers that we
> can discuss this with?
> >
> >
> >
> > I know a number of other people who have these displays and experience
> the exact same thing, so it is not just isolated to us 2 people.
> >
> >
> > Please can someone point us in the right direction?
> >
> >
> >
> > Thanks
> > Terry
> >
> >
> >
> >
> >
> >
> > --
> >
> > For more options, visit http://beagleboard.org/discuss
> >
> > ---
> >
> > You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> >
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to beagleboard...@googlegroups.com.
> >
> > For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Anguel]

Gerald,

CircuitCo support did not even answer my e-mail regarding the 
non-functional touchscreen. 4D Systems at least admitted that this is a 
well known problem. Once again: Why don't they clearly state on their LCD 
product pages that the touchscreen does not work in latest Angstrom? I 
really hope that customers see my thread before buying a LCD with 
touchscreen.

Anguel


On Tuesday, September 24, 2013 3:15:23 PM UTC+2, Gerald wrote:
>
> That is what I was told by Circuitco. 
>
> Gerald
>
>
> On Tue, Sep 24, 2013 at 12:55 AM, Anguel 
> > wrote:
>
>> How do you know this is a X11 bug? I see the same bug with TS_LIB. It is 
>> somewhere deep in the driver.
>>
>>
>> On Monday, September 23, 2013 9:04:12 PM UTC+2, Gerald wrote:
>> > As was previously indicated to you, this is an issue with X11, a bug. 
>> If you will fix the X11 it should work fine. Or just use the latest 
>> Angstrom build.
>> >
>> >
>> > This is you decision as to how you handle it.
>> >
>> >
>> >
>> > Gerald
>> >
>> >
>> >
>> >
>> >
>> > On Mon, Sep 23, 2013 at 11:00 AM, Anguel  wrote:
>> >
>> >
>> > Hi Terry,
>> >
>> > Nice to know that I am not the only one who cares about the 
>> touchscreen. Neither CircuitCo nor 4D Systems seem to really care about the 
>> problem. They sell the displays but don't reply to my e-mails anymore. I 
>> also reported the problem on Beaglebone IRC but did not receive any help 
>> there. I even tried tweaking a bit in the kernel but without success. I 
>> just don't have the experience to dig deeper in the ADC drivers and chase 
>> for the bug.
>> >
>> >
>> > The latest patches were actually submitted by Zubair Lutfullah, he 
>> seems to adapt them (from the TI driver developers who write them for the 
>> older kernel afaik). Zubair told me that he already knew about the jitter 
>> problem and gave me the following reply: "The touchscreen driver that was 
>> patched in the linux kernel
>> > was different compared to the old patches in the beaglebone
>> > tree. And we try to keep the beaglebone tree close to the
>> > mainline. The old 3.8 patches were ok. The
>> > mainlined ones introduced this problem.. A fix would 
>> require a comparison of the two drivers to
>> > figure out what went wrong and upload a patch to the
>> > mainline.. It would require time.."
>> >
>> > Unfortunately, Zubair is very busy right now. He also mailed his reply 
>> to Koen Kooi, one of the main Angstrom developers (also works at CircuitCo 
>> according to his Google+ profile). I am afraid that Koen is also very busy 
>> and won't have the time to look into the issue. So we can just hope that 
>> someone with more experience can fix the issue in the near future.
>> >
>> >
>> > Regards,
>> > Anguel
>> >
>> >
>> >
>> >
>> > On Monday, September 23, 2013 7:08:36 AM UTC+2, terrys...@gmail.comwrote:
>> >
>> > Hi Anguel
>> >
>> >
>> > I too have the same problem. I have a LCD4 and a LCD7 and both do the 
>> same thing.
>> > I suspect since the 4D Systems displays use the same drivers the 
>> 4DCAPE-43T does the same thing, so it doesn't seem to be hardware related 
>> at all since they use different brand touch screens.
>> >
>> >
>> >
>> > Have you had any reply out of CircuitCo?
>> > Does CircuitCo actually write the drivers or is it someone else?
>> > Can anyone help and point us to someone who wrote the drivers that we 
>> can discuss this with?
>> >
>> >
>> >
>> > I know a number of other people who have these displays and experience 
>> the exact same thing, so it is not just isolated to us 2 people.
>> >
>> >
>> > Please can someone point us in the right direction?
>> >
>> >
>> >
>> > Thanks
>> > Terry
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> >
>> > For more options, visit http://beagleboard.org/discuss
>> >
>> > ---
>> >
>> > You received this message because you are subscribed to the Google 
>> Groups "BeagleBoard" group.
>> >
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an email to beagleboard...@googlegroups.com.
>> >
>> > For more options, visit https://groups.google.com/groups/opt_out.
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Gerald Coley]

I would not buy it either. Contact the president at:

cl...@circuitco.com

Gerald


On Thu, Sep 26, 2013 at 5:53 AM, Anguel  wrote:

> Gerald,
>
> CircuitCo support did not even answer my e-mail regarding the
> non-functional touchscreen. 4D Systems at least admitted that this is a
> well known problem. Once again: Why don't they clearly state on their LCD
> product pages that the touchscreen does not work in latest Angstrom? I
> really hope that customers see my thread before buying a LCD with
> touchscreen.
>
> Anguel
>
>
>
> On Tuesday, September 24, 2013 3:15:23 PM UTC+2, Gerald wrote:
>
>> That is what I was told by Circuitco.
>>
>> Gerald
>>
>>
>> On Tue, Sep 24, 2013 at 12:55 AM, Anguel  wrote:
>>
>>> How do you know this is a X11 bug? I see the same bug with TS_LIB. It is
>>> somewhere deep in the driver.
>>>
>>>
>>> On Monday, September 23, 2013 9:04:12 PM UTC+2, Gerald wrote:
>>> > As was previously indicated to you, this is an issue with X11, a bug.
>>> If you will fix the X11 it should work fine. Or just use the latest
>>> Angstrom build.
>>> >
>>> >
>>> > This is you decision as to how you handle it.
>>> >
>>> >
>>> >
>>> > Gerald
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Mon, Sep 23, 2013 at 11:00 AM, Anguel  wrote:
>>> >
>>> >
>>> > Hi Terry,
>>> >
>>> > Nice to know that I am not the only one who cares about the
>>> touchscreen. Neither CircuitCo nor 4D Systems seem to really care about the
>>> problem. They sell the displays but don't reply to my e-mails anymore. I
>>> also reported the problem on Beaglebone IRC but did not receive any help
>>> there. I even tried tweaking a bit in the kernel but without success. I
>>> just don't have the experience to dig deeper in the ADC drivers and chase
>>> for the bug.
>>> >
>>> >
>>> > The latest patches were actually submitted by Zubair Lutfullah, he
>>> seems to adapt them (from the TI driver developers who write them for the
>>> older kernel afaik). Zubair told me that he already knew about the jitter
>>> problem and gave me the following reply: "The touchscreen driver that was
>>> patched in the linux kernel
>>> > was different compared to the old patches in the beaglebone
>>> > tree. And we try to keep the beaglebone tree close to the
>>> > mainline. The old 3.8 patches were ok. The
>>> > mainlined ones introduced this problem.. A fix would
>>> require a comparison of the two drivers to
>>> > figure out what went wrong and upload a patch to the
>>> > mainline.. It would require time.."
>>> >
>>> > Unfortunately, Zubair is very busy right now. He also mailed his reply
>>> to Koen Kooi, one of the main Angstrom developers (also works at CircuitCo
>>> according to his Google+ profile). I am afraid that Koen is also very busy
>>> and won't have the time to look into the issue. So we can just hope that
>>> someone with more experience can fix the issue in the near future.
>>> >
>>> >
>>> > Regards,
>>> > Anguel
>>> >
>>> >
>>> >
>>> >
>>> > On Monday, September 23, 2013 7:08:36 AM UTC+2, terrys...@gmail.comwrote:
>>> >
>>> > Hi Anguel
>>> >
>>> >
>>> > I too have the same problem. I have a LCD4 and a LCD7 and both do the
>>> same thing.
>>> > I suspect since the 4D Systems displays use the same drivers the
>>> 4DCAPE-43T does the same thing, so it doesn't seem to be hardware related
>>> at all since they use different brand touch screens.
>>> >
>>> >
>>> >
>>> > Have you had any reply out of CircuitCo?
>>> > Does CircuitCo actually write the drivers or is it someone else?
>>> > Can anyone help and point us to someone who wrote the drivers that we
>>> can discuss this with?
>>> >
>>> >
>>> >
>>> > I know a number of other people who have these displays and experience
>>> the exact same thing, so it is not just isolated to us 2 people.
>>> >
>>> >
>>> > Please can someone point us in the right direction?
>>> >
>>> >
>>> >
>>> > Thanks
>>> > Terry
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > For more options, visit http://beagleboard.org/discuss
>>> >
>>> > ---
>>> >
>>> > You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> >
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard...@googlegroups.**com.
>>> >
>>> > For more options, visit 
>>> > https://groups.google.com/**groups/opt_out
>>> .
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard...@**googlegroups.com.
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out
>>> .
>>>
>>
>>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you ar

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[garyamort]

On Tuesday, September 24, 2013 5:33:36 AM UTC-4, Anguel wrote:
>
>
>  
>
>> The concept here is the people that buy them, know how Linux works and 
>> can get things going themselves and make what ever tweaks are 
>> required. Supporting all the different kernel versions and distributions, 
>> that is no feasible.
>>
>
> Probably this is the nice business concept used by TI, CircuitCo, etc. 
> Sell chips and boards, make money, but let the open source community write 
> the software and support everything for free. Just make a product, label it 
> to be "for developers" and sell it without any support.
>


There is a difference between "any support" and "not supported".

"Not supported" means that it has been tested under a very specific 
software configuration and works for that configuration.  If you check the 
Linux Source code, you will find a LOT of code written by Texas Instruments 
- so they are certainly providing SOME support.

Interestingly, if you check the LCD drivers you will find that for small 
LCD screens, most of those drivers come from Nokia[or at the very least are 
based off Nokia drivers].

So no, it is not "the community" that is expected to support things "for 
free".  How it works is that Nokia, a cell phone manufacturer, decides to 
use a Texas Instruments processor in a cell phone.  They decide to use a 
specific model of LCD screen.   They pay developers to create an LCD driver 
for a Texas Instruments supported linux kernel.  If they find a bug in the 
TI LCD interface, they contact TI and TI works with them to fix it.  Once 
they have the TI supported kernel working, they then try to use the same 
driver in the latest version of Android.  If it doesn't work, their 
developers have to figure out what changes were made that broke something, 
and then they fix it.  Considering that their going to order 100,000+ TI 
processors, they probably pay TI for support so their developers and TI's 
developers work on the driver.

When that is all done, this driver which was written by Nokia with Texas 
Instruments help is then given to "the community" for free - under the 
terms of the standard GPL license, including:
"THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY 
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, *YOU ASSUME THE COST OF 
ALL NECESSARY SERVICING, REPAIR OR CORRECTION*."

Please note that last line as it is the one you seem to object to, and yet 
it is the very reason companies are willing to give away applications they 
paid developers to write to the community - as they are not required to 
support them and you agreed to assume the cost.

Android does NOT use the X11 window system, so the driver written by Nokia 
for their phone may not work properly for a Ubuntu desktop.  As the reason 
Nokia paid developers to write it was for an android phone, I can't see any 
reason to expect them to make sure it works for Ubuntu "for free".

Your receiving a huge amount of support from TI and CitcuitCo - however 
your "tone of voice" is demanding that they FIX the problem.  They are not 
required to fix the problem, and you agreed to assume the cost of all 
correction.  In all fairness, they should be billing you for the time spent 
responding to you as you agreed to "assume the cost".  

You have identified a problem.  Programmers from "the community", "Texas 
Instruments", and "CircuitCo" have acknowledged the problem, done a good 
bit of deductive reasoning to determine where the problem lies and the 
general idea of how to fix it and given this information to you for free.

There are four solutions specifically for you:

A) Use the linux versions that are known to work for the device, move on 
with your life.

B) Wait for someone to be willing to fix it "for free"

C) Fix it "yourself" - note this does not mean you personally, this means 
either you fix it or hire someone to fix it.

D) Give up in frustration and use a different product.  If you wish, loudly 
proclaim that "everything just works out of the box".  A few weeks down the 
road you will discover a different problem with the interaction of a 
completely different set of drivers that the vendor of that product doesn't 
use and does not support.  When you do, if you choose to loudly proclaim 
your "solution" you can choose to acknowledge that your solution that "just 
worked" actually does not work so others who may be misled by your comments 
to also switch don't suffer the same issue.  Or you can keep quiet about it 
to avoid looking foolish and thus cause economic harm to others.


As a summary "not supported" means that the company is not

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[David Anders]

Anguel,

circuitco responds to ALL emails sent to supp...@beagleboardtoys.com and 
supp...@boardzoo.com for products produced by circuitco. we have responded 
to a number of emails with questions about the jitter issue. we provide 
recommended configurations and setup for all of the products, however we 
sell the hardware independently for developers to do as they choose with 
it. i highlight that fact developers. we can not test every single 
software load out there for every single product. as such a developer is 
responsible for configuring their own software functionality. we provide a 
warranty and guarantee on the hardware along with full documentation. one 
of the ways we keep costs low is for these products to be community 
supported. if you are unhappy with the lcd cape, we will be happy to refund 
your money for both the cape and beaglebone black so that you may select 
something more to your liking. may i suggest the TI AM33x EVM platform? 
(https://estore.ti.com/TMDXEVM3358-AM335x-Evaluation-Module-P2714.aspx). it 
retails for $995USD.

thanks
Dave Anders
Circuitco

On Thursday, September 26, 2013 5:53:32 AM UTC-5, Anguel wrote:
>
> Gerald,
>
> CircuitCo support did not even answer my e-mail regarding the 
> non-functional touchscreen. 4D Systems at least admitted that this is a 
> well known problem. Once again: Why don't they clearly state on their LCD 
> product pages that the touchscreen does not work in latest Angstrom? I 
> really hope that customers see my thread before buying a LCD with 
> touchscreen.
>
> Anguel
>
>
> On Tuesday, September 24, 2013 3:15:23 PM UTC+2, Gerald wrote:
>>
>> That is what I was told by Circuitco. 
>>
>> Gerald
>>
>>
>> On Tue, Sep 24, 2013 at 12:55 AM, Anguel  wrote:
>>
>>> How do you know this is a X11 bug? I see the same bug with TS_LIB. It is 
>>> somewhere deep in the driver.
>>>
>>>
>>> On Monday, September 23, 2013 9:04:12 PM UTC+2, Gerald wrote:
>>> > As was previously indicated to you, this is an issue with X11, a bug. 
>>> If you will fix the X11 it should work fine. Or just use the latest 
>>> Angstrom build.
>>> >
>>> >
>>> > This is you decision as to how you handle it.
>>> >
>>> >
>>> >
>>> > Gerald
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Mon, Sep 23, 2013 at 11:00 AM, Anguel  wrote:
>>> >
>>> >
>>> > Hi Terry,
>>> >
>>> > Nice to know that I am not the only one who cares about the 
>>> touchscreen. Neither CircuitCo nor 4D Systems seem to really care about the 
>>> problem. They sell the displays but don't reply to my e-mails anymore. I 
>>> also reported the problem on Beaglebone IRC but did not receive any help 
>>> there. I even tried tweaking a bit in the kernel but without success. I 
>>> just don't have the experience to dig deeper in the ADC drivers and chase 
>>> for the bug.
>>> >
>>> >
>>> > The latest patches were actually submitted by Zubair Lutfullah, he 
>>> seems to adapt them (from the TI driver developers who write them for the 
>>> older kernel afaik). Zubair told me that he already knew about the jitter 
>>> problem and gave me the following reply: "The touchscreen driver that was 
>>> patched in the linux kernel
>>> > was different compared to the old patches in the beaglebone
>>> > tree. And we try to keep the beaglebone tree close to the
>>> > mainline. The old 3.8 patches were ok. The
>>> > mainlined ones introduced this problem.. A fix would 
>>> require a comparison of the two drivers to
>>> > figure out what went wrong and upload a patch to the
>>> > mainline.. It would require time.."
>>> >
>>> > Unfortunately, Zubair is very busy right now. He also mailed his reply 
>>> to Koen Kooi, one of the main Angstrom developers (also works at CircuitCo 
>>> according to his Google+ profile). I am afraid that Koen is also very busy 
>>> and won't have the time to look into the issue. So we can just hope that 
>>> someone with more experience can fix the issue in the near future.
>>> >
>>> >
>>> > Regards,
>>> > Anguel
>>> >
>>> >
>>> >
>>> >
>>> > On Monday, September 23, 2013 7:08:36 AM UTC+2, terrys...@gmail.comwrote:
>>> >
>>> > Hi Anguel
>>> >
>>> >
>>> > I too have the same problem. I have a LCD4 and a LCD7 and both do the 
>>> same thing.
>>> > I suspect since the 4D Systems displays use the same drivers the 
>>> 4DCAPE-43T does the same thing, so it doesn't seem to be hardware related 
>>> at all since they use different brand touch screens.
>>> >
>>> >
>>> >
>>> > Have you had any reply out of CircuitCo?
>>> > Does CircuitCo actually write the drivers or is it someone else?
>>> > Can anyone help and point us to someone who wrote the drivers that we 
>>> can discuss this with?
>>> >
>>> >
>>> >
>>> > I know a number of other people who have these displays and experience 
>>> the exact same thing, so it is not just isolated to us 2 people.
>>> >
>>> >
>>> > Please can someone point us in the right direction?
>>> >
>>> >
>>> >
>>> > Thanks
>>> >

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Anguel]

Gary,

Thank you for your extensive and philosophic point of view. I just don't 
understand how Nokia is related to the problem... It is clear that at some 
point in time some bug has slipped into the TI SoC ADC kernel drivers or 
the touchscreen drivers that use these ADC drivers. What I am angry about 
is that CircuitCo (and 4D Systems) know about the problem. Besides the fact 
that they don't do anything to fix it (although afaik they have good people 
working on Angstrom), they could at least post a notice on their product's 
webpages so customers don't have to chase where the bugs come from for 
weeks. The fact that they have still not done it makes me think that they 
want to keep their sales high. Again, the prices for the LCD boards are not 
low and we cannot talk about break even here. I am sure that actually many 
units are being sold together with the high sales volumes of the Beaglebone 
+ Beaglebone Black.

Regards,
Anguel

On Thursday, September 26, 2013 3:36:48 PM UTC+2, garyamort wrote:
>
>
>
> On Tuesday, September 24, 2013 5:33:36 AM UTC-4, Anguel wrote:
>>
>>
>>  
>>
>>> The concept here is the people that buy them, know how Linux works and 
>>> can get things going themselves and make what ever tweaks are 
>>> required. Supporting all the different kernel versions and distributions, 
>>> that is no feasible.
>>>
>>
>> Probably this is the nice business concept used by TI, CircuitCo, etc. 
>> Sell chips and boards, make money, but let the open source community write 
>> the software and support everything for free. Just make a product, label it 
>> to be "for developers" and sell it without any support.
>>
>
>
> There is a difference between "any support" and "not supported".
>
> "Not supported" means that it has been tested under a very specific 
> software configuration and works for that configuration.  If you check the 
> Linux Source code, you will find a LOT of code written by Texas Instruments 
> - so they are certainly providing SOME support.
>
> Interestingly, if you check the LCD drivers you will find that for small 
> LCD screens, most of those drivers come from Nokia[or at the very least are 
> based off Nokia drivers].
>
> So no, it is not "the community" that is expected to support things "for 
> free".  How it works is that Nokia, a cell phone manufacturer, decides to 
> use a Texas Instruments processor in a cell phone.  They decide to use a 
> specific model of LCD screen.   They pay developers to create an LCD driver 
> for a Texas Instruments supported linux kernel.  If they find a bug in the 
> TI LCD interface, they contact TI and TI works with them to fix it.  Once 
> they have the TI supported kernel working, they then try to use the same 
> driver in the latest version of Android.  If it doesn't work, their 
> developers have to figure out what changes were made that broke something, 
> and then they fix it.  Considering that their going to order 100,000+ TI 
> processors, they probably pay TI for support so their developers and TI's 
> developers work on the driver.
>
> When that is all done, this driver which was written by Nokia with Texas 
> Instruments help is then given to "the community" for free - under the 
> terms of the standard GPL license, including:
> "THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 
> APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 
> HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY 
> OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 
> THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 
> PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 
> IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, *YOU ASSUME THE COST OF 
> ALL NECESSARY SERVICING, REPAIR OR CORRECTION*."
>
> Please note that last line as it is the one you seem to object to, and yet 
> it is the very reason companies are willing to give away applications they 
> paid developers to write to the community - as they are not required to 
> support them and you agreed to assume the cost.
>
> Android does NOT use the X11 window system, so the driver written by Nokia 
> for their phone may not work properly for a Ubuntu desktop.  As the reason 
> Nokia paid developers to write it was for an android phone, I can't see any 
> reason to expect them to make sure it works for Ubuntu "for free".
>
> Your receiving a huge amount of support from TI and CitcuitCo - however 
> your "tone of voice" is demanding that they FIX the problem.  They are not 
> required to fix the problem, and you agreed to assume the cost of all 
> correction.  In all fairness, they should be billing you for the time spent 
> responding to you as you agreed to "assume the cost".  
>
> You have identified a problem.  Programmers from "the community", "Texas 
> Instruments", and "CircuitCo" have acknowledged the problem, done a good 
> bit of deductive reasoning to determine where the p

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Anguel]

David,

The only thing that I can say is that CircuitCo never answered my e-mail. 
If you have responded to so many e-mails regarding the jitter issue and 
after the long discussions here I really wonder why you have STILL not put 
a note that there are well known touchscreen issues with the latest 
official Angstrom images. This would prevent many developers like me from 
spending many weeks searching for the source of the problem and wasting 
their time. Or are you afraid that your sales may drop if people know that 
the touchscreens of your displays don't work with the latest kernel?

Regarding your suggestion for the $995 TI EVM board I may suggest the 
AM335x Starter Kit 
http://processors.wiki.ti.com/index.php/AM335x_Starter_Kit for $199 only.

Regards,
Anguel






On Thursday, September 26, 2013 7:38:42 PM UTC+2, David Anders wrote:
>
> Anguel,
>
> circuitco responds to ALL emails sent to 
> sup...@beagleboardtoys.comand 
> sup...@boardzoo.com  for products produced by circuitco. we 
> have responded to a number of emails with questions about the jitter issue. 
> we provide recommended configurations and setup for all of the products, 
> however we sell the hardware independently for developers to do as they 
> choose with it. i highlight that fact developers. we can not test every 
> single software load out there for every single product. as such a 
> developer is responsible for configuring their own software functionality. 
> we provide a warranty and guarantee on the hardware along with full 
> documentation. one of the ways we keep costs low is for these products to 
> be community supported. if you are unhappy with the lcd cape, we will be 
> happy to refund your money for both the cape and beaglebone black so that 
> you may select something more to your liking. may i suggest the TI AM33x 
> EVM platform? (
> https://estore.ti.com/TMDXEVM3358-AM335x-Evaluation-Module-P2714.aspx). 
> it retails for $995USD.
>
> thanks
> Dave Anders
> Circuitco
>
> On Thursday, September 26, 2013 5:53:32 AM UTC-5, Anguel wrote:
>>
>> Gerald,
>>
>> CircuitCo support did not even answer my e-mail regarding the 
>> non-functional touchscreen. 4D Systems at least admitted that this is a 
>> well known problem. Once again: Why don't they clearly state on their LCD 
>> product pages that the touchscreen does not work in latest Angstrom? I 
>> really hope that customers see my thread before buying a LCD with 
>> touchscreen.
>>
>> Anguel
>>
>>
>> On Tuesday, September 24, 2013 3:15:23 PM UTC+2, Gerald wrote:
>>>
>>> That is what I was told by Circuitco. 
>>>
>>> Gerald
>>>
>>>
>>> On Tue, Sep 24, 2013 at 12:55 AM, Anguel  wrote:
>>>
 How do you know this is a X11 bug? I see the same bug with TS_LIB. It 
 is somewhere deep in the driver.


 On Monday, September 23, 2013 9:04:12 PM UTC+2, Gerald wrote:
 > As was previously indicated to you, this is an issue with X11, a bug. 
 If you will fix the X11 it should work fine. Or just use the latest 
 Angstrom build.
 >
 >
 > This is you decision as to how you handle it.
 >
 >
 >
 > Gerald
 >
 >
 >
 >
 >
 > On Mon, Sep 23, 2013 at 11:00 AM, Anguel  
 wrote:
 >
 >
 > Hi Terry,
 >
 > Nice to know that I am not the only one who cares about the 
 touchscreen. Neither CircuitCo nor 4D Systems seem to really care about 
 the 
 problem. They sell the displays but don't reply to my e-mails anymore. I 
 also reported the problem on Beaglebone IRC but did not receive any help 
 there. I even tried tweaking a bit in the kernel but without success. I 
 just don't have the experience to dig deeper in the ADC drivers and chase 
 for the bug.
 >
 >
 > The latest patches were actually submitted by Zubair Lutfullah, he 
 seems to adapt them (from the TI driver developers who write them for the 
 older kernel afaik). Zubair told me that he already knew about the jitter 
 problem and gave me the following reply: "The touchscreen driver that was 
 patched in the linux kernel
 > was different compared to the old patches in the 
 beaglebone
 > tree. And we try to keep the beaglebone tree close to the
 > mainline. The old 3.8 patches were ok. The
 > mainlined ones introduced this problem.. A fix would 
 require a comparison of the two drivers to
 > figure out what went wrong and upload a patch to the
 > mainline.. It would require time.."
 >
 > Unfortunately, Zubair is very busy right now. He also mailed his 
 reply to Koen Kooi, one of the main Angstrom developers (also works at 
 CircuitCo according to his Google+ profile). I am afraid that Koen is also 
 very busy and won't have the time to look into the issue. So we can just 
 hope that someone with more experience can fix the issue in the near 
>>>

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[garyamort]

On Friday, September 27, 2013 4:47:44 AM UTC-4, Anguel wrote:
>
> Gary,
>
> Thank you for your extensive and philosophic point of view. I just don't 
> understand how Nokia is related to the problem...
> It is clear that at some point in time some bug has slipped into the TI 
> SoC ADC kernel drivers or the touchscreen drivers that use these ADC drivers



If your talking about touchscreens interfaces and LCD screens, your very 
likely using code written by Nokia or one of the other major cell phone 
manufacturers.  If there is a "bug" in the code it is likely that they 
wrote it.  Because the code DOES work under a different version of Linux 
and works under versions of Android - it is not even fair to say the the 
driver has a bug in it.  The driver works for the system it was written in. 
 Why it doesn't work in later versions of Linux may be because there was a 
true bug which only showed up when something else in the kernel changed. 
 It may also be that there were changes to the api functions being used by 
those drivers which changed the way they work.  The word bug tends to be 
taken negatively, as in the programmer of the code containing the bug made 
a mistake.  In the case of changing API's there was no "mistake".  

To understand why you have to understand how Linux itself is developed.   
There are thousands of drivers in the codebase for different items.   For 
those drivers to get into the source tree they must compile AT THE TIME 
THEY ARE ADDED, they must follow Linux Coding Standards, they must work AT 
THE TIME THEY ARE ADDED, and they must be licensed under the GPL.

Once they are IN the codebase then when changes are made to any of the 
functions they use, the programmer making those changes MUST run an 
automatic program to find every single call to that function and fix them - 
hopefully the process will be automatic.   Those changes have to follow the 
same rules as above PLUS every bit of code that they modified[all the 
drivers] must still compile successfully.  Note: it doesn't have to WORK, 
it just hast to compile.  That is because it would cost millions of dollars 
to test every single bit of hardware[since you have to have access to every 
single bit] to ensure that the drivers still function.  The best that can 
be reasonably expected is that they compile.

A better word to use is incompatibility - as you simply have no idea where 
the "bug" is so unless you specify each and every component that is being 
integrated then saying there is a bug in X companies code comes across as 
blaming the companies listed.

As for why I went into the long explanation, you were making comments about 
how TI expects "the community" to support their product for free - so I was 
giving you the true picture - how is a symbiotic relationship and how in 
this case your benefiting from work done by TI and Nokia - and that "the 
community" is expected to modify that work for their own usage if needed.
 

> . What I am angry about is that CircuitCo (and 4D Systems) know about the 
> problem. Besides the fact that they don't do anything to fix it (although 
> afaik they have good people working on Angstrom), they could at least post 
> a notice on their product's webpages so customers don't have to chase where 
> the bugs come from for weeks.
>


The comments in this thread indicated to me that they contributed to fixing 
the problem - in this case identifying where they think the problem lies 
and therefore cutting down on the time needed to debug code.

I will agree 100% that CircuitCo should update their product pages to 
include notices of compatibility issues as well as listing a known good 
software version compatibility matrix.  I only agree about 60% that 4D 
Systems should be doing this as well.

 

> The fact that they have still not done it makes me think that they want to 
> keep their sales high. Again, the prices for the LCD boards are not low and 
> we cannot talk about break even here.
>


We can't?  Consider the following:
SainSmart makes a similiar LCD module for Ardunio:
http://www.sainsmart.com/arduino-compatibles-1/lcd-module/sainsmart-3-2-tft-lcd-display-touch-panel-pcb-adapter-sd-slot-for-arduino-2560.html
  
It costs 16$.  If you go to ebay you can find similiar products for 12$.

Compare this to CircuitCo's 3" board:
http://www.mouser.com/ProductDetail/CircuitCo/BB-BONE-LCD3-01/?qs=2TuNuDMZFZ5UQcnBUi0fGw%3D%3D&gclid=CIy6vY7n67kCFUWd4AodLxkAqg
Which is 70$.

So what are the differences?  Well, first of all, the pin layouts for the 
boards are completely different.  BeagleBone capes have 2 rows of pins, 
while the Ardunio board has 1 row of pins.  I know that pins seem like a 
nothing cost, but the truth is that every time you add big bulky items to a 
board - you increase production costs.  So taking a stab in the dark, I'm 
going to guess that we added 4$ to the cost of the card(20$).  In addition 
to this, a beaglebone cape needs an EEPROM on it which is programmed with 
t

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[omarbeaglebone]

I am using the android 4.2.2 with the 3.2 kernel, downloaded from the TI 
website. I can't get anything on my 4DCAPE-43T. It won't even power up. I 
already booted into Angstrom and the screen does boot up and work so it can't 
be the screen. Anyway you can provide me with the link for your download? Maybe 
yours had teh 3.8 kernel? 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Terry Storm]

Have you checked out the Datasheet from 4D?

It states in there that both of the EEPROM ID Jumpers have to be connected 
for Android for it to work.
Give that a try.

On Thursday, 28 November 2013 18:51:01 UTC+13, omarbea...@gmail.com wrote:
>
> I am using the android 4.2.2 with the 3.2 kernel, downloaded from the TI 
> website. I can't get anything on my 4DCAPE-43T. It won't even power up. I 
> already booted into Angstrom and the screen does boot up and work so it 
> can't be the screen. Anyway you can provide me with the link for your 
> download? Maybe yours had teh 3.8 kernel? 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Terry Storm]

Lots of alternatives you can download
Aptoide  is one for example
Only have to get the apk for that and then download using aptoide like any
other App Store.


On 18 December 2013 17:24, Ian Kidd  wrote:

> I figured.  I'll give that a shot.  Be nice to have an App Store on that
> TI image.
>
>
> On Tuesday, December 17, 2013 9:19:22 PM UTC-7, Terry Storm wrote:
>>
>> Should read
>>
>> "but does not support the Hardware Graphics like the TI one"
>>
>> above.
>>
>> On Wednesday, 18 December 2013 13:27:18 UTC+13, Terry Storm wrote:
>>>
>>> Hi Ian
>>>
>>> Did you try the TI image instead of the Anderson image?
>>> The TI one seems to be more stable and the buttons are actually mapped
>>> to suit Android, which isn't the case on the Anderson image. Anderson Image
>>> is Kernel 3.8 however, but also does support the Hardware Graphics like the
>>> TI one, so the TI one is quite a bit faster too.
>>> I haven't had to calibrate, both just worked for me.
>>> Screen rotation utility was just from the App Store, just some free
>>> rotation app. Cant remember what it was called off the top of my head.
>>>
>>> Try and TI image and report back.
>>> Terry
>>>
>>> On Wednesday, 18 December 2013 12:38:01 UTC+13, Ian Kidd wrote:

 Hi, Terry.  I see you got the touchscreen working in Android.  I'm
 using the Anderson image, and while I can get swipe scrolling to work, it
 doesn't seem to be calibrated for the point of touch.  Any particular
 utility that you use to calibrate the touch on Android.

 Also, what was the screen rotation utility you mentioned?

>>>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/SXTaSUf4aSk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

OK,

Maybe it's time we work together and try to fix this bug. *A beaglebone
black that doesn't support correctly the touchscreen, it's a SHAME !*

So I'm going to try to fix it by myself =>

I prefer to put my conclusion here, because I don't hink everyone has the
time to read my research :




 *1) Presentation of the BUG*



   - When you touch the screen repeatedly ( up and down up and down ) the
   bug seems to happen ! ( rarely, but it does )
   - When you touch the screen continuously, you can see that sometime the
   mouse go far away from your finger .


*2) The driver*

The name of the driver is TI - TSC ADC (Touschscreen and analog digital
converter)

It's easy to find the source of this driver =>
drivers/input/touchscreen/ti_am335x_tsc.c

 *3) The  Interesting part*

 The interesting part of this driver, is this function :

static void titsc_read_coordinates(struct titsc *ts_dev,

u32 *x, u32 *y, u32 *z1, u32 *z2)

{

unsigned int fifocount = titsc_readl(ts_dev, REG_FIFO0CNT);

 unsigned int prev_val_x = ~0, prev_val_y = ~0;

unsigned int prev_diff_x = ~0, prev_diff_y = ~0;

 unsigned int read, diff;

unsigned int i, channel;

unsigned int creads = ts_dev->coordinate_readouts;

*z1 = *z2 = 0;

if (fifocount % (creads * 2 + 2))

 fifocount -= fifocount % (creads * 2 + 2);

/*

 * Delta filter is used to remove large variations in sampled

 * values from ADC. The filter tries to predict where the next

 * coordinate could be. This is done by taking a previous

 * coordinate and subtracting it form current one. Further the

 * algorithm compares the difference with that of a present value,

 * if true the value is reported to the sub system.

 */

for (i = 0; i < fifocount; i++) {

read = titsc_readl(ts_dev, REG_FIFO0);

 channel = (read & 0xf) >> 16;

read &= 0xfff;

 if (channel < creads) {

diff = abs(read - prev_val_x);

 if (diff < prev_diff_x) {

prev_diff_x = diff;

 *x = read;

}

prev_val_x = read;

} else if (channel < creads * 2) {

diff = abs(read - prev_val_y);

if (diff < prev_diff_y) {

prev_diff_y = diff;

*y = read;

}

 prev_val_y = read;

} else if (channel < creads * 2 + 1) {

 *z1 = read;

} else if (channel < creads * 2 + 2) {

 *z2 = read;

}

}

}



So did you watch this code ? Well, In my case, I understand why there is
this huge bug !

We have to admit, that sometime there is noise during the transfer of the
coordinate between the LCD and the driver.

So, this code is supposed to filter any of noise with this :



diff = abs(read - prev_val_x);

if (diff < prev_diff_x) {

prev_diff_x = diff;

*x = read;

}

prev_val_x = read;


Well, I'm sorry, but if the noise happen, you should not save the noise
value has the last position (correct me if I'm wrong ?) .

So, I changed the code with something like that :

 if (channel < creads) {
printk("raw x=%d\n", read);
diff = abs(read - prev_val_x);
if (diff < prev_diff_x) {
printk("x=%d & diff=%d\n", read, diff);
prev_diff_x = diff;
*x = read;
prev_val_x = read;
}

} else if (channel < creads * 2) {
printk("raw y=%d\n", read);
diff = abs(read - prev_val_y);
if (diff < prev_diff_y) {
printk("y=%d & diff=%d\n", read, diff);
prev_diff_y = diff;
*y = read;
prev_val_y = read;
}

} else if (channel < creads * 2 + 1) {
*z1 = read;

} else if (channel < creads * 2 + 2) {
*z2 = read;
}

Also, it's important to note that this function is called by the
function irqreturn_t titsc_irq:
I put a printk to be noticed when the function is called :

static irqreturn_t titsc_irq(int irq, void *dev)
{
struct titsc *ts_dev = dev;
struct input_dev *inp

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Ian Kidd]

I'm going to be the helpless little girl here and ask for a quick synopsis 
of how to apply the patch?  I'm not sure where the file is that gets this 
Diff, because I can't locate it in /lib/modules.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Terry Storm]

Ditto.

Regarding the fix which makes this work 99% of the time...
Have you considered the noise could be on the power lines which power the 
touch screen?
One could assume the power rails are meant to be between GND and VCC, 
however this may not be the case. It then assumes GND is 0 and VCC is Max. 
Since there are 4 AIN's used, it should be possible to read the voltages... 
Maybe do some sort of ratio calculation or something.
Just a thought.

Terry

On Thursday, 9 January 2014 07:56:11 UTC+13, Ian Kidd wrote:
>
> I'm going to be the helpless little girl here and ask for a quick synopsis 
> of how to apply the patch?  I'm not sure where the file is that gets this 
> Diff, because I can't locate it in /lib/modules.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

Lan Kidd, For the patch, I'm sure that Robert Nelson will include it on the
next release of the kernel, same for Koen !

Terry Storm, well not really :) , the noise come when you remove your
finger, always at this time  when the pressure is not enough we got
some crazy x and y value ..


On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm  wrote:

> Ditto.
>
> Regarding the fix which makes this work 99% of the time...
> Have you considered the noise could be on the power lines which power the
> touch screen?
> One could assume the power rails are meant to be between GND and VCC,
> however this may not be the case. It then assumes GND is 0 and VCC is Max.
> Since there are 4 AIN's used, it should be possible to read the voltages...
> Maybe do some sort of ratio calculation or something.
> Just a thought.
>
> Terry
>
>
> On Thursday, 9 January 2014 07:56:11 UTC+13, Ian Kidd wrote:
>>
>> I'm going to be the helpless little girl here and ask for a quick
>> synopsis of how to apply the patch?  I'm not sure where the file is that
>> gets this Diff, because I can't locate it in /lib/modules.
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Will Kostelecky]

I have the same problem with the LCD7 on Archlinux and would really like to 
get it fixed.   I can't find the above file on my installation and am not 
sure where to look.   Or for that matter what to do with the patched file 
if I were able to find it.   Can someone help with a) telling me where to 
look for the right file to patch, and b) tell me how to build a patched 
driver?   I am not a complete neophyte with Linux (I frequently build apps 
from source and can debug build problems)  but I dont know where to start 
with drivers!

Thanks,
Will

On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:
>
> Lan Kidd, For the patch, I'm sure that Robert Nelson will include it on 
> the next release of the kernel, same for Koen !
>
> Terry Storm, well not really :) , the noise come when you remove your 
> finger, always at this time  when the pressure is not enough we got 
> some crazy x and y value ..
>
>
> On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm 
> > wrote:
>
>> Ditto.
>>
>> Regarding the fix which makes this work 99% of the time...
>> Have you considered the noise could be on the power lines which power the 
>> touch screen?
>> One could assume the power rails are meant to be between GND and VCC, 
>> however this may not be the case. It then assumes GND is 0 and VCC is Max. 
>> Since there are 4 AIN's used, it should be possible to read the voltages... 
>> Maybe do some sort of ratio calculation or something.
>> Just a thought.
>>
>> Terry
>>
>>
>> On Thursday, 9 January 2014 07:56:11 UTC+13, Ian Kidd wrote:
>>>
>>> I'm going to be the helpless little girl here and ask for a quick 
>>> synopsis of how to apply the patch?  I'm not sure where the file is that 
>>> gets this Diff, because I can't locate it in /lib/modules.
>>>
>>  -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

I would love to create a patch for you, but i don't know how  I tried
to commit the result, but I got :

beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
# On branch v3.8.13-bone35
# Changes not staged for commit:
#   (use "git add ..." to update what will be committed)
#   (use "git checkout -- ..." to discard changes in working
directory)
#
# modified:   drivers/input/touchscreen/ti_am335x_tsc.c
#
no changes added to commit (use "git add" and/or "git commit -a")
beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
drivers/input/touchscreen/ti_am335x_tsc.c
error: insufficient permission for adding an object to repository database
.git/objects

error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to insert into
database
error: unable to index file drivers/input/touchscreen/ti_am335x_tsc.c
fatal: updating files failed



On Sun, Jan 12, 2014 at 1:35 PM, Will Kostelecky
wrote:

> I have the same problem with the LCD7 on Archlinux and would really like
> to get it fixed.   I can't find the above file on my installation and am
> not sure where to look.   Or for that matter what to do with the patched
> file if I were able to find it.   Can someone help with a) telling me where
> to look for the right file to patch, and b) tell me how to build a patched
> driver?   I am not a complete neophyte with Linux (I frequently build apps
> from source and can debug build problems)  but I dont know where to start
> with drivers!
>
> Thanks,
> Will
>
>
> On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:
>
>> Lan Kidd, For the patch, I'm sure that Robert Nelson will include it on
>> the next release of the kernel, same for Koen !
>>
>> Terry Storm, well not really :) , the noise come when you remove your
>> finger, always at this time  when the pressure is not enough we got
>> some crazy x and y value ..
>>
>>
>> On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm  wrote:
>>
>>> Ditto.
>>>
>>> Regarding the fix which makes this work 99% of the time...
>>> Have you considered the noise could be on the power lines which power
>>> the touch screen?
>>> One could assume the power rails are meant to be between GND and VCC,
>>> however this may not be the case. It then assumes GND is 0 and VCC is Max.
>>> Since there are 4 AIN's used, it should be possible to read the voltages...
>>> Maybe do some sort of ratio calculation or something.
>>> Just a thought.
>>>
>>> Terry
>>>
>>>
>>> On Thursday, 9 January 2014 07:56:11 UTC+13, Ian Kidd wrote:

 I'm going to be the helpless little girl here and ask for a quick
 synopsis of how to apply the patch?  I'm not sure where the file is that
 gets this Diff, because I can't locate it in /lib/modules.

>>>  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard...@googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[André Prado]

Micka thank you so much for your work!
We can compile this driver with Linaro and load it dynamically right? Using
mobprobe

Or am i mistaken?

Cheers


On Mon, Jan 13, 2014 at 11:58 AM, Micka  wrote:

> I would love to create a patch for you, but i don't know how  I tried
> to commit the result, but I got :
>
> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
> # On branch v3.8.13-bone35
> # Changes not staged for commit:
> #   (use "git add ..." to update what will be committed)
> #   (use "git checkout -- ..." to discard changes in working
> directory)
> #
> # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
> #
> no changes added to commit (use "git add" and/or "git commit -a")
> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
> drivers/input/touchscreen/ti_am335x_tsc.c
> error: insufficient permission for adding an object to repository database
> .git/objects
>
> error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to insert into
> database
> error: unable to index file drivers/input/touchscreen/ti_am335x_tsc.c
> fatal: updating files failed
>
>
>
> On Sun, Jan 12, 2014 at 1:35 PM, Will Kostelecky <
> will.kostele...@gmail.com> wrote:
>
>> I have the same problem with the LCD7 on Archlinux and would really like
>> to get it fixed.   I can't find the above file on my installation and am
>> not sure where to look.   Or for that matter what to do with the patched
>> file if I were able to find it.   Can someone help with a) telling me where
>> to look for the right file to patch, and b) tell me how to build a patched
>> driver?   I am not a complete neophyte with Linux (I frequently build apps
>> from source and can debug build problems)  but I dont know where to start
>> with drivers!
>>
>> Thanks,
>> Will
>>
>>
>> On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:
>>
>>> Lan Kidd, For the patch, I'm sure that Robert Nelson will include it on
>>> the next release of the kernel, same for Koen !
>>>
>>> Terry Storm, well not really :) , the noise come when you remove your
>>> finger, always at this time  when the pressure is not enough we got
>>> some crazy x and y value ..
>>>
>>>
>>> On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm  wrote:
>>>
 Ditto.

 Regarding the fix which makes this work 99% of the time...
 Have you considered the noise could be on the power lines which power
 the touch screen?
 One could assume the power rails are meant to be between GND and VCC,
 however this may not be the case. It then assumes GND is 0 and VCC is Max.
 Since there are 4 AIN's used, it should be possible to read the voltages...
 Maybe do some sort of ratio calculation or something.
 Just a thought.

 Terry


 On Thursday, 9 January 2014 07:56:11 UTC+13, Ian Kidd wrote:
>
> I'm going to be the helpless little girl here and ask for a quick
> synopsis of how to apply the patch?  I'm not sure where the file is that
> gets this Diff, because I can't locate it in /lib/modules.
>
  --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the Google
 Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to beagleboard...@googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.

>>>
>>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Att
André

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

I don't think so ( I'm not an expert on that ) But It's "easy" with the
Kernel from Robert Nelson to build, modify the kernel, rebuild the kernel,
install the kernel in your sdcard  It's what i've done ... .

I hope that Robert Nelson will include this modification for the next
release of the Kernel .


On Mon, Jan 20, 2014 at 2:32 PM, André Prado  wrote:

> Micka thank you so much for your work!
> We can compile this driver with Linaro and load it dynamically right?
> Using mobprobe
>
> Or am i mistaken?
>
> Cheers
>
>
> On Mon, Jan 13, 2014 at 11:58 AM, Micka  wrote:
>
>> I would love to create a patch for you, but i don't know how  I tried
>> to commit the result, but I got :
>>
>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
>> # On branch v3.8.13-bone35
>> # Changes not staged for commit:
>> #   (use "git add ..." to update what will be committed)
>> #   (use "git checkout -- ..." to discard changes in working
>> directory)
>> #
>> # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
>> #
>> no changes added to commit (use "git add" and/or "git commit -a")
>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
>> drivers/input/touchscreen/ti_am335x_tsc.c
>> error: insufficient permission for adding an object to repository
>> database .git/objects
>>
>> error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to insert into
>> database
>> error: unable to index file drivers/input/touchscreen/ti_am335x_tsc.c
>> fatal: updating files failed
>>
>>
>>
>> On Sun, Jan 12, 2014 at 1:35 PM, Will Kostelecky <
>> will.kostele...@gmail.com> wrote:
>>
>>> I have the same problem with the LCD7 on Archlinux and would really like
>>> to get it fixed.   I can't find the above file on my installation and am
>>> not sure where to look.   Or for that matter what to do with the patched
>>> file if I were able to find it.   Can someone help with a) telling me where
>>> to look for the right file to patch, and b) tell me how to build a patched
>>> driver?   I am not a complete neophyte with Linux (I frequently build apps
>>> from source and can debug build problems)  but I dont know where to start
>>> with drivers!
>>>
>>> Thanks,
>>> Will
>>>
>>>
>>> On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:
>>>
 Lan Kidd, For the patch, I'm sure that Robert Nelson will include it on
 the next release of the kernel, same for Koen !

 Terry Storm, well not really :) , the noise come when you remove your
 finger, always at this time  when the pressure is not enough we got
 some crazy x and y value ..


 On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm wrote:

> Ditto.
>
> Regarding the fix which makes this work 99% of the time...
> Have you considered the noise could be on the power lines which power
> the touch screen?
> One could assume the power rails are meant to be between GND and VCC,
> however this may not be the case. It then assumes GND is 0 and VCC is Max.
> Since there are 4 AIN's used, it should be possible to read the 
> voltages...
> Maybe do some sort of ratio calculation or something.
> Just a thought.
>
> Terry
>
>
> On Thursday, 9 January 2014 07:56:11 UTC+13, Ian Kidd wrote:
>>
>> I'm going to be the helpless little girl here and ask for a quick
>> synopsis of how to apply the patch?  I'm not sure where the file is that
>> gets this Diff, because I can't locate it in /lib/modules.
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to beagleboard...@googlegroups.com.
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> Att
> André
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[André Prado]

Micka could you please give me the way? I need to get
https://github.com/beagleboard linux repo and compile with Linaro? Is that
all?





On Mon, Jan 20, 2014 at 12:08 PM, Micka  wrote:

> I don't think so ( I'm not an expert on that ) But It's "easy" with the
> Kernel from Robert Nelson to build, modify the kernel, rebuild the kernel,
> install the kernel in your sdcard  It's what i've done ... .
>
> I hope that Robert Nelson will include this modification for the next
> release of the Kernel .
>
>
> On Mon, Jan 20, 2014 at 2:32 PM, André Prado wrote:
>
>> Micka thank you so much for your work!
>> We can compile this driver with Linaro and load it dynamically right?
>> Using mobprobe
>>
>> Or am i mistaken?
>>
>> Cheers
>>
>>
>> On Mon, Jan 13, 2014 at 11:58 AM, Micka  wrote:
>>
>>> I would love to create a patch for you, but i don't know how  I
>>> tried to commit the result, but I got :
>>>
>>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
>>> # On branch v3.8.13-bone35
>>> # Changes not staged for commit:
>>> #   (use "git add ..." to update what will be committed)
>>> #   (use "git checkout -- ..." to discard changes in working
>>> directory)
>>> #
>>> # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
>>> #
>>> no changes added to commit (use "git add" and/or "git commit -a")
>>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
>>> drivers/input/touchscreen/ti_am335x_tsc.c
>>> error: insufficient permission for adding an object to repository
>>> database .git/objects
>>>
>>> error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to insert into
>>> database
>>> error: unable to index file drivers/input/touchscreen/ti_am335x_tsc.c
>>> fatal: updating files failed
>>>
>>>
>>>
>>> On Sun, Jan 12, 2014 at 1:35 PM, Will Kostelecky <
>>> will.kostele...@gmail.com> wrote:
>>>
 I have the same problem with the LCD7 on Archlinux and would really
 like to get it fixed.   I can't find the above file on my installation and
 am not sure where to look.   Or for that matter what to do with the patched
 file if I were able to find it.   Can someone help with a) telling me where
 to look for the right file to patch, and b) tell me how to build a patched
 driver?   I am not a complete neophyte with Linux (I frequently build apps
 from source and can debug build problems)  but I dont know where to start
 with drivers!

 Thanks,
 Will


 On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:

> Lan Kidd, For the patch, I'm sure that Robert Nelson will include it
> on the next release of the kernel, same for Koen !
>
> Terry Storm, well not really :) , the noise come when you remove your
> finger, always at this time  when the pressure is not enough we got
> some crazy x and y value ..
>
>
> On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm wrote:
>
>> Ditto.
>>
>> Regarding the fix which makes this work 99% of the time...
>> Have you considered the noise could be on the power lines which power
>> the touch screen?
>> One could assume the power rails are meant to be between GND and VCC,
>> however this may not be the case. It then assumes GND is 0 and VCC is 
>> Max.
>> Since there are 4 AIN's used, it should be possible to read the 
>> voltages...
>> Maybe do some sort of ratio calculation or something.
>> Just a thought.
>>
>> Terry
>>
>>
>> On Thursday, 9 January 2014 07:56:11 UTC+13, Ian Kidd wrote:
>>>
>>> I'm going to be the helpless little girl here and ask for a quick
>>> synopsis of how to apply the patch?  I'm not sure where the file is that
>>> gets this Diff, because I can't locate it in /lib/modules.
>>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google
>> Groups "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to beagleboard...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the Google
 Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.

>>>
>>>  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Will Kostelecky]

Micka:

I second the huge thanks from Andre for the work you have done on this to
date...would also support Andre's question about the way!   If you could
give us some pointers on what we need to do, or point us to a reference on
the web, it would be greatly appreciated (even more greatly than hugely)!

Cheers,
Will


On Tue, Jan 21, 2014 at 12:10 AM, André Prado wrote:

> Micka could you please give me the way? I need to get
> https://github.com/beagleboard linux repo and compile with Linaro? Is
> that all?
>
>
>
>
>
> On Mon, Jan 20, 2014 at 12:08 PM, Micka  wrote:
>
>> I don't think so ( I'm not an expert on that ) But It's "easy" with the
>> Kernel from Robert Nelson to build, modify the kernel, rebuild the kernel,
>> install the kernel in your sdcard  It's what i've done ... .
>>
>> I hope that Robert Nelson will include this modification for the next
>> release of the Kernel .
>>
>>
>> On Mon, Jan 20, 2014 at 2:32 PM, André Prado wrote:
>>
>>> Micka thank you so much for your work!
>>> We can compile this driver with Linaro and load it dynamically right?
>>> Using mobprobe
>>>
>>> Or am i mistaken?
>>>
>>> Cheers
>>>
>>>
>>> On Mon, Jan 13, 2014 at 11:58 AM, Micka  wrote:
>>>
 I would love to create a patch for you, but i don't know how  I
 tried to commit the result, but I got :

 beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
 # On branch v3.8.13-bone35
 # Changes not staged for commit:
 #   (use "git add ..." to update what will be committed)
 #   (use "git checkout -- ..." to discard changes in working
 directory)
 #
 # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
 #
 no changes added to commit (use "git add" and/or "git commit -a")
 beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
 drivers/input/touchscreen/ti_am335x_tsc.c
 error: insufficient permission for adding an object to repository
 database .git/objects

 error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to insert into
 database
 error: unable to index file drivers/input/touchscreen/ti_am335x_tsc.c
 fatal: updating files failed



 On Sun, Jan 12, 2014 at 1:35 PM, Will Kostelecky <
 will.kostele...@gmail.com> wrote:

> I have the same problem with the LCD7 on Archlinux and would really
> like to get it fixed.   I can't find the above file on my installation and
> am not sure where to look.   Or for that matter what to do with the 
> patched
> file if I were able to find it.   Can someone help with a) telling me 
> where
> to look for the right file to patch, and b) tell me how to build a patched
> driver?   I am not a complete neophyte with Linux (I frequently build apps
> from source and can debug build problems)  but I dont know where to start
> with drivers!
>
> Thanks,
> Will
>
>
> On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:
>
>> Lan Kidd, For the patch, I'm sure that Robert Nelson will include it
>> on the next release of the kernel, same for Koen !
>>
>> Terry Storm, well not really :) , the noise come when you remove your
>> finger, always at this time  when the pressure is not enough we got
>> some crazy x and y value ..
>>
>>
>> On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm wrote:
>>
>>> Ditto.
>>>
>>> Regarding the fix which makes this work 99% of the time...
>>> Have you considered the noise could be on the power lines which
>>> power the touch screen?
>>> One could assume the power rails are meant to be between GND and
>>> VCC, however this may not be the case. It then assumes GND is 0 and VCC 
>>> is
>>> Max. Since there are 4 AIN's used, it should be possible to read the
>>> voltages... Maybe do some sort of ratio calculation or something.
>>> Just a thought.
>>>
>>> Terry
>>>
>>>
>>> On Thursday, 9 January 2014 07:56:11 UTC+13, Ian Kidd wrote:

 I'm going to be the helpless little girl here and ask for a quick
 synopsis of how to apply the patch?  I'm not sure where the file is 
 that
 gets this Diff, because I can't locate it in /lib/modules.

>>>  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to beagleboard...@googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emai

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel

git clone git://github.com/RobertCNelson/linux-dev.git
cd linux-dev/
git checkout origin/am33x-v3.8 -b tmp
./build_kernel.sh

go to the file KERNEL/drivers/input/touchscreen/ti_am335x_tsc.c

edit the file by following the file that I previously sent .

save the file, go to the folder linux-dev, and rebuild the kernel :

./tools/rebuild something .sh

micka,



On Tue, Jan 21, 2014 at 7:00 AM, Will Kostelecky
wrote:

> Micka:
>
> I second the huge thanks from Andre for the work you have done on this to
> date...would also support Andre's question about the way!   If you could
> give us some pointers on what we need to do, or point us to a reference on
> the web, it would be greatly appreciated (even more greatly than hugely)!
>
> Cheers,
> Will
>
>
> On Tue, Jan 21, 2014 at 12:10 AM, André Prado wrote:
>
>> Micka could you please give me the way? I need to get
>> https://github.com/beagleboard linux repo and compile with Linaro? Is
>> that all?
>>
>>
>>
>>
>>
>> On Mon, Jan 20, 2014 at 12:08 PM, Micka  wrote:
>>
>>> I don't think so ( I'm not an expert on that ) But It's "easy" with the
>>> Kernel from Robert Nelson to build, modify the kernel, rebuild the kernel,
>>> install the kernel in your sdcard  It's what i've done ... .
>>>
>>> I hope that Robert Nelson will include this modification for the next
>>> release of the Kernel .
>>>
>>>
>>> On Mon, Jan 20, 2014 at 2:32 PM, André Prado wrote:
>>>
 Micka thank you so much for your work!
 We can compile this driver with Linaro and load it dynamically right?
 Using mobprobe

 Or am i mistaken?

 Cheers


 On Mon, Jan 13, 2014 at 11:58 AM, Micka  wrote:

> I would love to create a patch for you, but i don't know how  I
> tried to commit the result, but I got :
>
> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
> # On branch v3.8.13-bone35
> # Changes not staged for commit:
> #   (use "git add ..." to update what will be committed)
> #   (use "git checkout -- ..." to discard changes in working
> directory)
> #
> # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
> #
> no changes added to commit (use "git add" and/or "git commit -a")
> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
> drivers/input/touchscreen/ti_am335x_tsc.c
> error: insufficient permission for adding an object to repository
> database .git/objects
>
> error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to insert
> into database
> error: unable to index file drivers/input/touchscreen/ti_am335x_tsc.c
> fatal: updating files failed
>
>
>
> On Sun, Jan 12, 2014 at 1:35 PM, Will Kostelecky <
> will.kostele...@gmail.com> wrote:
>
>> I have the same problem with the LCD7 on Archlinux and would really
>> like to get it fixed.   I can't find the above file on my installation 
>> and
>> am not sure where to look.   Or for that matter what to do with the 
>> patched
>> file if I were able to find it.   Can someone help with a) telling me 
>> where
>> to look for the right file to patch, and b) tell me how to build a 
>> patched
>> driver?   I am not a complete neophyte with Linux (I frequently build 
>> apps
>> from source and can debug build problems)  but I dont know where to start
>> with drivers!
>>
>> Thanks,
>> Will
>>
>>
>> On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:
>>
>>> Lan Kidd, For the patch, I'm sure that Robert Nelson will include it
>>> on the next release of the kernel, same for Koen !
>>>
>>> Terry Storm, well not really :) , the noise come when you remove
>>> your finger, always at this time  when the pressure is not enough we
>>> got some crazy x and y value ..
>>>
>>>
>>> On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm wrote:
>>>
 Ditto.

 Regarding the fix which makes this work 99% of the time...
 Have you considered the noise could be on the power lines which
 power the touch screen?
 One could assume the power rails are meant to be between GND and
 VCC, however this may not be the case. It then assumes GND is 0 and 
 VCC is
 Max. Since there are 4 AIN's used, it should be possible to read the
 voltages... Maybe do some sort of ratio calculation or something.
 Just a thought.

 Terry


 On Thursday, 9 January 2014 07:56:11 UTC+13, Ian Kidd wrote:
>
> I'm going to be the helpless little girl here and ask for a quick
> synopsis of how to apply the patch?  I'm not sure where the file is 
> that
> gets this Diff, because I can't locate it in /lib/modules.
>
  --
>>>

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[André Prado]

Thank you so much, i will do it when i get home :)


On Tue, Jan 21, 2014 at 6:16 AM, Micka  wrote:

>
> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel
>
> git clone git://github.com/RobertCNelson/linux-dev.git
>  cd linux-dev/
>  git checkout origin/am33x-v3.8 -b tmp
>  ./build_kernel.sh
>
> go to the file KERNEL/drivers/input/touchscreen/ti_am335x_tsc.c
>
> edit the file by following the file that I previously sent .
>
> save the file, go to the folder linux-dev, and rebuild the kernel :
>
> ./tools/rebuild something .sh
>
> micka,
>
>
>
> On Tue, Jan 21, 2014 at 7:00 AM, Will Kostelecky <
> will.kostele...@gmail.com> wrote:
>
>> Micka:
>>
>> I second the huge thanks from Andre for the work you have done on this to
>> date...would also support Andre's question about the way!   If you could
>> give us some pointers on what we need to do, or point us to a reference on
>> the web, it would be greatly appreciated (even more greatly than hugely)!
>>
>> Cheers,
>> Will
>>
>>
>> On Tue, Jan 21, 2014 at 12:10 AM, André Prado wrote:
>>
>>> Micka could you please give me the way? I need to get
>>> https://github.com/beagleboard linux repo and compile with Linaro? Is
>>> that all?
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Jan 20, 2014 at 12:08 PM, Micka  wrote:
>>>
 I don't think so ( I'm not an expert on that ) But It's "easy" with the
 Kernel from Robert Nelson to build, modify the kernel, rebuild the kernel,
 install the kernel in your sdcard  It's what i've done ... .

 I hope that Robert Nelson will include this modification for the next
 release of the Kernel .


 On Mon, Jan 20, 2014 at 2:32 PM, André Prado wrote:

> Micka thank you so much for your work!
> We can compile this driver with Linaro and load it dynamically right?
> Using mobprobe
>
> Or am i mistaken?
>
> Cheers
>
>
> On Mon, Jan 13, 2014 at 11:58 AM, Micka  wrote:
>
>> I would love to create a patch for you, but i don't know how  I
>> tried to commit the result, but I got :
>>
>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
>> # On branch v3.8.13-bone35
>> # Changes not staged for commit:
>> #   (use "git add ..." to update what will be committed)
>> #   (use "git checkout -- ..." to discard changes in working
>> directory)
>> #
>> # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
>> #
>> no changes added to commit (use "git add" and/or "git commit -a")
>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
>> drivers/input/touchscreen/ti_am335x_tsc.c
>> error: insufficient permission for adding an object to repository
>> database .git/objects
>>
>> error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to insert
>> into database
>> error: unable to index file drivers/input/touchscreen/ti_am335x_tsc.c
>> fatal: updating files failed
>>
>>
>>
>> On Sun, Jan 12, 2014 at 1:35 PM, Will Kostelecky <
>> will.kostele...@gmail.com> wrote:
>>
>>> I have the same problem with the LCD7 on Archlinux and would really
>>> like to get it fixed.   I can't find the above file on my installation 
>>> and
>>> am not sure where to look.   Or for that matter what to do with the 
>>> patched
>>> file if I were able to find it.   Can someone help with a) telling me 
>>> where
>>> to look for the right file to patch, and b) tell me how to build a 
>>> patched
>>> driver?   I am not a complete neophyte with Linux (I frequently build 
>>> apps
>>> from source and can debug build problems)  but I dont know where to 
>>> start
>>> with drivers!
>>>
>>> Thanks,
>>> Will
>>>
>>>
>>> On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:
>>>
 Lan Kidd, For the patch, I'm sure that Robert Nelson will include
 it on the next release of the kernel, same for Koen !

 Terry Storm, well not really :) , the noise come when you remove
 your finger, always at this time  when the pressure is not enough 
 we
 got some crazy x and y value ..


 On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm wrote:

> Ditto.
>
> Regarding the fix which makes this work 99% of the time...
> Have you considered the noise could be on the power lines which
> power the touch screen?
> One could assume the power rails are meant to be between GND and
> VCC, however this may not be the case. It then assumes GND is 0 and 
> VCC is
> Max. Since there are 4 AIN's used, it should be possible to read the
> voltages... Maybe do some sort of ratio calculation or something.
> Just a thought.
>
> Terry
>
>
> On Thursday, 9 January 2014 07:56:

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Will Kostelecky]

Micka:

I have gotten to the point of rebuilding the kernel and have what may be a
dumb question before I press enter...

In tools I have a rebuild.sh and a rebuild_deb.sh.   Form your message I am
guessing that I run the latter?

Thanks,
Will


On Tue, Jan 21, 2014 at 3:08 PM, André Prado  wrote:

> Thank you so much, i will do it when i get home :)
>
>
> On Tue, Jan 21, 2014 at 6:16 AM, Micka  wrote:
>
>>
>> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel
>>
>> git clone git://github.com/RobertCNelson/linux-dev.git
>>  cd linux-dev/
>>  git checkout origin/am33x-v3.8 -b tmp
>>  ./build_kernel.sh
>>
>> go to the file KERNEL/drivers/input/touchscreen/ti_am335x_tsc.c
>>
>> edit the file by following the file that I previously sent .
>>
>> save the file, go to the folder linux-dev, and rebuild the kernel :
>>
>> ./tools/rebuild something .sh
>>
>> micka,
>>
>>
>>
>> On Tue, Jan 21, 2014 at 7:00 AM, Will Kostelecky <
>> will.kostele...@gmail.com> wrote:
>>
>>> Micka:
>>>
>>> I second the huge thanks from Andre for the work you have done on this
>>> to date...would also support Andre's question about the way!   If you could
>>> give us some pointers on what we need to do, or point us to a reference on
>>> the web, it would be greatly appreciated (even more greatly than hugely)!
>>>
>>> Cheers,
>>> Will
>>>
>>>
>>> On Tue, Jan 21, 2014 at 12:10 AM, André Prado wrote:
>>>
 Micka could you please give me the way? I need to get
 https://github.com/beagleboard linux repo and compile with Linaro? Is
 that all?





 On Mon, Jan 20, 2014 at 12:08 PM, Micka  wrote:

> I don't think so ( I'm not an expert on that ) But It's "easy" with
> the Kernel from Robert Nelson to build, modify the kernel, rebuild the
> kernel, install the kernel in your sdcard  It's what i've done ... .
>
> I hope that Robert Nelson will include this modification for the next
> release of the Kernel .
>
>
> On Mon, Jan 20, 2014 at 2:32 PM, André Prado 
> wrote:
>
>> Micka thank you so much for your work!
>> We can compile this driver with Linaro and load it dynamically right?
>> Using mobprobe
>>
>> Or am i mistaken?
>>
>> Cheers
>>
>>
>> On Mon, Jan 13, 2014 at 11:58 AM, Micka wrote:
>>
>>> I would love to create a patch for you, but i don't know how  I
>>> tried to commit the result, but I got :
>>>
>>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
>>> # On branch v3.8.13-bone35
>>> # Changes not staged for commit:
>>> #   (use "git add ..." to update what will be committed)
>>> #   (use "git checkout -- ..." to discard changes in working
>>> directory)
>>> #
>>> # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
>>> #
>>> no changes added to commit (use "git add" and/or "git commit -a")
>>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
>>> drivers/input/touchscreen/ti_am335x_tsc.c
>>> error: insufficient permission for adding an object to repository
>>> database .git/objects
>>>
>>> error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to insert
>>> into database
>>> error: unable to index file drivers/input/touchscreen/ti_am335x_tsc.c
>>> fatal: updating files failed
>>>
>>>
>>>
>>> On Sun, Jan 12, 2014 at 1:35 PM, Will Kostelecky <
>>> will.kostele...@gmail.com> wrote:
>>>
 I have the same problem with the LCD7 on Archlinux and would really
 like to get it fixed.   I can't find the above file on my installation 
 and
 am not sure where to look.   Or for that matter what to do with the 
 patched
 file if I were able to find it.   Can someone help with a) telling me 
 where
 to look for the right file to patch, and b) tell me how to build a 
 patched
 driver?   I am not a complete neophyte with Linux (I frequently build 
 apps
 from source and can debug build problems)  but I dont know where to 
 start
 with drivers!

 Thanks,
 Will


 On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:

> Lan Kidd, For the patch, I'm sure that Robert Nelson will include
> it on the next release of the kernel, same for Koen !
>
> Terry Storm, well not really :) , the noise come when you remove
> your finger, always at this time  when the pressure is not enough 
> we
> got some crazy x and y value ..
>
>
> On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm 
> wrote:
>
>> Ditto.
>>
>> Regarding the fix which makes this work 99% of the time...
>> Have you considered the noise could be on the power lines which
>> power the 

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

I never used rebuild_deb.sh . I don't know what it is for .


On Wed, Jan 22, 2014 at 9:30 AM, Will Kostelecky
wrote:

> Micka:
>
> I have gotten to the point of rebuilding the kernel and have what may be a
> dumb question before I press enter...
>
> In tools I have a rebuild.sh and a rebuild_deb.sh.   Form your message I
> am guessing that I run the latter?
>
> Thanks,
> Will
>
>
> On Tue, Jan 21, 2014 at 3:08 PM, André Prado wrote:
>
>> Thank you so much, i will do it when i get home :)
>>
>>
>> On Tue, Jan 21, 2014 at 6:16 AM, Micka  wrote:
>>
>>>
>>> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel
>>>
>>> git clone git://github.com/RobertCNelson/linux-dev.git
>>>  cd linux-dev/
>>>  git checkout origin/am33x-v3.8 -b tmp
>>>  ./build_kernel.sh
>>>
>>> go to the file KERNEL/drivers/input/touchscreen/ti_am335x_tsc.c
>>>
>>> edit the file by following the file that I previously sent .
>>>
>>> save the file, go to the folder linux-dev, and rebuild the kernel :
>>>
>>> ./tools/rebuild something .sh
>>>
>>> micka,
>>>
>>>
>>>
>>> On Tue, Jan 21, 2014 at 7:00 AM, Will Kostelecky <
>>> will.kostele...@gmail.com> wrote:
>>>
 Micka:

 I second the huge thanks from Andre for the work you have done on this
 to date...would also support Andre's question about the way!   If you could
 give us some pointers on what we need to do, or point us to a reference on
 the web, it would be greatly appreciated (even more greatly than hugely)!

 Cheers,
 Will


 On Tue, Jan 21, 2014 at 12:10 AM, André Prado 
 wrote:

> Micka could you please give me the way? I need to get
> https://github.com/beagleboard linux repo and compile with Linaro? Is
> that all?
>
>
>
>
>
> On Mon, Jan 20, 2014 at 12:08 PM, Micka  wrote:
>
>> I don't think so ( I'm not an expert on that ) But It's "easy" with
>> the Kernel from Robert Nelson to build, modify the kernel, rebuild the
>> kernel, install the kernel in your sdcard  It's what i've done ... .
>>
>> I hope that Robert Nelson will include this modification for the next
>> release of the Kernel .
>>
>>
>> On Mon, Jan 20, 2014 at 2:32 PM, André Prado 
>> wrote:
>>
>>> Micka thank you so much for your work!
>>> We can compile this driver with Linaro and load it dynamically
>>> right? Using mobprobe
>>>
>>> Or am i mistaken?
>>>
>>> Cheers
>>>
>>>
>>> On Mon, Jan 13, 2014 at 11:58 AM, Micka wrote:
>>>
 I would love to create a patch for you, but i don't know how  I
 tried to commit the result, but I got :

 beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git commit
 # On branch v3.8.13-bone35
 # Changes not staged for commit:
 #   (use "git add ..." to update what will be committed)
 #   (use "git checkout -- ..." to discard changes in working
 directory)
 #
 # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
 #
 no changes added to commit (use "git add" and/or "git commit -a")
 beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git
 commit drivers/input/touchscreen/ti_am335x_tsc.c
 error: insufficient permission for adding an object to repository
 database .git/objects

 error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to insert
 into database
 error: unable to index file
 drivers/input/touchscreen/ti_am335x_tsc.c
 fatal: updating files failed



 On Sun, Jan 12, 2014 at 1:35 PM, Will Kostelecky <
 will.kostele...@gmail.com> wrote:

> I have the same problem with the LCD7 on Archlinux and would
> really like to get it fixed.   I can't find the above file on my
> installation and am not sure where to look.   Or for that matter what 
> to do
> with the patched file if I were able to find it.   Can someone help 
> with a)
> telling me where to look for the right file to patch, and b) tell me 
> how to
> build a patched driver?   I am not a complete neophyte with Linux (I
> frequently build apps from source and can debug build problems)  but 
> I dont
> know where to start with drivers!
>
> Thanks,
> Will
>
>
> On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:
>
>> Lan Kidd, For the patch, I'm sure that Robert Nelson will include
>> it on the next release of the kernel, same for Koen !
>>
>> Terry Storm, well not really :) , the noise come when you remove
>> your finger, always at this time  when the pressure is not 
>> enough we
>> got some crazy x and y value ..
>>
>>
>

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[longdirtyanimalf]

Hello Will,

I am experiencing the same problems !!

I am compiling a new kernel for ArchLinux with the proposed 
jitter-patch ... the lecacy-one (3.8.13) ... I will let you know if I am 
successfull !!

Greetings, Alfred.


Op zondag 12 januari 2014 13:35:38 UTC+1 schreef Will Kostelecky:

> I have the same problem with the LCD7 on Archlinux and would really like 
> to get it fixed.   I can't find the above file on my installation and am 
> not sure where to look.   Or for that matter what to do with the patched 
> file if I were able to find it.   Can someone help with a) telling me where 
> to look for the right file to patch, and b) tell me how to build a patched 
> driver?   I am not a complete neophyte with Linux (I frequently build apps 
> from source and can debug build problems)  but I dont know where to start 
> with drivers!
>
> Thanks,
> Will
>
> On Thursday, 9 January 2014 07:58:47 UTC, Mickae1 wrote:
>>
>> Lan Kidd, For the patch, I'm sure that Robert Nelson will include it on 
>> the next release of the kernel, same for Koen !
>>
>> Terry Storm, well not really :) , the noise come when you remove your 
>> finger, always at this time  when the pressure is not enough we got 
>> some crazy x and y value ..
>>
>>
>> On Thu, Jan 9, 2014 at 6:54 AM, Terry Storm  wrote:
>>
>>> Ditto.
>>>
>>> Regarding the fix which makes this work 99% of the time...
>>> Have you considered the noise could be on the power lines which power 
>>> the touch screen?
>>> One could assume the power rails are meant to be between GND and VCC, 
>>> however this may not be the case. It then assumes GND is 0 and VCC is Max. 
>>> Since there are 4 AIN's used, it should be possible to read the voltages... 
>>> Maybe do some sort of ratio calculation or something.
>>> Just a thought.
>>>
>>> Terry
>>>
>>>
>>> On Thursday, 9 January 2014 07:56:11 UTC+13, Ian Kidd wrote:

 I'm going to be the helpless little girl here and ask for a quick 
 synopsis of how to apply the patch?  I'm not sure where the file is that 
 gets this Diff, because I can't locate it in /lib/modules.

>>>  -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to beagleboard...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Will Kostelecky]

Everything went well up to the point of actually installing the patched and
rebuilt kernel!   I run from an SD card so had to point the install script
to it.   It installed ok on the first partition but blew up on the
second.   I have not had a chance to dig into why yet.   I am thinking of
trying the upgrade on the internal drive and see if that, being what is
expected by default, works better?


On Wed, Jan 22, 2014 at 8:39 AM, Micka  wrote:

> I never used rebuild_deb.sh . I don't know what it is for .
>
>
> On Wed, Jan 22, 2014 at 9:30 AM, Will Kostelecky <
> will.kostele...@gmail.com> wrote:
>
>> Micka:
>>
>> I have gotten to the point of rebuilding the kernel and have what may be
>> a dumb question before I press enter...
>>
>> In tools I have a rebuild.sh and a rebuild_deb.sh.   Form your message I
>> am guessing that I run the latter?
>>
>> Thanks,
>> Will
>>
>>
>> On Tue, Jan 21, 2014 at 3:08 PM, André Prado wrote:
>>
>>> Thank you so much, i will do it when i get home :)
>>>
>>>
>>> On Tue, Jan 21, 2014 at 6:16 AM, Micka  wrote:
>>>

 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel

 git clone git://github.com/RobertCNelson/linux-dev.git
  cd linux-dev/
  git checkout origin/am33x-v3.8 -b tmp
  ./build_kernel.sh

 go to the file KERNEL/drivers/input/touchscreen/ti_am335x_tsc.c

 edit the file by following the file that I previously sent .

 save the file, go to the folder linux-dev, and rebuild the kernel :

 ./tools/rebuild something .sh

 micka,



 On Tue, Jan 21, 2014 at 7:00 AM, Will Kostelecky <
 will.kostele...@gmail.com> wrote:

> Micka:
>
> I second the huge thanks from Andre for the work you have done on this
> to date...would also support Andre's question about the way!   If you 
> could
> give us some pointers on what we need to do, or point us to a reference on
> the web, it would be greatly appreciated (even more greatly than hugely)!
>
> Cheers,
> Will
>
>
> On Tue, Jan 21, 2014 at 12:10 AM, André Prado 
> wrote:
>
>> Micka could you please give me the way? I need to get
>> https://github.com/beagleboard linux repo and compile with Linaro?
>> Is that all?
>>
>>
>>
>>
>>
>> On Mon, Jan 20, 2014 at 12:08 PM, Micka wrote:
>>
>>> I don't think so ( I'm not an expert on that ) But It's "easy" with
>>> the Kernel from Robert Nelson to build, modify the kernel, rebuild the
>>> kernel, install the kernel in your sdcard  It's what i've done ... .
>>>
>>> I hope that Robert Nelson will include this modification for the
>>> next release of the Kernel .
>>>
>>>
>>> On Mon, Jan 20, 2014 at 2:32 PM, André Prado >> > wrote:
>>>
 Micka thank you so much for your work!
 We can compile this driver with Linaro and load it dynamically
 right? Using mobprobe

 Or am i mistaken?

 Cheers


 On Mon, Jan 13, 2014 at 11:58 AM, Micka wrote:

> I would love to create a patch for you, but i don't know how 
> I tried to commit the result, but I got :
>
> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git
> commit
> # On branch v3.8.13-bone35
> # Changes not staged for commit:
> #   (use "git add ..." to update what will be committed)
> #   (use "git checkout -- ..." to discard changes in working
> directory)
> #
> # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
> #
> no changes added to commit (use "git add" and/or "git commit -a")
> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git
> commit drivers/input/touchscreen/ti_am335x_tsc.c
> error: insufficient permission for adding an object to repository
> database .git/objects
>
> error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to insert
> into database
> error: unable to index file
> drivers/input/touchscreen/ti_am335x_tsc.c
> fatal: updating files failed
>
>
>
> On Sun, Jan 12, 2014 at 1:35 PM, Will Kostelecky <
> will.kostele...@gmail.com> wrote:
>
>> I have the same problem with the LCD7 on Archlinux and would
>> really like to get it fixed.   I can't find the above file on my
>> installation and am not sure where to look.   Or for that matter 
>> what to do
>> with the patched file if I were able to find it.   Can someone help 
>> with a)
>> telling me where to look for the right file to patch, and b) tell me 
>> how to
>> build a patched driver?   I am not a complete neophyte with Linux (I
>> frequently build apps from source and can de

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

Well,

First, thx to Robert Nelson, the patch for the touchscreen fix has been
implemented  :

https://github.com/RobertCNelson/linux-dev/commit/20c9c32e3443826d79ea01e17cbd2d6fa2c616ae

Which means, that now, you don't need to implement it yourself :p , you
just need to build the kernel and install it in your sdcard.

Which means that soon, the fix will be implemented to each release of
ubuntu/debian from Robert Nelson !

Also Will Kostelecky, the script to install the kernel, only work for a
Robert Nelson image ( ubuntu/debian ) .


Micka,





On Thu, Jan 23, 2014 at 8:45 AM, Will Kostelecky
wrote:

> Everything went well up to the point of actually installing the patched
> and rebuilt kernel!   I run from an SD card so had to point the install
> script to it.   It installed ok on the first partition but blew up on the
> second.   I have not had a chance to dig into why yet.   I am thinking of
> trying the upgrade on the internal drive and see if that, being what is
> expected by default, works better?
>
>
>
> On Wed, Jan 22, 2014 at 8:39 AM, Micka  wrote:
>
>> I never used rebuild_deb.sh . I don't know what it is for .
>>
>>
>> On Wed, Jan 22, 2014 at 9:30 AM, Will Kostelecky <
>> will.kostele...@gmail.com> wrote:
>>
>>> Micka:
>>>
>>> I have gotten to the point of rebuilding the kernel and have what may be
>>> a dumb question before I press enter...
>>>
>>> In tools I have a rebuild.sh and a rebuild_deb.sh.   Form your message I
>>> am guessing that I run the latter?
>>>
>>> Thanks,
>>> Will
>>>
>>>
>>> On Tue, Jan 21, 2014 at 3:08 PM, André Prado wrote:
>>>
 Thank you so much, i will do it when i get home :)


 On Tue, Jan 21, 2014 at 6:16 AM, Micka  wrote:

>
> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel
>
> git clone git://github.com/RobertCNelson/linux-dev.git
>  cd linux-dev/
>  git checkout origin/am33x-v3.8 -b tmp
>  ./build_kernel.sh
>
> go to the file KERNEL/drivers/input/touchscreen/ti_am335x_tsc.c
>
> edit the file by following the file that I previously sent .
>
> save the file, go to the folder linux-dev, and rebuild the kernel :
>
> ./tools/rebuild something .sh
>
> micka,
>
>
>
> On Tue, Jan 21, 2014 at 7:00 AM, Will Kostelecky <
> will.kostele...@gmail.com> wrote:
>
>> Micka:
>>
>> I second the huge thanks from Andre for the work you have done on
>> this to date...would also support Andre's question about the way!   If 
>> you
>> could give us some pointers on what we need to do, or point us to a
>> reference on the web, it would be greatly appreciated (even more greatly
>> than hugely)!
>>
>> Cheers,
>> Will
>>
>>
>> On Tue, Jan 21, 2014 at 12:10 AM, André Prado > > wrote:
>>
>>> Micka could you please give me the way? I need to get
>>> https://github.com/beagleboard linux repo and compile with Linaro?
>>> Is that all?
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Jan 20, 2014 at 12:08 PM, Micka wrote:
>>>
 I don't think so ( I'm not an expert on that ) But It's "easy" with
 the Kernel from Robert Nelson to build, modify the kernel, rebuild the
 kernel, install the kernel in your sdcard  It's what i've done ... 
 .

 I hope that Robert Nelson will include this modification for the
 next release of the Kernel .


 On Mon, Jan 20, 2014 at 2:32 PM, André Prado <
 andreprad...@gmail.com> wrote:

> Micka thank you so much for your work!
> We can compile this driver with Linaro and load it dynamically
> right? Using mobprobe
>
> Or am i mistaken?
>
> Cheers
>
>
> On Mon, Jan 13, 2014 at 11:58 AM, Micka wrote:
>
>> I would love to create a patch for you, but i don't know how 
>> I tried to commit the result, but I got :
>>
>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git
>> commit
>> # On branch v3.8.13-bone35
>> # Changes not staged for commit:
>> #   (use "git add ..." to update what will be committed)
>> #   (use "git checkout -- ..." to discard changes in
>> working directory)
>> #
>> # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
>> #
>> no changes added to commit (use "git add" and/or "git commit -a")
>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git
>> commit drivers/input/touchscreen/ti_am335x_tsc.c
>> error: insufficient permission for adding an object to repository
>> database .git/objects
>>
>> error: drivers/input/touchscreen/ti_am335x_tsc.c: failed to
>> insert into database
>> error: unable to index file
>> drivers/input/tou

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Will Kostelecky]

:-(


On Thu, Jan 23, 2014 at 8:36 AM, Micka  wrote:

> Well,
>
> First, thx to Robert Nelson, the patch for the touchscreen fix has been
> implemented  :
>
>
> https://github.com/RobertCNelson/linux-dev/commit/20c9c32e3443826d79ea01e17cbd2d6fa2c616ae
>
> Which means, that now, you don't need to implement it yourself :p , you
> just need to build the kernel and install it in your sdcard.
>
> Which means that soon, the fix will be implemented to each release of
> ubuntu/debian from Robert Nelson !
>
> Also Will Kostelecky, the script to install the kernel, only work for a
> Robert Nelson image ( ubuntu/debian ) .
>
>
> Micka,
>
>
>
>
>
> On Thu, Jan 23, 2014 at 8:45 AM, Will Kostelecky <
> will.kostele...@gmail.com> wrote:
>
>> Everything went well up to the point of actually installing the patched
>> and rebuilt kernel!   I run from an SD card so had to point the install
>> script to it.   It installed ok on the first partition but blew up on the
>> second.   I have not had a chance to dig into why yet.   I am thinking of
>> trying the upgrade on the internal drive and see if that, being what is
>> expected by default, works better?
>>
>>
>>
>> On Wed, Jan 22, 2014 at 8:39 AM, Micka  wrote:
>>
>>> I never used rebuild_deb.sh . I don't know what it is for .
>>>
>>>
>>> On Wed, Jan 22, 2014 at 9:30 AM, Will Kostelecky <
>>> will.kostele...@gmail.com> wrote:
>>>
 Micka:

 I have gotten to the point of rebuilding the kernel and have what may
 be a dumb question before I press enter...

 In tools I have a rebuild.sh and a rebuild_deb.sh.   Form your message
 I am guessing that I run the latter?

 Thanks,
 Will


 On Tue, Jan 21, 2014 at 3:08 PM, André Prado wrote:

> Thank you so much, i will do it when i get home :)
>
>
> On Tue, Jan 21, 2014 at 6:16 AM, Micka  wrote:
>
>>
>> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel
>>
>> git clone git://github.com/RobertCNelson/linux-dev.git
>>  cd linux-dev/
>>  git checkout origin/am33x-v3.8 -b tmp
>>  ./build_kernel.sh
>>
>> go to the file KERNEL/drivers/input/touchscreen/ti_am335x_tsc.c
>>
>> edit the file by following the file that I previously sent .
>>
>> save the file, go to the folder linux-dev, and rebuild the kernel :
>>
>> ./tools/rebuild something .sh
>>
>> micka,
>>
>>
>>
>> On Tue, Jan 21, 2014 at 7:00 AM, Will Kostelecky <
>> will.kostele...@gmail.com> wrote:
>>
>>> Micka:
>>>
>>> I second the huge thanks from Andre for the work you have done on
>>> this to date...would also support Andre's question about the way!   If 
>>> you
>>> could give us some pointers on what we need to do, or point us to a
>>> reference on the web, it would be greatly appreciated (even more greatly
>>> than hugely)!
>>>
>>> Cheers,
>>> Will
>>>
>>>
>>> On Tue, Jan 21, 2014 at 12:10 AM, André Prado <
>>> andreprad...@gmail.com> wrote:
>>>
 Micka could you please give me the way? I need to get
 https://github.com/beagleboard linux repo and compile with Linaro?
 Is that all?





 On Mon, Jan 20, 2014 at 12:08 PM, Micka wrote:

> I don't think so ( I'm not an expert on that ) But It's "easy"
> with the Kernel from Robert Nelson to build, modify the kernel, 
> rebuild the
> kernel, install the kernel in your sdcard  It's what i've done 
> ... .
>
> I hope that Robert Nelson will include this modification for the
> next release of the Kernel .
>
>
> On Mon, Jan 20, 2014 at 2:32 PM, André Prado <
> andreprad...@gmail.com> wrote:
>
>> Micka thank you so much for your work!
>> We can compile this driver with Linaro and load it dynamically
>> right? Using mobprobe
>>
>> Or am i mistaken?
>>
>> Cheers
>>
>>
>> On Mon, Jan 13, 2014 at 11:58 AM, Micka wrote:
>>
>>> I would love to create a patch for you, but i don't know how
>>>  I tried to commit the result, but I got :
>>>
>>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git
>>> commit
>>> # On branch v3.8.13-bone35
>>> # Changes not staged for commit:
>>> #   (use "git add ..." to update what will be committed)
>>> #   (use "git checkout -- ..." to discard changes in
>>> working directory)
>>> #
>>> # modified:   drivers/input/touchscreen/ti_am335x_tsc.c
>>> #
>>> no changes added to commit (use "git add" and/or "git commit -a")
>>> beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git
>>> commit drivers/input/touchscreen/ti_am335x_tsc.c
>>>

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

What ? You have an angstrom image ? You should change  Angstrom it's
over  go to the Ubuntu/Debian image !


On Thu, Jan 23, 2014 at 10:39 AM, Will Kostelecky  wrote:

> :-(
>
>
> On Thu, Jan 23, 2014 at 8:36 AM, Micka  wrote:
>
>> Well,
>>
>> First, thx to Robert Nelson, the patch for the touchscreen fix has been
>> implemented  :
>>
>>
>> https://github.com/RobertCNelson/linux-dev/commit/20c9c32e3443826d79ea01e17cbd2d6fa2c616ae
>>
>> Which means, that now, you don't need to implement it yourself :p , you
>> just need to build the kernel and install it in your sdcard.
>>
>> Which means that soon, the fix will be implemented to each release of
>> ubuntu/debian from Robert Nelson !
>>
>> Also Will Kostelecky, the script to install the kernel, only work for a
>> Robert Nelson image ( ubuntu/debian ) .
>>
>>
>> Micka,
>>
>>
>>
>>
>>
>> On Thu, Jan 23, 2014 at 8:45 AM, Will Kostelecky <
>> will.kostele...@gmail.com> wrote:
>>
>>> Everything went well up to the point of actually installing the patched
>>> and rebuilt kernel!   I run from an SD card so had to point the install
>>> script to it.   It installed ok on the first partition but blew up on the
>>> second.   I have not had a chance to dig into why yet.   I am thinking of
>>> trying the upgrade on the internal drive and see if that, being what is
>>> expected by default, works better?
>>>
>>>
>>>
>>> On Wed, Jan 22, 2014 at 8:39 AM, Micka  wrote:
>>>
 I never used rebuild_deb.sh . I don't know what it is for .


 On Wed, Jan 22, 2014 at 9:30 AM, Will Kostelecky <
 will.kostele...@gmail.com> wrote:

> Micka:
>
> I have gotten to the point of rebuilding the kernel and have what may
> be a dumb question before I press enter...
>
> In tools I have a rebuild.sh and a rebuild_deb.sh.   Form your message
> I am guessing that I run the latter?
>
> Thanks,
> Will
>
>
> On Tue, Jan 21, 2014 at 3:08 PM, André Prado 
> wrote:
>
>> Thank you so much, i will do it when i get home :)
>>
>>
>> On Tue, Jan 21, 2014 at 6:16 AM, Micka  wrote:
>>
>>>
>>> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel
>>>
>>> git clone git://github.com/RobertCNelson/linux-dev.git
>>>  cd linux-dev/
>>>  git checkout origin/am33x-v3.8 -b tmp
>>>  ./build_kernel.sh
>>>
>>> go to the file KERNEL/drivers/input/touchscreen/ti_am335x_tsc.c
>>>
>>> edit the file by following the file that I previously sent .
>>>
>>> save the file, go to the folder linux-dev, and rebuild the kernel :
>>>
>>> ./tools/rebuild something .sh
>>>
>>> micka,
>>>
>>>
>>>
>>> On Tue, Jan 21, 2014 at 7:00 AM, Will Kostelecky <
>>> will.kostele...@gmail.com> wrote:
>>>
 Micka:

 I second the huge thanks from Andre for the work you have done on
 this to date...would also support Andre's question about the way!   If 
 you
 could give us some pointers on what we need to do, or point us to a
 reference on the web, it would be greatly appreciated (even more 
 greatly
 than hugely)!

 Cheers,
 Will


 On Tue, Jan 21, 2014 at 12:10 AM, André Prado <
 andreprad...@gmail.com> wrote:

> Micka could you please give me the way? I need to get
> https://github.com/beagleboard linux repo and compile with
> Linaro? Is that all?
>
>
>
>
>
> On Mon, Jan 20, 2014 at 12:08 PM, Micka wrote:
>
>> I don't think so ( I'm not an expert on that ) But It's "easy"
>> with the Kernel from Robert Nelson to build, modify the kernel, 
>> rebuild the
>> kernel, install the kernel in your sdcard  It's what i've done 
>> ... .
>>
>> I hope that Robert Nelson will include this modification for the
>> next release of the Kernel .
>>
>>
>> On Mon, Jan 20, 2014 at 2:32 PM, André Prado <
>> andreprad...@gmail.com> wrote:
>>
>>> Micka thank you so much for your work!
>>> We can compile this driver with Linaro and load it dynamically
>>> right? Using mobprobe
>>>
>>> Or am i mistaken?
>>>
>>> Cheers
>>>
>>>
>>> On Mon, Jan 13, 2014 at 11:58 AM, Micka 
>>> wrote:
>>>
 I would love to create a patch for you, but i don't know how
  I tried to commit the result, but I got :

 beaglekernel@beaglekernel-VirtualBox:~/linux-dev/KERNEL$ git
 commit
 # On branch v3.8.13-bone35
 # Changes not staged for commit:
 #   (use "git add ..." to update what will be committed)
 #   (use "git checkout -- ..." to discard

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Will Kostelecky]

Arch.   Much faster than Debian for my application.   I must admit messing
with the kernel might be above my level of competency.  I am but an app
developer!


On Thu, Jan 23, 2014 at 9:41 AM, Micka  wrote:

> What ? You have an angstrom image ? You should change  Angstrom it's
> over  go to the Ubuntu/Debian image !
>
>
> On Thu, Jan 23, 2014 at 10:39 AM, Will Kostelecky <
> will.kostele...@gmail.com> wrote:
>
>> :-(
>>
>>
>> On Thu, Jan 23, 2014 at 8:36 AM, Micka  wrote:
>>
>>> Well,
>>>
>>> First, thx to Robert Nelson, the patch for the touchscreen fix has been
>>> implemented  :
>>>
>>>
>>> https://github.com/RobertCNelson/linux-dev/commit/20c9c32e3443826d79ea01e17cbd2d6fa2c616ae
>>>
>>> Which means, that now, you don't need to implement it yourself :p , you
>>> just need to build the kernel and install it in your sdcard.
>>>
>>> Which means that soon, the fix will be implemented to each release of
>>> ubuntu/debian from Robert Nelson !
>>>
>>> Also Will Kostelecky, the script to install the kernel, only work for a
>>> Robert Nelson image ( ubuntu/debian ) .
>>>
>>>
>>> Micka,
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Jan 23, 2014 at 8:45 AM, Will Kostelecky <
>>> will.kostele...@gmail.com> wrote:
>>>
 Everything went well up to the point of actually installing the patched
 and rebuilt kernel!   I run from an SD card so had to point the install
 script to it.   It installed ok on the first partition but blew up on the
 second.   I have not had a chance to dig into why yet.   I am thinking of
 trying the upgrade on the internal drive and see if that, being what is
 expected by default, works better?



 On Wed, Jan 22, 2014 at 8:39 AM, Micka  wrote:

> I never used rebuild_deb.sh . I don't know what it is for .
>
>
> On Wed, Jan 22, 2014 at 9:30 AM, Will Kostelecky <
> will.kostele...@gmail.com> wrote:
>
>> Micka:
>>
>> I have gotten to the point of rebuilding the kernel and have what may
>> be a dumb question before I press enter...
>>
>> In tools I have a rebuild.sh and a rebuild_deb.sh.   Form your
>> message I am guessing that I run the latter?
>>
>> Thanks,
>> Will
>>
>>
>> On Tue, Jan 21, 2014 at 3:08 PM, André Prado 
>> wrote:
>>
>>> Thank you so much, i will do it when i get home :)
>>>
>>>
>>> On Tue, Jan 21, 2014 at 6:16 AM, Micka wrote:
>>>

 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel

 git clone git://github.com/RobertCNelson/linux-dev.git
  cd linux-dev/
  git checkout origin/am33x-v3.8 -b tmp
  ./build_kernel.sh

 go to the file KERNEL/drivers/input/touchscreen/ti_am335x_tsc.c

 edit the file by following the file that I previously sent .

 save the file, go to the folder linux-dev, and rebuild the kernel :

 ./tools/rebuild something .sh

 micka,



 On Tue, Jan 21, 2014 at 7:00 AM, Will Kostelecky <
 will.kostele...@gmail.com> wrote:

> Micka:
>
> I second the huge thanks from Andre for the work you have done on
> this to date...would also support Andre's question about the way!   
> If you
> could give us some pointers on what we need to do, or point us to a
> reference on the web, it would be greatly appreciated (even more 
> greatly
> than hugely)!
>
> Cheers,
> Will
>
>
> On Tue, Jan 21, 2014 at 12:10 AM, André Prado <
> andreprad...@gmail.com> wrote:
>
>> Micka could you please give me the way? I need to get
>> https://github.com/beagleboard linux repo and compile with
>> Linaro? Is that all?
>>
>>
>>
>>
>>
>> On Mon, Jan 20, 2014 at 12:08 PM, Micka wrote:
>>
>>> I don't think so ( I'm not an expert on that ) But It's "easy"
>>> with the Kernel from Robert Nelson to build, modify the kernel, 
>>> rebuild the
>>> kernel, install the kernel in your sdcard  It's what i've done 
>>> ... .
>>>
>>> I hope that Robert Nelson will include this modification for the
>>> next release of the Kernel .
>>>
>>>
>>> On Mon, Jan 20, 2014 at 2:32 PM, André Prado <
>>> andreprad...@gmail.com> wrote:
>>>
 Micka thank you so much for your work!
 We can compile this driver with Linaro and load it dynamically
 right? Using mobprobe

 Or am i mistaken?

 Cheers


 On Mon, Jan 13, 2014 at 11:58 AM, Micka 
 wrote:

> I would love to create a patch for you, but i d

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Robert Nelson]

On Mon, Jan 27, 2014 at 4:36 AM, Terry Storm  wrote:
> Great news
>
> Can someone please link me to the latest Debian/Ubuntu image which features
> this fix? Is there is pre-made image available, or do I need to build it?
> Ditto for Arch Linux, would love to try that one out too with the fix for
> that.


https://groups.google.com/d/msg/beagleboard/w9PfhGkByQU/bE_BNG4vgHgJ

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Terry Storm]

Brilliant

Thank you Robert, and thank you Micka for the patch.

Just ran it up, booted from SD card and I cant fault the touch in the few 
minutes I have played with it.
Great news, thank you both.

Will continue to test.

Terry

On Tuesday, 28 January 2014 02:45:40 UTC+13, RobertCNelson wrote:
>
> On Mon, Jan 27, 2014 at 4:36 AM, Terry Storm 
> > 
> wrote: 
> > Great news 
> > 
> > Can someone please link me to the latest Debian/Ubuntu image which 
> features 
> > this fix? Is there is pre-made image available, or do I need to build 
> it? 
> > Ditto for Arch Linux, would love to try that one out too with the fix 
> for 
> > that. 
>
>  
> https://groups.google.com/d/msg/beagleboard/w9PfhGkByQU/bE_BNG4vgHgJ 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

Well, It's good that it works in other device :)

Micka,


On Mon, Jan 27, 2014 at 9:32 PM, Terry Storm  wrote:

> Brilliant
>
> Thank you Robert, and thank you Micka for the patch.
>
> Just ran it up, booted from SD card and I cant fault the touch in the few
> minutes I have played with it.
> Great news, thank you both.
>
> Will continue to test.
>
> Terry
>
> On Tuesday, 28 January 2014 02:45:40 UTC+13, RobertCNelson wrote:
>
>> On Mon, Jan 27, 2014 at 4:36 AM, Terry Storm 
>> wrote:
>> > Great news
>> >
>> > Can someone please link me to the latest Debian/Ubuntu image which
>> features
>> > this fix? Is there is pre-made image available, or do I need to build
>> it?
>> > Ditto for Arch Linux, would love to try that one out too with the fix
>> for
>> > that.
>>
>> 
>> https://groups.google.com/d/msg/beagleboard/w9PfhGkByQU/bE_BNG4vgHgJ
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.rcn-ee.com/
>>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Will Kostelecky]

Micka:

I am now adding a Debian BBB to my collection to drive a 3d printer and 
need to apply your patch.   The new image did not work for me (hung on a 
black screen of death) so I followed the procedure for rebuilding the 
kernel per an earlier note of yours.   Unfortunately during this process I 
trashed the am335x_tsc file and was wondering if you know how I can get a 
source copy from the web.or if you can send me a copy of your patched 
version...

Thanks for any help you can render!

Cheers,
Will

On Tuesday, 28 January 2014 09:05:15 UTC, Mickae1 wrote:
>
> Well, It's good that it works in other device :)
>
> Micka,
>
>
> On Mon, Jan 27, 2014 at 9:32 PM, Terry Storm 
> > wrote:
>
>> Brilliant
>>
>> Thank you Robert, and thank you Micka for the patch.
>>
>> Just ran it up, booted from SD card and I cant fault the touch in the few 
>> minutes I have played with it.
>> Great news, thank you both.
>>
>> Will continue to test.
>>
>> Terry
>>
>> On Tuesday, 28 January 2014 02:45:40 UTC+13, RobertCNelson wrote:
>>
>>> On Mon, Jan 27, 2014 at 4:36 AM, Terry Storm  
>>> wrote: 
>>> > Great news 
>>> > 
>>> > Can someone please link me to the latest Debian/Ubuntu image which 
>>> features 
>>> > this fix? Is there is pre-made image available, or do I need to build 
>>> it? 
>>> > Ditto for Arch Linux, would love to try that one out too with the fix 
>>> for 
>>> > that. 
>>>
>>>  
>>> https://groups.google.com/d/msg/beagleboard/w9PfhGkByQU/bE_BNG4vgHgJ 
>>>
>>> Regards, 
>>>
>>> -- 
>>> Robert Nelson 
>>> http://www.rcn-ee.com/ 
>>>
>>  -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Bas Laarhoven]

Hi Piotr,

Have you studied the errata for the processor? IIRC some issues and 
workarounds with the TSC are documented there.


-- Bas


On 24-2-2014 12:51, michc...@o2.pl wrote:

Hi,

I step in as everybody looking to find solutions for TS issues. 
Actually, I'm still working on solving it. However, I have some tips 
and "discoveries" I'd like to share, meby someone will find it useful.


1) I have just external TS, no cape at all, the TS is 10 inch.

2) I found "after many hours :(" that ti_am335x_tsc driver can not be 
build in, and must be loaded as a module after the cape for TSC is 
loaded. That's because I use "overlay-ed" cape for TSC. Even though it 
is set to be loaded in uEnv.txt!


3) Big touch screen has bigger capacity, it results in permanent 
"auto-touch"  event generation, driving me nuts since LCD7 TS works 
nicely. I have discovered, that adjusting delays in driver is the 
solution!!!  There are "open-delay", "sample-delay", "charging-delay" 
defined in ti_am335x_tscad.h file. They have fundamental influence on 
this effect. Someone has mentioned that "hardware issue" was observed 
as a few "auto-touch" glitches. That is exactly this, just in case of 
a smaller TS, it is not so evident.


So, concluding, now I'm focusing on adjusting delays. I'll let you 
know my setting for this 10inch TS.


Regards,
Piotr


--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google 
Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to beagleboard+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


--
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Piotr Murawski]

Good point! However, the issue in the errata is about "pen-up" whereas I 
had "pen-down" false interrupt. Increasing charging time clearly moves the 
problem away. 
Piotr.

W dniu poniedziałek, 24 lutego 2014 14:45:31 UTC+1 użytkownik Bas Laarhoven 
napisał:
>
>
> Hi Piotr, 
>
> Have you studied the errata for the processor? IIRC some issues and 
> workarounds with the TSC are documented there. 
>
> -- Bas 
>
>
> On 24-2-2014 12:51, mich...@o2.pl  wrote: 
> > Hi, 
> > 
> > I step in as everybody looking to find solutions for TS issues. 
> > Actually, I'm still working on solving it. However, I have some tips 
> > and "discoveries" I'd like to share, meby someone will find it useful. 
> > 
> > 1) I have just external TS, no cape at all, the TS is 10 inch. 
> > 
> > 2) I found "after many hours :(" that ti_am335x_tsc driver can not be 
> > build in, and must be loaded as a module after the cape for TSC is 
> > loaded. That's because I use "overlay-ed" cape for TSC. Even though it 
> > is set to be loaded in uEnv.txt! 
> > 
> > 3) Big touch screen has bigger capacity, it results in permanent 
> > "auto-touch"  event generation, driving me nuts since LCD7 TS works 
> > nicely. I have discovered, that adjusting delays in driver is the 
> > solution!!!  There are "open-delay", "sample-delay", "charging-delay" 
> > defined in ti_am335x_tscad...

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[roop]

Hi Micka,

Would you be able to send me the driver you compiled with these changes? 
RobertCNelson's latest builds (-40) have ti_am335x_tsc.ko from last year.

I tried the steps you provided last night, I got as far as compiling the 
kernel but the driver I made had invalid ELF data so I did not try loading 
it.

Alternatively, the patch you have, which version of the ti_am335x_tsc.c driver 
is it meant to patch? there's been a lot of activity on ti_am335x_tsc.c.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[roop]

Hi Micka,

Any chance you can post the ti_am335x_tsc.ko that you compiled for debian? 
RobertCNelson's 
recent releases contain an old ti_am335x_tsc.ko (from last year).

On Tuesday, 28 January 2014 01:05:15 UTC-8, Mickae1 wrote:
>
> Well, It's good that it works in other device :)
>
> Micka,
>
>
> On Mon, Jan 27, 2014 at 9:32 PM, Terry Storm 
> > wrote:
>
> Brilliant
>
> Thank you Robert, and thank you Micka for the patch.
>
> Just ran it up, booted from SD card and I cant fault the touch in the few 
> minutes I have played with it.
> Great news, thank you both.
>
> Will continue to test.
>
> Terry
>
> On Tuesday, 28 January 2014 02:45:40 UTC+13, RobertCNelson wrote:
>
> On Mon, Jan 27, 2014 at 4:36 AM, Terry Storm  wrote: 
> > Great news 
> > 
> > Can someone please link me to the l
>
> ...

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

Are you sure ? =>
https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L847


On Tue, Mar 11, 2014 at 7:38 PM,  wrote:

> Hi Micka,
>
> Would you be able to send me the driver you compiled with these changes?
> RobertCNelson's latest builds (-40) have ti_am335x_tsc.ko from last year.
>
> I tried the steps you provided last night, I got as far as compiling the
> kernel but the driver I made had invalid ELF data so I did not try loading
> it.
>
> Alternatively, the patch you have, which version of the ti_am335x_tsc.c driver
> is it meant to patch? there's been a lot of activity on ti_am335x_tsc.c.
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Roop Singh]

My apologies:


-rw-r--r-- 1 root root  11K Feb 15 01:10 ti_am335x_tsc.ko


The jitter does not seem to be much better with this. Worse than the jitter is 
sometimes when I press and release, there is a much larger jump, say 50 pixels 
away from my finger. I see this with a 4.3" newhaven display. I have some 7" 
screens on the way, perhaps there will be a difference there?
  _  

From: Micka [mailto:mickamus...@gmail.com]
To: beagleboard@googlegroups.com
Sent: Thu, 13 Mar 2014 00:59:42 -0800
Subject: Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black 
LCD Capes


Are you sure ? => 
https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L847
  


On Tue, Mar 11, 2014 at 7:38 PM,   wrote:
  
Hi Micka,


Would you be able to send me the driver you compiled with these changes? 
RobertCNelson's latest builds (-40) have ti_am335x_tsc.ko from last year.  


I tried the steps you provided last night, I got as far as compiling the kernel 
but the driver I made had invalid ELF data so I did not try loading it.


Alternatively, the patch you have, which version of the ti_am335x_tsc.c driver 
is it meant to patch? there's been a lot of activity on ti_am335x_tsc.c.  




-- 
  For more options, visit http://beagleboard.org/discuss
  --- 
  You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to beagleboard+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.
  


-- 
  For more options, visit http://beagleboard.org/discuss
  --- 
  You received this message because you are subscribed to a topic in the Google 
Groups "BeagleBoard" group.
  To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/beagleboard/SXTaSUf4aSk/unsubscribe.
  To unsubscribe from this group and all its topics, send an email to 
beagleboard+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

If you have an oscilloscope I'm sure that you can see this crazy noise ...
. During my test i could saw the noise in the driver.

I also discovered that the TI driver include a filter to the jitter issue =>
module dejitter delta=100

I'm sure the jitter filter from TI is much better than mine .

 ... maybe it will be better to use the TI driver (TSLIB) than the default
driver . .


Robert Nelson ? Any idea how to do it ? I found some tutorial, but in my
last tried I didn't succeeded :

http://boundarydevices.com/debian-in-more-depth-adding-touch-support/


Micka,



On Thu, Mar 13, 2014 at 6:27 PM, Roop Singh  wrote:

>  My apologies:
>
> -rw-r--r-- 1 root root  11K Feb 15 01:10 ti_am335x_tsc.ko
>
> The jitter does not seem to be much better with this. Worse than the
> jitter is sometimes when I press and release, there is a much larger jump,
> say 50 pixels away from my finger. I see this with a 4.3" newhaven display.
> I have some 7" screens on the way, perhaps there will be a difference there?
>
> --
> *From:* Micka [mailto:mickamus...@gmail.com]
> *To:* beagleboard@googlegroups.com
> *Sent:* Thu, 13 Mar 2014 00:59:42 -0800
>
> *Subject:* Re: [beagleboard] Re: Touchscreen Jitter / Jumping on
> Beaglebone Black LCD Capes
>
> Are you sure ? =>
> https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L847
>
>
> On Tue, Mar 11, 2014 at 7:38 PM,  wrote:
>
>> Hi Micka,
>>
>> Would you be able to send me the driver you compiled with these changes?
>> RobertCNelson's latest builds (-40) have ti_am335x_tsc.ko from last year.
>>
>> I tried the steps you provided last night, I got as far as compiling the
>> kernel but the driver I made had invalid ELF data so I did not try loading
>> it.
>>
>> Alternatively, the patch you have, which version of the ti_am335x_tsc.c 
>> driver
>> is it meant to patch? there's been a lot of activity on ti_am335x_tsc.c.
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/SXTaSUf4aSk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Roop Singh]

I love TSLIB, their modular approach and on the fly tweaking allowed me to get 
the touchscreen working really well Then I found that X11 no longer 
supports TSLIB :(


My option was hacking this driver (which you've done to an extent, thanks 
again) or downgrading all of X11 to be compatible with TSLIB again. Maybe 
that's a better option, I'm not sure.


Is calling tslib from the driver what you're suggesting Micha?
  _  

From: Micka [mailto:mickamus...@gmail.com]
To: beagleboard@googlegroups.com
Cc: Robert Nelson [mailto:robertcnel...@gmail.com]
Sent: Thu, 13 Mar 2014 11:08:23 -0800
Subject: Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black 
LCD Capes


If you have an oscilloscope I'm sure that you can see this crazy noise ... . 
During my test i could saw the noise in the driver. 


I also discovered that the TI driver include a filter to the jitter issue =>  
module dejitter delta=100  


I'm sure the jitter filter from TI is much better than mine .


 ... maybe it will be better to use the TI driver (TSLIB) than the default 
driver . .

  


Robert Nelson ? Any idea how to do it ? I found some tutorial, but in my last 
tried I didn't succeeded :


http://boundarydevices.com/debian-in-more-depth-adding-touch-support/
  




Micka,





On Thu, Mar 13, 2014 at 6:27 PM, Roop Singh  wrote:
  
  My apologies:


-rw-r--r-- 1 root root  11K Feb 15 01:10 ti_am335x_tsc.ko  


The jitter does not seem to be much better with this. Worse than the jitter is 
sometimes when I press and release, there is a much larger jump, say 50 pixels 
away from my finger. I see this with a 4.3" newhaven display. I have some 7" 
screens on the way, perhaps there will be a difference there?  
_  

From: Micka [mailto:mickamus...@gmail.com]
To: beagleboard@googlegroups.com
  Sent: Thu, 13 Mar 2014 00:59:42 -0800

Subject: Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black 
LCD Capes




Are you sure ? => 
https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L847  
  


On Tue, Mar 11, 2014 at 7:38 PM,   wrote:

Hi Micka,


Would you be able to send me the driver you compiled with these changes? 
RobertCNelson's latest builds (-40) have ti_am335x_tsc.ko from last year.


I tried the steps you provided last night, I got as far as compiling the kernel 
but the driver I made had invalid ELF data so I did not try loading it.


Alternatively, the patch you have, which version of the ti_am335x_tsc.c driver 
is it meant to patch? there's been a lot of activity on ti_am335x_tsc.c.




-- 
  For more options, visit http://beagleboard.org/discuss
  --- 
  You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to beagleboard+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.
  


-- 
  For more options, visit http://beagleboard.org/discuss
  --- 
  You received this message because you are subscribed to a topic in the Google 
Groups "BeagleBoard" group.
  To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/beagleboard/SXTaSUf4aSk/unsubscribe.
  To unsubscribe from this group and all its topics, send an email to 
beagleboard+unsubscr...@googlegroups.com.

  For more options, visit https://groups.google.com/d/optout.




-- 
  For more options, visit http://beagleboard.org/discuss
  --- 
  You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to beagleboard+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.
  


-- 
  For more options, visit http://beagleboard.org/discuss
  --- 
  You received this message because you are subscribed to a topic in the Google 
Groups "BeagleBoard" group.
  To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/beagleboard/SXTaSUf4aSk/unsubscribe.
  To unsubscribe from this group and all its topics, send an email to 
beagleboard+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Roop Singh]

I seem to have some issue posting to google groups via the sites, my apologies 
if this gets duplicated.




I have a solution!


1). grab install.me from here: 
https://rcn-ee.net/deb/wheezy-armhf/v3.8.13-bone21/ and run it. It'd downgrade 
your kernel


2). Change your .dts files from touchscreen drives from ti,coordinate-readouts 
to ti,steps-to-configure and compile


3). Enjoy really nice touchscreen operation!






How I found this out: 3 days of fiddling with this! I noticed that the angstrom 
release's touchscreen works really well. I saw their .dts files had 
steps-to-configure in it instead of the newer ti,coordinate-readouts. I then 
read the driver changes in ti_am33x_tsc in linus' repo and traced it back to 
June 2013 which was the last time that 'step-to-configure' source was 
available. I don't know how to compile this file on it's own so I grabbed a 
RobertCNelson kernel from around that date (linked above). Ran install.sh, 
changed and recompiled my dtbo and voila!


I'll leave it to the dedicated people here to decide if they want to merge the 
two drivers together into a newer driver that's also perfect touschscreen 
response. Btw, the driver author wrote in the source about fixing this exact 
jumping problem:



/*
* Delta filter is used to remove large variations in sampled
* values from ADC. The filter tries to predict where the next
* coordinate could be. This is done by taking a previous
* coordinate and subtracting it form current one. Further the
* algorithm compares the difference with that of a present value,
* if true the value is reported to the sub system.
*/


I see that note missing in newer versions and that section gone, so this 
critical piece of code was removed for some reason.  _  

From: Micka [mailto:mickamus...@gmail.com]
To: beagleboard@googlegroups.com
Cc: Robert Nelson [mailto:robertcnel...@gmail.com]
Sent: Thu, 13 Mar 2014 11:08:23 -0800
Subject: Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black 
LCD Capes


If you have an oscilloscope I'm sure that you can see this crazy noise ... . 
During my test i could saw the noise in the driver. 


I also discovered that the TI driver include a filter to the jitter issue =>  
module dejitter delta=100  


I'm sure the jitter filter from TI is much better than mine .


 ... maybe it will be better to use the TI driver (TSLIB) than the default 
driver . .

  


Robert Nelson ? Any idea how to do it ? I found some tutorial, but in my last 
tried I didn't succeeded :


http://boundarydevices.com/debian-in-more-depth-adding-touch-support/
  




Micka,





On Thu, Mar 13, 2014 at 6:27 PM, Roop Singh  wrote:
  
  My apologies:


-rw-r--r-- 1 root root  11K Feb 15 01:10 ti_am335x_tsc.ko  


The jitter does not seem to be much better with this. Worse than the jitter is 
sometimes when I press and release, there is a much larger jump, say 50 pixels 
away from my finger. I see this with a 4.3" newhaven display. I have some 7" 
screens on the way, perhaps there will be a difference there?  
_  

From: Micka [mailto:mickamus...@gmail.com]
To: beagleboard@googlegroups.com
  Sent: Thu, 13 Mar 2014 00:59:42 -0800

Subject: Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black 
LCD Capes




Are you sure ? => 
https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L847  
  


On Tue, Mar 11, 2014 at 7:38 PM,   wrote:

Hi Micka,


Would you be able to send me the driver you compiled with these changes? 
RobertCNelson's latest builds (-40) have ti_am335x_tsc.ko from last year.


I tried the steps you provided last night, I got as far as compiling the kernel 
but the driver I made had invalid ELF data so I did not try loading it.


Alternatively, the patch you have, which version of the ti_am335x_tsc.c driver 
is it meant to patch? there's been a lot of activity on ti_am335x_tsc.c.




-- 
  For more options, visit http://beagleboard.org/discuss
  --- 
  You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to beagleboard+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.
  


-- 
  For more options, visit http://beagleboard.org/discuss
  --- 
  You received this message because you are subscribed to a topic in the Google 
Groups "BeagleBoard" group.
  To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/beagleboard/SXTaSUf4aSk/unsubscribe.
  To unsubscribe from this group and all its topics, send an email to 
beagleboard+unsubscr...@googlegroups.com.

  For more options, visit https://groups.google.com/d/optout.




-- 
  For more options, visit http://beagleboard.org/discuss
  --- 
  You received this message because you are subscr

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[roop]

I have a solution!

1). grab install.me from here: 
https://rcn-ee.net/deb/wheezy-armhf/v3.8.13-bone21/ and run it. It'd 
downgrade your kernel

2). Change your .dts files from touchscreen drives from 
ti,coordinate-readouts to ti,steps-to-configure and compile

3). Enjoy really nice touchscreen operation!



How I found this out: 3 days of fiddling with this! I noticed that the 
angstrom release's touchscreen works really well. I saw their .dts files 
had steps-to-configure in it instead of the newer ti,coordinate-readouts. I 
then read the driver changes in ti_am33x_tsc in linus' repo and traced it 
back to June 2013 which was the last time that 'step-to-configure' source 
was available. I don't know how to compile this file on it's own so I 
grabbed a RobertCNelson kernel from around that date (linked above). Ran 
install.sh, changed and recompiled my dtbo and voila!

I'll leave it to the dedicated people here to decide if they want to merge 
the two drivers together into a newer driver that's also perfect response. 
Btw, the driver author wrote in the source about fixing this exact jumping 
problem:

/*
 * Delta filter is used to remove large variations in sampled
 * values from ADC. The filter tries to predict where the next
 * coordinate could be. This is done by taking a previous
 * coordinate and subtracting it form current one. Further the
 * algorithm compares the difference with that of a present value,
 * if true the value is reported to the sub system.
 */

I see that note missing in newer versions and that section gone, so this 
critical piece of code was removed for some reason.

time for the champagne :)



On Thursday, 13 March 2014 11:08:23 UTC-7, Mickae1 wrote:
>
> If you have an oscilloscope I'm sure that you can see this crazy noise ... 
> . During my test i could saw the noise in the driver. 
>
> I also discovered that the TI driver include a filter to the jitter issue 
> =>
> module dejitter delta=100
>
> I'm sure the jitter filter from TI is much better than mine .
>
>  ... maybe it will be better to use the TI driver (TSLIB) than the default 
> driver . .
>
>
> Robert Nelson ? Any idea how to do it ? I found some tutorial, but in my 
> last tried I didn't succeeded :
>
> http://boundarydevices.com/debian-in-more-depth-adding-touch-support/
>
>
> Micka,
>
>
>
> On Thu, Mar 13, 2014 at 6:27 PM, Roop Singh  >wrote:
>
>  My apologies:
>
> -rw-r--r-- 1 root root  11K Feb 15 01:10 ti_am335x_tsc.ko
>
> The jitter does not seem to be much better with this. Worse than the 
> jitter is sometimes when I press and release, there is a much larger jump, 
> say 50 pixels away from my finger. I see this with a 4.3" newhaven display. 
> I have some 7" screens on the way, perhaps there will be a difference there?
>
> ------------------
> *From:* Micka [mailto:micka...@gmail.com ]
> *To:* beagl...@googlegroups.com 
> *Sent:* Thu, 13 Mar 2014 00:59:42 -0800
>
> *Subject:* Re: [beagleboard] Re: Touchscreen Jitter / Jumping on 
> Beaglebone Black LCD Capes
>
> Are you sure ? => 
> https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L847
>  
>
> On Tue, Mar 11, 2014 at 7:38 PM, > wrote:
>
> Hi Micka,
>
> Would you be able to send me the driver you compiled with these changes? 
> RobertCNelson's latest builds (-40) have ti_am335x_tsc.ko from last year.
>
> I tried the steps you provided last night, I got as far as compiling the 
> kernel but the driver I made had invalid ELF data so I did not try loading 
> it.
>
> Alternatively, the patch you have, which version of the ti_am335x_tsc.c 
> driver 
> is it meant to patch? there's been a lot of activity on ti_am335x_tsc.c.
>
>  -- 
> For more options, visit http://beagleboard.org/discuss
>
> ...

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fwd: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Micka]

Hi Robert,

What do you think about that ? ( bellow )

Could you change the kernel 3.8 to include this touchscreen driver update ?

Thx,

Micka.

-- Forwarded message --
From: Roop Singh 
Date: Mon, Mar 24, 2014 at 12:59 AM
Subject: Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone
Black LCD Capes
To: beagleboard@googlegroups.com
Cc: Robert Nelson 


 I seem to have some issue posting to google groups via the sites, my
apologies if this gets duplicated.

I have a solution!

1). grab install.me from here:
https://rcn-ee.net/deb/wheezy-armhf/v3.8.13-bone21/ and run it. It'd
downgrade your kernel

2). Change your .dts files from touchscreen drives from
ti,coordinate-readouts to ti,steps-to-configure and compile

3). Enjoy really nice touchscreen operation!



How I found this out: 3 days of fiddling with this! I noticed that the
angstrom release's touchscreen works really well. I saw their .dts files
had steps-to-configure in it instead of the newer ti,coordinate-readouts. I
then read the driver changes in ti_am33x_tsc in linus' repo and traced it
back to June 2013 which was the last time that 'step-to-configure' source
was available. I don't know how to compile this file on it's own so I
grabbed a RobertCNelson kernel from around that date (linked above). Ran
install.sh, changed and recompiled my dtbo and voila!

I'll leave it to the dedicated people here to decide if they want to merge
the two drivers together into a newer driver that's also perfect
touschscreen response. Btw, the driver author wrote in the source about
fixing this exact jumping problem:

/*
* Delta filter is used to remove large variations in sampled
* values from ADC. The filter tries to predict where the next
* coordinate could be. This is done by taking a previous
* coordinate and subtracting it form current one. Further the
* algorithm compares the difference with that of a present value,
* if true the value is reported to the sub system.
*/

I see that note missing in newer versions and that section gone, so this
critical piece of code was removed for some reason.

--
*From:* Micka [mailto:mickamus...@gmail.com]
*To:* beagleboard@googlegroups.com
*Cc:* Robert Nelson [mailto:robertcnel...@gmail.com]
*Sent:* Thu, 13 Mar 2014 11:08:23 -0800

*Subject:* Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone
Black LCD Capes

If you have an oscilloscope I'm sure that you can see this crazy noise ...
. During my test i could saw the noise in the driver.

I also discovered that the TI driver include a filter to the jitter issue =>
module dejitter delta=100

I'm sure the jitter filter from TI is much better than mine .

 ... maybe it will be better to use the TI driver (TSLIB) than the default
driver . .


Robert Nelson ? Any idea how to do it ? I found some tutorial, but in my
last tried I didn't succeeded :

http://boundarydevices.com/debian-in-more-depth-adding-touch-support/


Micka,



On Thu, Mar 13, 2014 at 6:27 PM, Roop Singh  wrote:

>  My apologies:
>
> -rw-r--r-- 1 root root  11K Feb 15 01:10 ti_am335x_tsc.ko
>
> The jitter does not seem to be much better with this. Worse than the
> jitter is sometimes when I press and release, there is a much larger jump,
> say 50 pixels away from my finger. I see this with a 4.3" newhaven display.
> I have some 7" screens on the way, perhaps there will be a difference there?
>
> --
> *From:* Micka [mailto:mickamus...@gmail.com]
> *To:* beagleboard@googlegroups.com
> *Sent:* Thu, 13 Mar 2014 00:59:42 -0800
>
> *Subject:* Re: [beagleboard] Re: Touchscreen Jitter / Jumping on
> Beaglebone Black LCD Capes
>
> Are you sure ? =>
> https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh#L847
>
>
> On Tue, Mar 11, 2014 at 7:38 PM,  wrote:
>
>> Hi Micka,
>>
>> Would you be able to send me the driver you compiled with these changes?
>> RobertCNelson's latest builds (-40) have ti_am335x_tsc.ko from last year.
>>
>> I tried the steps you provided last night, I got as far as compiling the
>> kernel but the driver I made had invalid ELF data so I did not try loading
>> it.
>>
>> Alternatively, the patch you have, which version of the ti_am335x_tsc.c 
>> driver
>> is it meant to patch? there's been a lot of activity on ti_am335x_tsc.c.
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
&