Could you present me some advice as New Year gift? :) I've updated to 2.6.37 recently.
On Tue, Dec 28, 2010 at 09:47, AndrewP <[email protected]> wrote: > Checked through Xorg.0.log once more, and something caught my attention. > > [ 26.461] (--) stylus: Wacom General ISDV4 tablet maxX=26312 maxY=16520 > maxZ=127 resX=2540 resY=2540 tilt=disabled > > maxZ value is 127. Isn't it max pressure level? Its't nor 255 nor 2047. Why > 127 then? Where it came from? > > Maybe my tablet ID isn't recognized correctly? > > > > On Tue, Dec 28, 2010 at 12:21, AndrewP <[email protected]> wrote: > >> Unfortunately, my developer abilities are very limited. I honestly looked >> through the code, and found one place where pressure is filtered to adjust >> for weared styli. Maybe it has something to do with my issue, some misfit >> happens? >> >> As far as I know my tablet has 256 levels of pressure (according to >> specifications), and we have 2048 levels in xinput, could it be some scaling >> mistake? For example it is scaled too much, but we're limited to 2048 levels >> and driver cuts the rest? we saw it happening when isdv4-debugger showed >> pressure level around 100, when xinput was maxed-out to 2048, already. >> I couldn't find where translation to xinput values takes place. >> >> >> >> >> On Tue, Dec 28, 2010 at 01:19, Ping Cheng <[email protected]> wrote: >> >>> On Mon, Dec 27, 2010 at 4:59 AM, AndrewP <[email protected]> wrote: >>> > Hello, >>> > tried it once more in another distribution with live usb, behaviour >>> is >>> > the same. Unfortunately Live media didn't provide xinput or >>> isdv4-debugger, >>> > and I can't substantiate my words with their output. >>> > >>> > here's my Xorg.0.log http://dpaste.org/4OkF/ >>> > my parameter values http://dpaste.org/bYwv/ all are defaults, >>> except for >>> > Threshold which was increased due to false clicks and sensitivity on >>> Peter's >>> > advice. >>> >>> I tested my system with the driver from git on X server 1.9.3 (Fedora >>> 14). I see full pressure up to 2048. So, it does look like something >>> unique to your system/device. >>> >>> > i believe both issues are connected and relate to distorted value >>> > translations from serial to X, as you remember isdv4-debugger output >>> was >>> > seemingly acceptable (in sense of pressure levels it was fine). >>> >>> If isdv4-debugger output is right, it likely means that the device is >>> not something we can blame. >>> >>> > Anyway, my primary concern is, I have about ten pressure gradations in >>> X >>> > (gimp) and there are all 256 visible in isdv4-debugger. >>> >>> Peter worked on isdv4-debugger. I am not very familiar with that tool. >>> But if it reports the correct value, I guess we can trust it. >>> >>> > I guess if I had entire pressure range I won't even encounter this >>> false >>> > clicks, because they would fit into Threshold. >>> >>> I guess so too. It might be something between the raw data is >>> processed and posted, i.e., maybe the pressure was not posted properly >>> to XInput. >>> >>> > So what it could be? wrong driver settings? buggy X? or some >>> inaccuracies in >>> > input-wacom driver? >>> >>> How comfortable are you with debugging the driver? Tracing into the >>> code is the most reliable way to figure out the root cause of the >>> issue. The two files that you can pay a bit of attention are: >>> wcmISDV4.c and wcmCommon.c. >>> >>> Ping >>> >> >> >
------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
