Author Topic: X.org Problems  (Read 7532 times)

olipage

  • Newbie
  • *
  • Posts: 10
    • View Profile
X.org Problems
« on: April 07, 2009, 07:12:59 am »
Hi,

I am using latest angstroem kernel 2.6.26 on my zaurus. After the upgrade to this kernel everything works as supposed, even better poverall performance. i was experimenting with window manager xfce, but didn't work out. now that i return to matchbox, actually setting everything back to matchbox i have a strange behaviour in xournal.

When trying to "write" or set marks to whatever the touchscreen seems to be really really sensible as it is almost unpossible to make a more or less good line. i have marks looking like a heartbeat in fact when trying to make a straight line?

does anyone have any idea where to begin searching for this thing? i liked xournal, but now its almost unusable as i can't write anything. when trying to write the marks get absolutely unreadable. besides of this all the otherthings are working fine...

kind regards,

Oliver Zieger

utx

  • Full Member
  • ***
  • Posts: 135
    • View Profile
    • http://www.penguin.cz/~utx/zaurus/
X.org Problems
« Reply #1 on: April 07, 2009, 07:40:50 am »
This is a problem of the kernel. According to the Cyril Hrubiš's blog and private talk, touch screen code in the kernel needs rewrite: Current implementation is polling based, but it should be interrupt based. To eliminate noise, reading of touchscreen should be synchronized with the LCD panel refresh.

As an ugly work-around you can use tslib filtering.

Note: Collie have had the same problem in past.

ofels

  • Full Member
  • ***
  • Posts: 139
    • View Profile
    • http://
X.org Problems
« Reply #2 on: April 07, 2009, 03:35:40 pm »
Quote from: utx
This is a problem of the kernel. According to the Cyril Hrubiš's blog and private talk, touch screen code in the kernel needs rewrite: Current implementation is polling based, but it should be interrupt based. To eliminate noise, reading of touchscreen should be synchronized with the LCD panel refresh.

As an ugly work-around you can use tslib filtering.

Note: Collie have had the same problem in past.

Needless to say that the same is occuring under zubuntu...

Oliver

olipage

  • Newbie
  • *
  • Posts: 10
    • View Profile
X.org Problems
« Reply #3 on: April 08, 2009, 11:04:32 am »
hey guys,

thanks a lot for this. so thats the reason for this. hm, it used to work fine with 2.6.23, so i thought this wouldn't really be something of the kernel, but ok.

kind regards,

Oliver

olipage

  • Newbie
  • *
  • Posts: 10
    • View Profile
X.org Problems
« Reply #4 on: May 25, 2009, 08:10:45 am »
Quote from: utx
This is a problem of the kernel. According to the Cyril Hrubiš's blog and private talk, touch screen code in the kernel needs rewrite: Current implementation is polling based, but it should be interrupt based. To eliminate noise, reading of touchscreen should be synchronized with the LCD panel refresh.

As an ugly work-around you can use tslib filtering.

Note: Collie have had the same problem in past.

well, i somehow got tslib to work, and using ts_test i get a really good result using the touchscreen. unfortunately, when using xournal, the result is still unusable. it seems, ts_test DOES use the device through the filtering using the env-vars, but the xournal for example not. is there a way to have the flitering used by all programs? unfortunatly i can't even say whether it is using filtering other then in ts_test. is there somewhere to look it up? setup and daemon seems to get started, following init.d (there is a start script, using the ts.conf) - if i have an invalid ts.conf screen does not work at all. so it seems to get loaded at least.

thanks for any advice...

Oliver