I see it too. As Peter said in the beginning of my crusade "all values are
sane".
But damn I feel it, the difference between how I it works in Windows 7 (and
that's
how I expected it to work and feel) and how it work in Linux. I surveyed 3
more
poeple to confirm that there is a difference.
and I thought comparison of isdv4-debugger log and xinput log reveals what's
wrong,
because it's definitely show that X got full pressure, when device reporting
aroung the
half of it. I saw when executed both at once.
And I followed isdv4-debugger output, it's values "felt sane". I mean I got
maximum
when I felt it should be, and progression of values was corresponding to
force
I exerted. xinput --test on the other hand was very sensitive.
On Wed, Jan 19, 2011 at 03:04, Ping Cheng <[email protected]> wrote:
> On Tue, Jan 18, 2011 at 1:57 PM, Chris Bagwell <[email protected]>
> wrote:
> > On Tue, Jan 18, 2011 at 3:49 PM, Ping Cheng <[email protected]> wrote:
> >> On Tue, Jan 18, 2011 at 11:32 AM, AndrewP <[email protected]> wrote:
> >>> Updated driver from git, and here's my Xorg.0.log for
> >>> it http://dpaste.org/D35D/
> >>> maxZ=127, as it was before.
> >>
> >> I get maxZ=127 in my log file as well. So, you are not alone.
> >>
> >>> and here's tablet id:
> >>> nomad insonifi # cat /sys/class/tty/ttyS0/device/id
> >>> WACf004
> >>
> >> I have the same device id as yours: WACf004
> >>
> >> With the latest xf86-input-wacom from git, the pen can still reliably
> >> move the cursor here.
> >
> > Can you use it in gimp with accurate pressure levels?
>
> I don't know how to tell the accurate pressure levels in gimp :(. All
> I can tell is that I got pressure.
>
> > At the least,
> > your both getting only 1/2 the pressure levels because of that 127.
>
> I see 0 to 2048 when I run "xinput test" on the tool.
>
> Ping
>
> > I can see how the needed Threshold value can pretty much only get full
> > pressure into gimp.
> >
> >>
> >>> I didn't understand why inputattach didn't work. I checked serial
> device
> >>> with xdd, and confirmed tablet uses ttyS0.
> >>> then executed ./inputattach --wacom /dev/ttyS0 in root console. event10
> >>> device appeared, but it was silent,
> >>> neither xinput nor evtest haven't output anything from it.
> >>
> >> Make sure no other driver is driving your device and you issued evtest
> >> under root (I believe you did). Nothing else I can think of at this
> >> moment.
> >>
> >> Ping
> >>
> >>> On Tue, Jan 18, 2011 at 15:46, Chris Bagwell <[email protected]>
> wrote:
> >>>>
> >>>> Hi Andrew,
> >>>>
> >>>> Can you upgraded to latest git? There was a fix that went in that I
> >>>> think will now return maxZ in log file for "generic" tablets.
> >>>>
> >>>> I think your tablet is being considered generic and not setting a
> >>>> variable called tablet_id. I'm not sure it means much related to your
> >>>> problem but maybe.
> >>>>
> >>>> There should be a file of form /sys/class/tty/ttyS0/device/id. Can
> >>>> you show what its value is?
> >>>>
> >>>> Chris
> >>>>
> >>>> On Tue, Jan 18, 2011 at 9:03 AM, AndrewP <[email protected]> wrote:
> >>>> > Ok, here I have Xorg.0.log, where I don't see any maxZ
> >>>> > values. http://dpaste.org/nL1t/
> >>>> > And log and output after I've run ./inputattach --wacom /dev/ttyS0 &
> >>>> > http://dpaste.org/5vON/ -- Xorg.0.log with inputattach (W8001)
> >>>> > http://dpaste.org/WrfR/ -- Xinput --list
> >>>> >
> >>>> > Tablet didn't work with inputattach. And inputattach didn't work
> with
> >>>> > --wacom-384 (just if you're curious).
> >>>> >
> >>>> > On Tue, Jan 18, 2011 at 02:10, Ping Cheng <[email protected]>
> wrote:
> >>>> >>
> >>>> >> On Mon, Jan 17, 2011 at 11:19 AM, AndrewP <[email protected]>
> wrote:
> >>>> >> > sure, I do. If I set it high it works almost like mouse button
> >>>> >> > (without
> >>>> >> > any
> >>>> >> > pressure) if low I get more pressure levels (very sensitive
> >>>> >> > progression),
> >>>> >> > but clicks get very sensitive.
> >>>> >> > I stress I have very low pressure range, if I increase threshold
> I
> >>>> >> > get
> >>>> >> > even
> >>>> >> > less, but need to exert more force (which is quite consistent).
> It
> >>>> >> > looks
> >>>> >> > biased to me. That's why it is so sensitive.
> >>>> >> > What should I do to help you?
> >>>> >>
> >>>> >> Trace into the code is one way. Or you can try the kernel serial
> >>>> >> driver (included in input-wacom-0.10.10-1/2.6.30/wacom-w8001.c) and
> >>>> >> follow the steps at input-wacom-0.10.10-1/inputattch/README to let
> the
> >>>> >> kernel driver drive your device). If wacom_w8001.c works for you,
> we
> >>>> >> can say for sure there are issues for isdv4 support in
> >>>> >> cf86-input-wacom. If not,...well, we have to find other ways to
> nail
> >>>> >> the issue.
> >>>> >>
> >>>> >> Ping
> >>>> >>
> >>>> >> P.S., Chris' question may help us know something of your device or
> the
> >>>> >> driver too.
> >>>> >
> >>>> >
> >>>
> >>>
> >>
> >
>
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
