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 <anguel....@gmail.com<javascript:> > > 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 <anguel....@gmail.com> 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 <javascript:>. >> 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.
