<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom">
    <title>gmane.linux.drivers.wacom</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6371"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6370"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6369"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6368"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6367"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6366"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6365"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6364"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6363"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6362"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6361"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6360"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6359"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6358"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6357"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6356"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6355"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6354"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6353"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.drivers.wacom/6352"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6371">
    <title>Re: Bamboo not loading in Centos 6.2</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6371</link>
    <description>&lt;pre&gt;Hi alettta,

Kernel 2.6.32-220.13.1.el6.centos.plus.x86_64
X.Org X Server 1.10.4

Looking at your Xorg.0.log:
[ 39.278] (II) Using input driver 'wacom' for 'cursor'
[ 39.278] (II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so
[ 39.278] (**) Option "SendCoreEvents"
[ 39.278] (**) cursor: always reports core events
[ 39.278] (**) Option "Device" "/dev/input/wacom"
[ 39.278] (WW) cursor: failed to open /dev/input/wacom.
[ 39.278] (EE) PreInit returned 8 for "cursor"
[ 39.278] (II) UnloadModule: "wacom"
[ 39.278] (II) Unloading wacom
[ 39.278] (II) Using input driver 'wacom' for 'stylus'
[ 39.278] (II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so
[ 39.278] (**) Option "SendCoreEvents"
[ 39.279] (**) stylus: always reports core events
[ 39.279] (**) Option "Device" "/dev/input/wacom"
[ 39.279] (WW) stylus: failed to open /dev/input/wacom.
[ 39.279] (EE) PreInit returned 8 for "stylus"
[ 39.279] (II) UnloadModule: "wacom"
[ 39.279] (II) Unloading wacom
[ 39.279] (II) Using input driver 'wacom' for 'eras&lt;/pre&gt;</description>
    <dc:creator>Favux ...</dc:creator>
    <dc:date>2012-05-18T18:35:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6370">
    <title>Re: Panasonic CF-H2 Toughbook - patch fortesting</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6370</link>
    <description>&lt;pre&gt;
Fine, so I do not need that. Is there a recommended package or project
around shipping proper udev rules for getting the wacom.ko kernel
driver inserted automatically after a kernel boot ?

As of now, I am doing this either manually or a distribution dependent
way, but I presume a proper udev relevant package or a project
containing that would be beneficial. Do you know something about that
?

Best Regards,
Laszlo Papp

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Laszlo Papp</dc:creator>
    <dc:date>2012-05-15T17:20:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6369">
    <title>Re: Panasonic CF-H2 Toughbook - patch fortesting</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6369</link>
    <description>&lt;pre&gt;
xf86-input-wacom isn't really necessary if you run a kernel newer than 2.6.35.


xf86-input-wacom update is mainly for kernels older than 2.6.35, which
does not pass resolution from input_absinfo.

Ping


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Ping Cheng</dc:creator>
    <dc:date>2012-05-15T17:11:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6368">
    <title>Re: Panasonic CF-H2 Toughbook - patch fortesting</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6368</link>
    <description>&lt;pre&gt;Okay, finally got this working, yay \o/.

The input-wacom driver insertion was enough alone. The installed
ubuntu package, xserver-xorg-input-wacom-1:0.14.0-0ubuntu2, is fine if
I insert the module. I do not need the patched one in that case.

I am not sure for what I need the patched one then. Perhaps for
getting module loaded automatically after a reboot ? Could you please
clarify ?

Best Regards,
Laszlo Papp

On Tue, May 15, 2012 at 7:37 PM, Laszlo Papp &amp;lt;lpapp&amp;lt; at &amp;gt;kde.org&amp;gt; wrote:

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Laszlo Papp</dc:creator>
    <dc:date>2012-05-15T16:54:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6367">
    <title>Re: Panasonic CF-H2 Toughbook - patch fortesting</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6367</link>
    <description>&lt;pre&gt;Hey,

I do not have such issues. Perhaps that was an old build log. This is
the current:
./autogen.sh --prefix=/usr --libdir=/usr/lib
autoreconf2.50: Entering directory `.'
autoreconf2.50: configure.ac: not using Gettext
autoreconf2.50: running: aclocal
autoreconf2.50: configure.ac: tracing
autoreconf2.50: running: libtoolize --install --copy
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf2.50: running: /usr/bin/autoconf
autoreconf2.50: running: /usr/bin/autoheader
autoreconf2.50: running: automake --add-missing --copy --no-force
autoreconf2.50: Leaving directory `.'
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
...

Rebuilding the git master HEAD version of the xf86-input-wacom project
does not break (no black blank screen), and the digitizer pen works.
Touch with my fingers does not.

It means that to me the driver does not really make the touch support
wor&lt;/pre&gt;</description>
    <dc:creator>Laszlo Papp</dc:creator>
    <dc:date>2012-05-15T16:37:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6366">
    <title>Re: Panasonic CF-H2 Toughbook - patch fortesting</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6366</link>
    <description>&lt;pre&gt;Hi Laszlo,

I added linuxwacom-discuss to our discussion so more people can reply
to you when I am not available.

libtool then build the kernel driver again.

Let's make sure the kernel driver works before moving to xf86-input-wacom.

To see if your Wacom kernel driver is running properly, please issue
"dmesg" after "modprobe wacom" and check message related to
wacom/Wacom.

Ping

On Tue, May 15, 2012 at 7:49 AM, Laszlo Papp &amp;lt;lpapp&amp;lt; at &amp;gt;kde.org&amp;gt; wrote:

------------------------
 root&amp;lt; at &amp;gt;symbio-CF-H2ASAAEF3:/home/symbio/Projects/wacom/input-wacom# ./autogen.sh
Can't exec "libtoolize": No such file or directory at
/usr/bin/autoreconf2.50 line 196.
Use of uninitialized value in pattern match (m//) at
/usr/bin/autoreconf2.50 line 196.
autoreconf2.50: Entering directory `.'
autoreconf2.50: configure.ac: not using Gettext
autoreconf2.50: running: aclocal
autoreconf2.50: configure.ac: tracing
autoreconf2.50: configure.ac: not using Libtool
autoreconf2.50: running: /usr/bin/autoconf
autoreconf2.50: running: /usr/bin/autohe&lt;/pre&gt;</description>
    <dc:creator>Ping Cheng</dc:creator>
    <dc:date>2012-05-15T16:29:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6365">
    <title>Bamboo not loading in Centos 6.2</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6365</link>
    <description>&lt;pre&gt;Subject: Re: [Linuxwacom-discuss] installing a Wacom Pad under Centos
        6.2
To: aletta&amp;lt; at &amp;gt;aletta.org
Cc: LinuxWacom Discuss &amp;lt;linuxwacom-discuss&amp;lt; at &amp;gt;lists.sourceforge.net&amp;gt;
Message-ID:
        &amp;lt;CANRwn3R0VwPS3Sb6NKO1y8L4by9WLCZuHdcjrDQ3Ynv+f0Pfwg&amp;lt; at &amp;gt;mail.gmail.com&amp;gt;
Content-Type: text/plain; charset=UTF-8

Could you attach the contents of your /var/log/Xorg.0.log file and
/etc/X11/xorg.conf file if you have one? It might be that the wacom
driver isn't being loaded.

Jason
&lt;/pre&gt;</description>
    <dc:creator>aletta mes</dc:creator>
    <dc:date>2012-05-15T01:04:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6364">
    <title>Re: Bamboo One, Pressure Reset</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6364</link>
    <description>&lt;pre&gt;

Thanks for the update.  I'll attempt to submit a patch to upstream asap.

Chris

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Chris Bagwell</dc:creator>
    <dc:date>2012-05-10T17:40:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6363">
    <title>Re: Ubuntu 12.04: Serial Wacom Tablet touch not in absolute mode when logged in</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6363</link>
    <description>&lt;pre&gt;10.05.2012 20:20, Timo Aaltonen kirjoitti:

.. though it also makes gnome-settings-daemon crashy, need to figure out
why.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Timo Aaltonen</dc:creator>
    <dc:date>2012-05-10T17:33:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6362">
    <title>Re: Ubuntu 12.04: Serial Wacom Tablet touch not in absolute mode when logged in</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6362</link>
    <description>&lt;pre&gt;07.05.2012 06:24, Favux ... kirjoitti:

The bug was due to g-s-d using the fallback device settings, since it
couldn't find a match from the libwacom data. Updating libwacom to 0.5
fixed it.

t

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Timo Aaltonen</dc:creator>
    <dc:date>2012-05-10T17:20:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6361">
    <title>Panasonic CF-H2 Toughbook - Touchscreen doesnot work</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6361</link>
    <description>&lt;pre&gt;Hey,

I have just come across this thread due to similar issues I am now tackling:
http://sourceforge.net/mailarchive/forum.php?thread_name=CAGzDe_a_LGjREjbuuCHXNUoRYhOJHAvgH_YfvZv22NSc6jsHvg%40mail.gmail.com&amp;amp;forum_name=linuxwacom-discuss

Having that thread read, I was able to get the digitizer work; thanks
to "Chris" and "favux". Please read this thread for further details:
https://sourceforge.net/tracker/?func=detail&amp;amp;atid=525125&amp;amp;aid=3462918&amp;amp;group_id=69596

I am having precisely this device:
http://business.panasonic.co.uk/computer-product/products-and-accessories/introducing-the-full-toughbook-range/fully-ruggedized-toughbooks/cf-h2-field

At any rate, if I understood correctly, the solution for the
touchscreen in case the Samsung Slate 7 hardware, was an "upstream"
Linux kernel patch. What would be the best place where this issue
should be addressed ? I am not really a master of these hardwares,
especially since this panasonic toughbook is quite rare and extremely
expensive due to the military usage. :-)&lt;/pre&gt;</description>
    <dc:creator>Laszlo Papp</dc:creator>
    <dc:date>2012-05-10T10:27:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6360">
    <title>Re: Bamboo One, Pressure Reset</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6360</link>
    <description>&lt;pre&gt;Hi Chris,

I hope I'm not stealing Chu's thunder.


He did test your second solution.  "Okay, tested that code. Seems to
work!".  Screenshot:  http://i.imgur.com/McKKL.png

He also supplied evtest(3).txt.  I see the full pressure range,
starting at 3 and going all the way up to 1023.  Looks like you got it
first try.  :)

Favux
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
&lt;/pre&gt;</description>
    <dc:creator>Favux ...</dc:creator>
    <dc:date>2012-05-09T20:27:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6359">
    <title>Re: two screens , a tablet and two pointers</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6359</link>
    <description>&lt;pre&gt;Hello,

It's working now.

I have generated a new xorg.conf , using nvidia-settings.
The trick has been to forget Xinerama, which was not working.
Instead, i use simple screen overlay, with Twinview:

Section "Screen"
     Identifier     "Screen0"
     Device         "Device0"
     Monitor        "Monitor0"
     DefaultDepth    24
     Option         "TwinView" "1"
     Option         "TwinViewXineramaInfoOrder" "CRT-0"
     Option         "metamodes" "CRT-0: 1280x1024 +0+0, CRT-1: 1280x1024 
+1280+0"
     SubSection     "Display"
         Depth       24
     EndSubSection
EndSection

If someone would use this configuration, then don't forget to remove 
«monitor» configuration from /etc/X11/xorg.conf.d/ directory.

Using «xorg.conf» configuration file is quite old school (it doesn't 
even exists in moderns xorg installations), but for me it was the solution.

You can find the complete config file here:

http://pastebin.com/4p5RcSPu


Thank you for helping me solving this.



-----------------------------&lt;/pre&gt;</description>
    <dc:creator>jseb</dc:creator>
    <dc:date>2012-05-08T21:03:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6358">
    <title>Re: Bamboo One, Pressure Reset</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6358</link>
    <description>&lt;pre&gt;
Glad to hear it.  If you have some spare time, I would appreciate if
you could test this solution since its safer for us to ship.

Replace the line you modified to 0x03 to instead read:

input_report_abs(input, ABS_PRESSURE, (le16_to_cpup((__le16
*)&amp;amp;data[6]) &amp;amp; features-&amp;gt;pressure_max));

Chris

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Chris Bagwell</dc:creator>
    <dc:date>2012-05-08T20:14:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6357">
    <title>Re: Bamboo One, Pressure Reset</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6357</link>
    <description>&lt;pre&gt;
Thanks for confirming, Jason.  Since pressure_max happens to be an
appropriate bitmask for all GRAPHIRES, we could change from this:

input_report_abs(input, ABS_PRESSURE, data[6] | ((data[7] &amp;amp; 0x01) &amp;lt;&amp;lt; 8));

to this to always ignore invalid bits and run faster.

input_report_abs(input, ABS_PRESSURE, (le16_to_cpup((__le16
*)&amp;amp;data[6]) &amp;amp; features-&amp;gt;pressure_max));

I always seem to get endian stuff wrong on first try but hopefully that works.

If someone could test it on a Graphire that supports at least 512
pressure levels then we can commit this fix.

Chris

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Chris Bagwell</dc:creator>
    <dc:date>2012-05-08T19:27:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6356">
    <title>Re: Bamboo One, Pressure Reset</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6356</link>
    <description>&lt;pre&gt;I did some quick looking around, and I can confirm that those two PIDs
have 1024 levels of pressure. As Chris suspects, the extra bit is in
(data[7] &amp;amp; 0x02). I'm not 100% sure if that bit is 0 for tablets with
only 512 levels, but we usually try to be compatible when expanding
packet formats. I don't see any conflicts in that bit with the packets
from the older Graphire {3,4} so its probably safe.

Jason

---
Day xee-nee-svsh duu-'ushtlh-ts'it;
nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it.
Huu-chan xuu naa~-gha.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss&amp;lt; at &amp;gt;lists.sourcefor&lt;/pre&gt;</description>
    <dc:creator>Jason Gerecke</dc:creator>
    <dc:date>2012-05-08T16:26:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6355">
    <title>Re: Bamboo One, Pressure Reset</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6355</link>
    <description>&lt;pre&gt;Yes, several testers reported pressure was working.  Two on the LWP
forum:  http://sourceforge.net/projects/linuxwacom/forums/forum/236871/topic/4520268

I think I followed your argument on changing the wacom_graphire_irq():
and that looks easy enough.  Hopefully Chu will be willing to test
that for us after he sets the pressure level back to 1024.  Chu,
that's in wacom_wac.c line #246.

For the rest that's up to you, Jason, and Ping.

Favux

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Favux ...</dc:creator>
    <dc:date>2012-05-08T03:18:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6354">
    <title>Re: Bamboo One, Pressure Reset</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6354</link>
    <description>&lt;pre&gt;
Hmmm, lets hope they didn't do that.  Were there any reports of
pressure working with a 0x6A or 0x6B that you've heard of?

I also had started with Amazon and thats were I saw the 512.  I guess
I should have started with Wacom.

OK.  So we are not reading enough bits to get 1024 values.  The way
that would behave is how described.  Pressure would work normal up
until half way point and then roll over  to zero pressure; never going
above 50% pressure while at full pressure.

If we are lucky, the missing bit is just the higher order bit in
data[7].  Find this in wacom_graphire_irq():

                        input_report_abs(input, ABS_PRESSURE, data[6]
| ((data[7] &amp;amp; 0x01) &amp;lt;&amp;lt; 8));

and change to this:

                        input_report_abs(input, ABS_PRESSURE, data[6]
| ((data[7] &amp;amp; 0x03) &amp;lt;&amp;lt; 8));


Its hard to know if we can submit that change though.  Maybe Ping or
Jason can comment.  We are always looking at data[7] &amp;amp; 0x1 even on
hardware that only supports 256 level so we know it seems to be fixed
to zer&lt;/pre&gt;</description>
    <dc:creator>Chris Bagwell</dc:creator>
    <dc:date>2012-05-08T02:54:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6353">
    <title>Re: Bamboo One, Pressure Reset</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6353</link>
    <description>&lt;pre&gt;Hi Chris,

The Bamboo 6A and 6B are the CTE460 and CTE660 respectively.  It's on
the back of your tablet Chu.

Most of the sites show 1024 pressure levels for those CTE models.  If
it was a CTF then 512 I think.:
http://www.wacom.asia/in/bamboo-tablets/bamboo-one
http://www.wacom.com.hk/product/bamboo-one-medium
http://www.theitbazaar.com/store/our-shop?page=shop.product_details&amp;amp;flypage=flypage.tpl&amp;amp;product_id=666&amp;amp;vmcchk=1
http://www.buytheprice.com/shop-online-deal/wacom-bamboo-one-small__2392

Although to add to the fun this one shows both:
http://www.amazon.co.uk/Wacom-Bamboo-One-Graphics-Tablet/dp/tech-data/B000VZZCSO

I don't know if Wacom ever sells models with the same PID but
different pressure levels.

Favux

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile sec&lt;/pre&gt;</description>
    <dc:creator>Favux ...</dc:creator>
    <dc:date>2012-05-08T01:18:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6352">
    <title>Re: Bamboo One, Pressure Reset</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6352</link>
    <description>&lt;pre&gt;
Everything I see on google indicates Bamboo One's only support 512
pressure levels.   The line you show here says its using the same
packet format as Graphire models and all those are shown as only
support 512 or 256 levels so it looks like this modification is needed
to be logically correct but we will need some other change it seems.


Since you were OK with above edit, are you OK trying other changes?

In wacom_graphire_irq(), this is how pressure is computed (enough bits
for 512 levels);

input_report_abs(input, ABS_PRESSURE, data[6] | ((data[7] &amp;amp; 0x01) &amp;lt;&amp;lt; 8));

Some of the other tablets have similar pressure logic but they also do
something I've never fully understood.  Here is from Tablet PC logic:

                int pressure = ((data[7] &amp;amp; 0x01) &amp;lt;&amp;lt; 8) | data[6];
                if (pressure &amp;lt; 0)
                        pressure = features-&amp;gt;pressure_max + pressure + 1;
                input_report_abs(input, ABS_PRESSURE, pressure);

I mean I can kinda guess but haven't fully worked it out on paper.
&lt;/pre&gt;</description>
    <dc:creator>Chris Bagwell</dc:creator>
    <dc:date>2012-05-08T00:31:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.drivers.wacom/6351">
    <title>Bamboo One, Pressure Reset</title>
    <link>http://permalink.gmane.org/gmane.linux.drivers.wacom/6351</link>
    <description>&lt;pre&gt;In Ubuntu's Precise Pangolin (12.04 -- both on upgrade and fresh install) I
have a problem with pressure on my Wacom Bamboo One medium (056a:006b).
This screenshot shows the problem: http://i.imgur.com/z3Lgk.png

Athlon x2, 3GB RAM DDR2
3.2 kernel
X Server 1.11.3
xf86-input-wacom-0.14.0 - with some Ubuntu patches

xsetwacom list
Wacom Bamboo1 5x8 stylus id: 8 type: STYLUS
Wacom Bamboo1 5x8 eraser id: 11 type: ERASER
Wacom Bamboo1 5x8 cursor id: 12 type: CURSOR

Several Wacom sites say the 6B has 1024 pressure levels. My model was sold
in India. In evtest, see evtest(1).txt (attached), I noticed the maximum
ABS_PRESSURE shown was 511 as I drew a series of lines. So I downloaded the
input-wacom-0.13.0 tar and changed the pressure level to 512.
*static const struct wacom_features wacom_features_0x6B =
{ "Wacom Bamboo1 5x8", WACOM_PKGLEN_GRAPHIRE, 21648, 13530, 511,
63, GRAPHIRE, WACOM_INTUOS_RES, WACOM_INTUOS_RES };*

After compiling and installing the input-wacom wacom.ko the pressure
problem was unchanged. Ev&lt;/pre&gt;</description>
    <dc:creator>Chu</dc:creator>
    <dc:date>2012-05-07T20:38:29</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.drivers.wacom">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.drivers.wacom</link>
  </textinput>
</rdf:RDF>

