[Linuxwacom-devel] xsetwacom: Add Tab key to special keys

[Favux ...]

Requested by Intuous4 user.
From 5bc58c8800168a8deec1c4aa8a1a63a95beab094 Mon Sep 17 00:00:00 2001
From: David 
Date: Sat, 7 Aug 2010 13:02:10 -0500
Subject: [PATCH] xsetwacom:  add Tab key to special keys
 Signed-off-by: David Foley 

---
 tools/xsetwacom.c |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/tools/xsetwacom.c b/tools/xsetwacom.c
index 1577c6e..d68606e 100644
--- a/tools/xsetwacom.c
+++ b/tools/xsetwacom.c
@@ -917,6 +917,8 @@ static struct modifier specialkeys[] = {
 
 	{"backspace", "BackSpace"}, {"Backspace", "BackSpace"},
 
+	{"tab", "Tab"},
+
 	{ NULL, NULL }
 };
 
-- 
1.7.0.4

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev ___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] xsetwacom: Add space key to special keys

[Favux ...]

Hi,

Another one.  This time requested by a Intuos3 user.

Dave
From 1e5cc45d9c65e4f2669c34948a05d394e8f1a626 Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Mon, 9 Aug 2010 12:07:20 -0500
Subject: [PATCH] xsetwacom:  add space key to special keys
 Signed-off-by: David Foley 

---
 tools/xsetwacom.c |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/tools/xsetwacom.c b/tools/xsetwacom.c
index d68606e..1c76788 100644
--- a/tools/xsetwacom.c
+++ b/tools/xsetwacom.c
@@ -919,6 +919,8 @@ static struct modifier specialkeys[] = {
 
 	{"tab", "Tab"},
 
+	{"Space", "space"},
+
 	{ NULL, NULL }
 };
 
-- 
1.7.0.4

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev ___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] xsetwacom: Add space key to special keys

[Favux ...]

On Mon, Aug 9, 2010 at 7:47 PM, Peter Hutterer  wrote:
>
> Maybe we should put a note into the man page that the key sequences accepted
> are X keysyms readily to be obtained with e.g. xev?

Good idea.

> I don't quite agree with this one anyway - while I can understand that we'd
> be adding lowercase versions for those that are otherwise capitalised or
> camel case as X symbols, I don't think we need capitalised versions for
> already lowercase symbols.

Understood.  Thank you for explaining and for looking at it.

Dave

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Wacom Bamboo Fun: Pen&Touch problem

[Favux ...]

On Mon, Aug 16, 2010 at 4:45 PM, Juan Carlos  wrote:
> Hi,
>
> First of all Whot said me, after chat with him in the irc channel, that I
> should send my problem here :)
>
> I recently bought a Wacom Bamboo Fun: Pen&Touch, and I could saw that didn't
> work due its not supported surely. I tested the last tarball.
> Dmesg:
> [209232.857279] usbcore: registered new interface driver wacom
> [209232.857452] wacom: v1.52:USB Wacom tablet driver
> [209266.091331] usb 8-2: new full speed USB device using uhci_hcd and
> address 4
> [209266.266325] usb 8-2: configuration #1 chosen from 1 choice
>
> Devices
> http://pastebin.com/d7cQFLDU
>
> Best regards,
> Juan Carlos
>
>

Hi Juan,

What linux distro do you have?  Which release?

What version Xserver?  What kernel?

Favux

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Wacom Bamboo Fun: Pen&Touch problem

[Favux ...]

On Wed, Aug 18, 2010 at 9:52 AM, Tom  wrote:
> Hi,
>
> i have the same problem with ubuntu 10.10 (kernel 2.6.35, xserver 1.8 i
> think). Bamboo P&T is not detected.
> Cheers,
>
> Tom
>
>
> On Mon, 2010-08-16 at 18:38 -0500, Favux ... wrote:
>> On Mon, Aug 16, 2010 at 4:45 PM, Juan Carlos  wrote:
>> > Hi,
>> >
>> > First of all Whot said me, after chat with him in the irc channel, that I
>> > should send my problem here :)
>> >
>> > I recently bought a Wacom Bamboo Fun: Pen&Touch, and I could saw that 
>> > didn't
>> > work due its not supported surely. I tested the last tarball.
>> > Dmesg:
>> > [209232.857279] usbcore: registered new interface driver wacom
>> > [209232.857452] wacom: v1.52:USB Wacom tablet driver
>> > [209266.091331] usb 8-2: new full speed USB device using uhci_hcd and
>> > address 4
>> > [209266.266325] usb 8-2: configuration #1 chosen from 1 choice
>> >
>> > Devices
>> > http://pastebin.com/d7cQFLDU
>> >
>> > Best regards,
>> > Juan Carlos
>> >
>> >
>>
>> Hi Juan,
>>
>> What linux distro do you have?  Which release?
>>
>> What version Xserver?  What kernel?
>>
>> Favux
>>

Hi Tom,

Linuxwacom doesn't support the 2.6.35 kernel yet.  So you can't build
a wacom.ko that communicates to the Bamboo.  There's a work-a-round in
the Maverick development forum you could try.  I link to it from the
linuxwacom HOW TO:
http://ubuntuforums.org/showpost.php?p=6546012&postcount=1  It's near
the top in "Lucid Lynx (10.4) & Maverick Meerkat (10.10)".  I think
part of the work-a-round was recently added to linuxwacom so that
might complicate things.

Favux

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Wacom Intuos4 LED userland app

[Favux ...]

On Sat, Aug 21, 2010 at 5:03 AM, Christoph Karg  wrote:
> Hello,
>
> as an owner of a wacom intuos4 tablet I was eager to apply Nick Hirsch's patch
> to support the led display of the tablet.
>
> Unfortunately, the patch didn't work for me. I use Debian Squeeze with a
> custom linux kernel 2.6.34.2. At first, I thought about to modify the patch to
> work with my kernel. But since the usbfs is marked as deprecated, I decided to
> write a little userland command line application for setting the led display.
> I used the code posted in this forum and put it in a C++ class in order to
> have a proper interface. The result is a little application for interaction
> with the intuos4. The features of the app are:
>
> 1. The app uses libusb to communicate with the tablet.
> 2. Images are converted to an appropriate format under usage of the Magick
> library. This is, you can download a png/jpg image directly to the tablet, if
> the image has the appropriate size.
> 3. The app contains an icon library. These icons can be used directly for
> configuration the tablet display. A bunch of common icons are included in 
> order
> to use the app without generating appropriate images. The library is
> expandable.
>
> Pros:
>
> - Easy to use
> - no kernel patch needed, i.e., works with the standard kernel
>
> Cons:
>
> - must be root to execute the software
> - the wacom driver must be reloaded after usage of the software (an
> appropriate shell script is included in the archive)
> - works only with the Intuos4 M tablet (since I don't know the vendor and
> product ids of the other Intuos 4 tablets).
>
> I have attached an archive with the code and a little documentation.
>
> Sincerely,
> Christoph
>

Hi Christoph,

Thank you for the Intuous4 OLED applet.  I've linked a couple Intuous4
threads on Ubuntu forums to your post, so hopefully some testers soon.
 Am I correct in assuming, if they have another Intuous4 with a
different product number, all they need to do is add another line to
the defines in WacomIntuous4LED.cpp under line 19, basically
duplicating line 19 with the new produc id?  And substitute their for
Product ID for yours at line 16 in intous4-led-check.cpp?

Favux

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Wacom Intuos4 LED userland app

[Favux ...]

Hi Christoph,

By the way here are all the Intuos4 Product ID's I'm aware of:

ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b8",
SYMLINK+="input/tablet-intuos4-4x6"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b9",
SYMLINK+="input/tablet-intuos4-6x9"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00ba",
SYMLINK+="input/tablet-intuos4-8x13"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00bb",
SYMLINK+="input/tablet-intuos4-12x19"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00bc",
SYMLINK+="input/tablet-intuos4-wl-usb"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00bd",
SYMLINK+="input/tablet-intuos4-wl"

Favux

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Wacom Bamboo Fun: Pen&Touch problem

[Favux ...]

On Tue, Aug 31, 2010 at 10:02 PM, Chris Bagwell  wrote:
> On Tue, Aug 31, 2010 at 12:44 AM, Peter Hutterer
>  wrote:
>> On Wed, Aug 25, 2010 at 06:28:53PM +0200, Ping Cheng wrote:
>>> On Wed, Aug 25, 2010 at 5:04 PM, Chris Bagwell  wrote:
>>> > Sure, I'll jump back in once the touch-only model support is
>>> > committed.  Assuming Henrik's patch is submit, there is some things to
>>> > discuss on X side; which I will be happy to help with as well.
>>>
>>> Thank you for your help.
>>>
>>> > Henrik's current driver on linux-input is both MT and synaptic-like;
>>> > which is actually my preference as well but brings up important issue.
>>> >  Do we modify xf86-input-wacom to be compatible with synpatic-like
>>> > input events or do we work with distributions to develop rules to
>>> > re-direct wacom "touch" input devices over to xf86-input-synaptics?
>>>
>>> I'd like to know Peter's answer to this question. It is not purely a
>>> Wacom driver decision, I think.
>>
>> AFAICT, the device is exported as a separate device, right? If so, there's
>> no need to hook the wacom driver onto it - we just treat it as a touchpad
>> and hook the synaptics driver onto it.
>>
>
> Yes, on both Bamboo's and Tablet PC's, the exported device is nicely
> isolated.  In Bamboo's case, its very much like a standard touchpad
> (x/y/pressure+4 buttons).  For Tablet PC's, its very much like a
> buttonless touchpad.
>
> Some pros/cons for having xf86-input-synaptics handle wacom touch devices.
>
> Pros:
> * Get synaptics gesture support immediately (edge scrolling, two
> finger scrolling).
> * Get gnome-mouse-properties (and similar) GUI configuration support
> (I can finally enable Lefty mode from a GUI!)
> * It will force us to be Synaptics compatible.  This allows switching
> to xf86-input-multitouch driver and get their gestures (swipes,
> pinching, 3-fingers, etc).  Or at least it keeps us closer to
> compatible to what ever client-side gesture engines are coming up.
>
> Cons:
> * ISDV4 devices requires some touchpad logic in xf86-input-wacom
> anyways (not a code savings)
> * User would lose xf86-input-wacom's advanced button remapping.
>
> My suggestion?
>
> * Make touchpad-like wacom devices to use events that are
> synaptics-like (no multiplexing, no serial/channel #'s, change way
> BTN_TOOL_*'s are used, use MT events for 2 finger HW, etc).  This
> means specifically Bamboo and Tablet PC's.  Since Tablet PC code has
> already shipped in a kernel, we need a roadmap of how and when to
> convert over.
> * Modify xf86-input-wacom so that it can handle todays ISDV4/TabletPC
> version of touchpads and also make it compatible with synaptics-like
> touchpads.  Since its backwards/forwards compatible, that roadmap for
> TabletPC can be change it today.
> * Decide which X driver we prefer as default and then let user do any
> xorg.conf.d modifications if they prefer a specific pro/con item
> above.
>
> Chris
>

Hi,

I predict howls of anguish if the Bamboo P&T's pad (tablet buttons)
can not be programmed like every other Wacom tablet.

Dave

--
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] xf86-input-wacom and Waltop tablets

[Favux ...]

On Sat, Sep 4, 2010 at 4:20 AM, Nikolai Kondrashov  wrote:
> Hello everyone,
>
> I see you have some code for Waltop tablets in xf86-input-wacom, taken from
> the manufacturer's driver (which is in turn based on the Wacom driver).
> However, the kernel part of this driver didn't get it into the kernel.
> Although, as Peter Hutterer says, Timo Aaltonen did something regarding
> this.
>
> Unaware of Timo's work, I have recently added kernel support [1] for 5 (3 if
> you discount version differences) Waltop models. However, it is aimed for
> xf86-input-evdev support and thus most of them use HID_QUIRK_MULTI_INPUT to
> route all the report IDs to separate event devices digestible by this
> driver. I'm not sure if that would harm xf86-input-wacom or not, though.
>
> Still, I would like to make the Waltop tablets supported by xf86-input-wacom
> too. I'm prepared to either take over or help with Timo's work or tune both
> my kernel driver and xf86-input-wacom to compatibility.
>
> I have periodical (although short) access to the models I have supported and
> I think I could find a few more.
>
> What would you like me do?
>
> Thank you for your attention.
>
> Sincerely,
> Nick
>
> [1] 
> http://git.kernel.org/?p=linux/kernel/git/jikos/hid.git;f=drivers/hid/hid-waltop.c;hb=refs/heads/for-next
>
Hi Nikolai,

That sounds great.

In case you didn't find it here is a link to what I think is some of
Timo's preliminary Waltop work:
http://users.tkk.fi/~tjaalton/foo/waltop.diff

Dave

--
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Wacom Intuos4 LED userland app

[Favux ...]

On Tue, Aug 24, 2010 at 10:05 AM, Christoph Karg  wrote:
> Am Montag 23 August 2010, 02:50:37 schrieben Sie:
>> Hi Christoph,
>>
>> By the way here are all the Intuos4 Product ID's I'm aware of:
>>
>> ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b8",
>> SYMLINK+="input/tablet-intuos4-4x6"
>> ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00b9",
>> SYMLINK+="input/tablet-intuos4-6x9"
>> ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00ba",
>> SYMLINK+="input/tablet-intuos4-8x13"
>> ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00bb",
>> SYMLINK+="input/tablet-intuos4-12x19"
>> ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00bc",
>> SYMLINK+="input/tablet-intuos4-wl-usb"
>> ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00bd",
>> SYMLINK+="input/tablet-intuos4-wl"
>>
>> Favux
>
> Hi Favux,
>
> I inserted the id's in order to enable auto detection. The modified version of
> WacomIntuos4LED.cpp is attached. However I was not able to test it, since I do
> not own the respective tablets.
>
> Christoph
>

Hi Christoph,

OK, two Intuos4 users have tested your OLED code so far and it works
for them!  : )

I'm a little surprised that there haven't been more, but we'll see.

I suggest changing the line in the README from "the wacom driver must
be reloaded after usage of the software" to "the wacom usb driver
(wacom.ko) must be unloaded before usage of the software and then
reloaded".  Both users were confused by the first version.

Also I gather you want the unpacked tar folder placed in
/home/username and then just run the script from the folder.  Is that
correct?

Thanks again.

Dave

--
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Waltop (VisTablet PenPad) support

[Favux ...]

On Mon, Sep 6, 2010 at 10:15 AM, H:S /he29  wrote:
>> Could you please try with my Waltop kernel driver?
>> You could simply build and run a "waltop" or "for-next" branch of Jiri
>> Kosina repository
>> here: http://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
>> Alternatively, theoretically, I can provide patches for your kernel
>> version.
>
> I'm not much familiar with git and it appears to me that I just probably
> downloaded & compiled vanilla linux kernel; I don't know how to select
> other branches or whatever else I should do with this.. In the end,
> patches compatible with kernel 2.6.36-rc3 would be probably better. ^^
>
> There's however one other thing that surprised me - I've just noticed,
> that the wacom kernel module isn't even loaded, the tablet just works
> without it (and loading it manually doesn't change anything). So is the
> Waltop tablet (without the manufacturer's kernel patch) acting as some
> universal HID compatible "mouse", which just happen to be compatible with
> xf86-input-wacom driver, or what?
>
>
>> Regarding the settings. What about using "input_absinfo" "resolution"
>> field?
>> ...
>
> I'm not a developer, so I don't have any idea what do you mean by that. :)
> I was talking about the hard-coded values in xf86-wacom-input/src/wcmUSB.c
> - it appears to me, that settings for Waltop tablets are currently
> assigned to some random Wacom models, so they should be corrected or
> autodetected.. but as Waltop doesn't seem to be cooperating, it would take
> some time to get the right values for all of the devices and I don't know,
> how problematic such autodetection could be :)
>
> Martin
>

Hi Nikolai,

I'm having the same problem as Martin.  When I clone your git I just
see a vanilla kernel hid section and can't find your hid-waltop.c in
it anywhere.  Haven't bothered to figure out what kernel version it
is.  If I use your other link I have the hid-waltop.c and the
hid-ids.h, but with line numbers.

If I could get a clean copy of your current hid-waltop.c and the
hid-ids.h (or a patch for the hid-ids.h) I'm reasonably sure I could
talk Ubuntu users through patching a vanilla version of their current
kernel to generate a hid-waltop.ko they could test with.

Dave

--
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Waltop (VisTablet PenPad) support

[Favux ...]

On Mon, Sep 6, 2010 at 3:34 PM, Nikolai Kondrashov  wrote:
>
> The hid-waltop.c and hid-ids.h changes won't be enough, unfortunately.  You
> could take my patches from my reply to Martin, if the list maintainer
> approves it. Otherwise I could send them to you personally.
>
> Sincerely,
> Nick

Hi Nick,

Ouch!  We just figured out how to get them from raw.  What else is
needed?  We'd be trying to compile the hid-waltop.ko for the Lucid
2.6.32 kernel.  Please send the changes.

Thanks for answering.

Dave

--
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Synpatics taking over some of the devices

[Favux ...]

On Sun, Sep 19, 2010 at 12:20 AM, Giuseppe Bilotta
 wrote:
> On Sun, Sep 19, 2010 at 12:36 AM, Chris Bagwell  wrote:
>>
>>
>> On Sep 18, 2010, at 4:16 PM, Giuseppe Bilotta  
>> wrote:
>>
>>> Hello all,
>>>
>>> I have a Bamboo Pen & Touch, for which I'm using the latest
>>> development versions of the kernel driver (0.8.8-8) and the latest
>>> version of the xf86-input-wacom driver (and by last I mean the git
>>> version from Sep 7 this year, git pull tells me there are no new
>>> commits). When I plug the device in, I get 5 devices in xinput: Pen
>>> stylus, Pen eraser, Finger, Finger pad, Finger touch. These devices
>>> are all managed by the xf86-input-wacom driver, _except_ for the
>>> Finger device which is managed by  the _synaptics_ driver.
>>>
>>> Since I have an up-to-date Debian unstable on this machine, I use
>>> xorg.conf.d configuration mechanism for Xorg, and I placed the
>>> wacom.conf snipped (distributed with xf86-input-wacom) into my
>>> /etc/X11/xorg.conf.d directory so that it takes precedent on anything
>>> else; however, synaptics still takes over that device. I'm not sure if
>>> this actually disturbs much while using the board as a touchpad (I
>>> mostly use the pen feature), but it does get annoying because when I
>>> unplug the tablet, even the built-in touchpad in my laptop disappears
>>> (as the synaptics driver gets unloaded).
>>>
>>> So my question is the following: is this a wacom bug (is it exposing
>>> one device more than necessary?), a synpatics bug (is it taking over
>>> devices it shouldn't?), or a misconfiguration issue in Xorg that can
>>> be solved in some particular way?
>>>
>>
>> The kernel only exposes two input devices. One for pen/eraser and one for 
>> touchpad. On X side there should be 4 devices: pen, eraser, touch, and pad.
>>
>> My guess is your debian is somehow adding an unneeded symlink to an extra 
>> /dev/input device that is confusing things and being treated as a touchpad.  
>> Looking at contents of you /dev/input dir and your Xorg.log should give 
>> further clues.
>
> I don't have symlinks in /dev/input (well I do in
> /dev/input/by-{path,id} but that's intentional and standard, if I
> understand these things correctly) so there something else going on,
> especially considering that devices are added to Xorg with the udev
> callbacks and not by a simple enumeration of what's in /dev/input. So
> aside from the keyboard, webcam and accelerometer (which are either
> unhandled or handled by the standard evdev drivers), these are the
> devices that involve wacom and synaptics (and I must say that by
> looking at the Xorg log it's not always clear what ends up handling
> what ...):
>
> The first device is Wacom BambooFun 2FG 4x5 Pen (/dev/input/event9),
> which gets handled by the wacom module, and I get two Xorg devices,
> stylus and eraser. (This is correct, as far as I can tell, aside from
> the double application of the Wacom class, which I guess means I have
> a copy of the wacom conf elsewhere, I'll see into this)
>
> The next device is _still_ the Pen, this time in the form of
> /dev/input/mouse2 -- after going over the logs for the umpteenth time,
> I think this is something that deserves a deeper look.
> /dev/input/mouse2 (which is _not_ a symlink, btw) is not handled by
> Xorg because nothing reclaims it.
>
> Then we have Wacom BambooFun 2FG 4x5 Finger (/dev/input/event10),
> which gets handled by wacom again, and I get the touch and pad
> devices. This is correct, again.
>
> The next device is _still_ the Finger, but this time as
> /dev/input/mouse3, and _this_ is what gets handled by synaptics. Now
> the funny thing that happens is that while Xorg thinks that the
> synaptics driver is driving /dev/input/mouse3, what really happens is
> this:
>
> (II) Synaptics touchpad driver version 1.3.99
> (--) Wacom BambooFun 2FG 4x5 Finger auto-dev sets device to /dev/input/event7
> (**) Option "Device" "/dev/input/event7"
>
> We have a winner! At this point (the tablet was plugged in before Xorg
> started) Xorg thinks synaptics is driving one device, while synaptics
> is actually driving _another_ device, and more precisely my actual
> touchpad (mouse device: mouse1, event device: event7). This also
> explains why, when I unplug the tablet, my touchpad disappears,
> whereas if the tablet is plugged in _after_ Xorg started, this does
> not happen! However, synaptics still tries to handle the Wacom Finger
> device /dev/input/mouse3.
>
> Plugged before:
>
> (II) config/udev: Adding input device Wacom BambooFun 2FG 4x5 Finger
> (/dev/input/mouse3)
> (**) Wacom BambooFun 2FG 4x5 Finger: Applying InputClass "touchpad catchall"
> (II) LoadModule: "synaptics"
> (II) Loading /usr/local/lib/xorg/modules/input/synaptics_drv.so
> (II) Module synaptics: vendor="X.Org Foundation"
>        compiled for 1.7.7, module version = 1.3.99
>        Module class: X.Org XInput Driver
>        ABI class: X.Org XInput driver, version 7.0
> (II) Synaptics touchpad driver version 

Re: [Linuxwacom-devel] Problem compiling after update to kernel 2.6.36

[Favux ...]

On Sun, Oct 31, 2010 at 10:32 AM, Przemo Firszt  wrote:
> Dnia 2010-10-31, nie o godzinie 09:10 -0500, Favux ... pisze:
> [..]
>> Hi Przemo,
>>
>> On Sun, Oct 31, 2010 at 6:42 AM, Przemo Firszt  wrote:
>>
>> I don't think the code to support the Bamboo P&T's has made it
>> upstream into the 2.6.36 kernel.  If I'm right then for them at least
>> you need to be able to compile linuxwacom for the wacom.ko in 2.6.36.
> [..]
> Hi Favux,
> OK, I didn't know that he wants it for Bamboo.
> Do we have patches that I could push to [1]?
> There is a devel and a "tested" branch for code that is good enough to
> go mainstream.
>
> [1]http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/wacom-kernel;a=shortlog;h=refs/heads/devel
>
> --
> Regards,
> Przemo Firszt
>
>

Hi Prxemo,

Actually I was kind of hoping you could update us.  I gather from this
thread in linuxwacom-devel:
http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTi%3DAgBD-ZifkLW5r%2BfTPSwFg%3D_J%3D4p9YhmR_jbc%2B%40mail.gmail.com&forum_name=linuxwacom-devel
 that Dmitry won't accept the wacom.ko Bamboo code.  Start with Ping's
post on 8-24-10 and Peter's question on 8-25-10.  Ping replies:

"The kernel input tree maintainer, aka Dmitry, will not accept our
patch unless it is MT based.

Henrik has submitted an MT based patch for Bamboo, touch-only model,
recently. We'll see how that one goes."

I haven't heard any update on Henrik's submission.  Peter, Ping, and
Chris probably know what's going on.

Favux

--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Problem compiling after update to kernel 2.6.36

[Favux ...]

On Sun, Oct 31, 2010 at 10:59 AM, Favux ...  wrote:
> On Sun, Oct 31, 2010 at 10:32 AM, Przemo Firszt  wrote:
>> Dnia 2010-10-31, nie o godzinie 09:10 -0500, Favux ... pisze:
>> [..]
>>> Hi Przemo,
>>>
>>> On Sun, Oct 31, 2010 at 6:42 AM, Przemo Firszt  wrote:
>>>
>>> I don't think the code to support the Bamboo P&T's has made it
>>> upstream into the 2.6.36 kernel.  If I'm right then for them at least
>>> you need to be able to compile linuxwacom for the wacom.ko in 2.6.36.
>> [..]
>> Hi Favux,
>> OK, I didn't know that he wants it for Bamboo.
>> Do we have patches that I could push to [1]?
>> There is a devel and a "tested" branch for code that is good enough to
>> go mainstream.
>>
>> [1]http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/wacom-kernel;a=shortlog;h=refs/heads/devel
>>
>> --
>> Regards,
>> Przemo Firszt
>>
>>
>
> Hi Prxemo,
>
> Actually I was kind of hoping you could update us.  I gather from this
> thread in linuxwacom-devel:
> http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTi%3DAgBD-ZifkLW5r%2BfTPSwFg%3D_J%3D4p9YhmR_jbc%2B%40mail.gmail.com&forum_name=linuxwacom-devel
>  that Dmitry won't accept the wacom.ko Bamboo code.  Start with Ping's
> post on 8-24-10 and Peter's question on 8-25-10.  Ping replies:
>
> "The kernel input tree maintainer, aka Dmitry, will not accept our
> patch unless it is MT based.
>
> Henrik has submitted an MT based patch for Bamboo, touch-only model,
> recently. We'll see how that one goes."
>
> I haven't heard any update on Henrik's submission.  Peter, Ping, and
> Chris probably know what's going on.
>
> Favux
>

Oops, sorry about the typo in your name.

Favux

--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] linuxwacom: add 3-new-bambooPT-models

[Favux ...]

For linuxwacom's wacom_wac.c and wcmUSB.c.

Adds three new Bamboo Pen & Touch models:

Bamboo Comic Medium                             (CTH661/S1; Product ID = 0xd8)
Bamboo P & T Special Edition Small          (CTH461/L; Product ID = 0xdA)
Bamboo P & T Special Edition Medium       (CTH661; Product ID = 0xdB)

Signed-off-by: David Foley

Dave
? 3-new-bambooPT-models.patch
Index: src/2.6.30/wacom_wac.c
===
RCS file: /cvsroot/linuxwacom/linuxwacom-prod/src/2.6.30/wacom_wac.c,v
retrieving revision 1.6
diff -u -r1.6 wacom_wac.c
--- src/2.6.30/wacom_wac.c	12 Oct 2010 17:56:37 -	1.6
+++ src/2.6.30/wacom_wac.c	10 Nov 2010 19:40:49 -
@@ -1325,6 +1325,12 @@
 	{ "Wacom BambooFun 2FG 6x8", WACOM_PKGLEN_BBFUN,  21648, 13530, 1023, 63, BAMBOO_PT };
 static struct wacom_features wacom_features_0xD0 =
 	{ "Wacom Bamboo 2FG", WACOM_PKGLEN_BBFUN, 14720,  9200, 1023, 63, BAMBOO_PT };
+static struct wacom_features wacom_features_0xD8 =
+	{ "Wacom Bamboo Comic 2FG", WACOM_PKGLEN_BBFUN,   21648, 13530, 1023, 63, BAMBOO_PT };
+static struct wacom_features wacom_features_0xDA =
+	{ "Wacom Bamboo 2FG 4x5 SE", WACOM_PKGLEN_BBFUN,  14720,  9200, 1023, 63, BAMBOO_PT };
+static struct wacom_features wacom_features_0xD8 =
+	{ "Wacom Bamboo 2FG 6x8 SE", WACOM_PKGLEN_BBFUN,  21648, 13530, 1023, 63, BAMBOO_PT };
 static const struct wacom_features wacom_features_0x20 =
 	{ "Wacom Intuos 4x5", WACOM_PKGLEN_INTUOS,12700, 10600, 1023, 31, INTUOS };
 static const struct wacom_features wacom_features_0x21 =
@@ -1470,6 +1476,9 @@
 	{ USB_DEVICE_WACOM(0xD2) },
 	{ USB_DEVICE_WACOM(0xD3) },
 	{ USB_DEVICE_WACOM(0xD0) },
+	{ USB_DEVICE_WACOM(0xD8) },
+	{ USB_DEVICE_WACOM(0xDA) },
+	{ USB_DEVICE_WACOM(0xDB) },
 	{ USB_DEVICE_WACOM(0x41) },
 	{ USB_DEVICE_WACOM(0x42) },
 	{ USB_DEVICE_WACOM(0x43) },
Index: src/xdrv/wcmUSB.c
===
RCS file: /cvsroot/linuxwacom/linuxwacom-prod/src/xdrv/wcmUSB.c,v
retrieving revision 1.29
diff -u -r1.29 wcmUSB.c
--- src/xdrv/wcmUSB.c	1 Oct 2010 21:10:03 -	1.29
+++ src/xdrv/wcmUSB.c	10 Nov 2010 19:40:50 -
@@ -484,6 +484,9 @@
 	{ 0xD3, 2540, 2540, &usbBamboo }, /* CTL-660 */
 	{ 0xD2, 2540, 2540, &usbBamboo }, /* CTL-461/S */
 	{ 0xD0, 2540, 2540, &usbBamboo }, /* Bamboo Touch */
+	{ 0xD8, 2540, 2540, &usbBamboo }, /* CTH-661/S1 */
+	{ 0xDA, 2540, 2540, &usbBamboo }, /* CTH-461/L */
+	{ 0xDB, 2540, 2540, &usbBamboo }, /* CTH-661 */
 
 	{ 0xB0, 5080, 5080, &usbIntuos3}, /* Intuos3 4x5 */
 	{ 0xB1, 5080, 5080, &usbIntuos3}, /* Intuos3 6x8 */
--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] xf86-input-wacom: add 3-new-bambooPT-models

[Favux ...]

For xf86-input-wacom's wcmUSB.c.

Adds three new Bamboo Pen & Touch models:

Bamboo Comic Medium (CTH661/S1; Product ID = 0xd8)
Bamboo P & T Special Edition Small  (CTH461/L; Product ID = 0xdA)
Bamboo P & T Special Edition Medium (CTH661; Product ID = 0xdB)

Dave
From dd40a75938a02df975a2fd8b3f1e6bfa0320b35b Mon Sep 17 00:00:00 2001
From: David 
Date: Wed, 10 Nov 2010 11:21:58 -0600
Subject: [PATCH] wcmUSB.c:  3-new-bambooPT-models

Adds 3 new Bamboo Pen & Touch models.  Supporting changes to linuxwacom wacom_wac.c also needed.

Signed-off-by: David Foley
---
 src/wcmUSB.c |3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/src/wcmUSB.c b/src/wcmUSB.c
index 4d8a0fb..d5a441d 100644
--- a/src/wcmUSB.c
+++ b/src/wcmUSB.c
@@ -185,6 +185,9 @@ static struct
 	{ WACOM_VENDOR_ID, 0xD3, 2540, 2540, &usbBamboo }, /* CTL-660 */
 	{ WACOM_VENDOR_ID, 0xD2, 2540, 2540, &usbBamboo }, /* CTL-461/S */
 	{ WACOM_VENDOR_ID, 0xD0, 2540, 2540, &usbBamboo }, /* Bamboo Touch */
+	{ WACOM_VENDOR_ID, 0xD8, 2540, 2540, &usbBamboo }, /* CTH-661/S1 */
+	{ WACOM_VENDOR_ID, 0xDA, 2540, 2540, &usbBamboo }, /* CTH-461/L */
+	{ WACOM_VENDOR_ID, 0xDB, 2540, 2540, &usbBamboo }, /* CTH-661 */
 
 	{ WACOM_VENDOR_ID, 0x20, 2540, 2540, &usbIntuos }, /* Intuos 4x5 */
 	{ WACOM_VENDOR_ID, 0x21, 2540, 2540, &usbIntuos }, /* Intuos 6x8 */
-- 
1.7.1

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] linuxwacom: add 3-new-bambooPT-models

[Favux ...]

On Wed, Nov 10, 2010 at 2:50 PM, Favux ...  wrote:
> For linuxwacom's wacom_wac.c and wcmUSB.c.
>
> Adds three new Bamboo Pen & Touch models:
>
> Bamboo Comic Medium                             (CTH661/S1; Product ID = 0xd8)
> Bamboo P & T Special Edition Small          (CTH461/L; Product ID = 0xdA)
> Bamboo P & T Special Edition Medium       (CTH661; Product ID = 0xdB)
>
> Signed-off-by: David Foley
>
> Dave
>

Corrected typo in first patch sent.

Dave
? 3-new-bambooPT-models.patch
Index: src/2.6.30/wacom_wac.c
===
RCS file: /cvsroot/linuxwacom/linuxwacom-prod/src/2.6.30/wacom_wac.c,v
retrieving revision 1.6
diff -u -r1.6 wacom_wac.c
--- src/2.6.30/wacom_wac.c	12 Oct 2010 17:56:37 -	1.6
+++ src/2.6.30/wacom_wac.c	10 Nov 2010 21:21:54 -
@@ -1325,6 +1325,12 @@
 	{ "Wacom BambooFun 2FG 6x8", WACOM_PKGLEN_BBFUN,  21648, 13530, 1023, 63, BAMBOO_PT };
 static struct wacom_features wacom_features_0xD0 =
 	{ "Wacom Bamboo 2FG", WACOM_PKGLEN_BBFUN, 14720,  9200, 1023, 63, BAMBOO_PT };
+static struct wacom_features wacom_features_0xD8 =
+	{ "Wacom Bamboo Comic 2FG", WACOM_PKGLEN_BBFUN,   21648, 13530, 1023, 63, BAMBOO_PT };
+static struct wacom_features wacom_features_0xDA =
+	{ "Wacom Bamboo 2FG 4x5 SE", WACOM_PKGLEN_BBFUN,  14720,  9200, 1023, 63, BAMBOO_PT };
+static struct wacom_features wacom_features_0xDB =
+	{ "Wacom Bamboo 2FG 6x8 SE", WACOM_PKGLEN_BBFUN,  21648, 13530, 1023, 63, BAMBOO_PT };
 static const struct wacom_features wacom_features_0x20 =
 	{ "Wacom Intuos 4x5", WACOM_PKGLEN_INTUOS,12700, 10600, 1023, 31, INTUOS };
 static const struct wacom_features wacom_features_0x21 =
@@ -1470,6 +1476,9 @@
 	{ USB_DEVICE_WACOM(0xD2) },
 	{ USB_DEVICE_WACOM(0xD3) },
 	{ USB_DEVICE_WACOM(0xD0) },
+	{ USB_DEVICE_WACOM(0xD8) },
+	{ USB_DEVICE_WACOM(0xDA) },
+	{ USB_DEVICE_WACOM(0xDB) },
 	{ USB_DEVICE_WACOM(0x41) },
 	{ USB_DEVICE_WACOM(0x42) },
 	{ USB_DEVICE_WACOM(0x43) },
Index: src/xdrv/wcmUSB.c
===
RCS file: /cvsroot/linuxwacom/linuxwacom-prod/src/xdrv/wcmUSB.c,v
retrieving revision 1.29
diff -u -r1.29 wcmUSB.c
--- src/xdrv/wcmUSB.c	1 Oct 2010 21:10:03 -	1.29
+++ src/xdrv/wcmUSB.c	10 Nov 2010 21:21:55 -
@@ -484,6 +484,9 @@
 	{ 0xD3, 2540, 2540, &usbBamboo }, /* CTL-660 */
 	{ 0xD2, 2540, 2540, &usbBamboo }, /* CTL-461/S */
 	{ 0xD0, 2540, 2540, &usbBamboo }, /* Bamboo Touch */
+	{ 0xD8, 2540, 2540, &usbBamboo }, /* CTH-661/S1 */
+	{ 0xDA, 2540, 2540, &usbBamboo }, /* CTH-461/L */
+	{ 0xDB, 2540, 2540, &usbBamboo }, /* CTH-661 */
 
 	{ 0xB0, 5080, 5080, &usbIntuos3}, /* Intuos3 4x5 */
 	{ 0xB1, 5080, 5080, &usbIntuos3}, /* Intuos3 6x8 */
--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] xf86-input-wacom: add 3-new-bambooPT-models

[Favux ...]

Hi Chris,

On Wed, Nov 10, 2010 at 3:38 PM, Chris Bagwell  wrote:
> On Wed, Nov 10, 2010 at 2:53 PM, Favux ...  wrote:
>> For xf86-input-wacom's wcmUSB.c.
>>
>> Adds three new Bamboo Pen & Touch models:
>>
>> Bamboo Comic Medium                     (CTH661/S1; Product ID = 0xd8)
>> Bamboo P & T Special Edition Small      (CTH461/L; Product ID = 0xdA)
>> Bamboo P & T Special Edition Medium     (CTH661; Product ID = 0xdB)
>>
>
> Special Edition?  Comic?  I feel my hardware is out dated all the sudden!
>
> There is 1 piece remaining in xf86-input-wacom were we check tablet_id
> <= 0xd0 and >= 0xd3 and do something special... and I happen to just
> have added that in this month.
>
> If you use linuxwacom driver then no harm.  If you instead patch Linux
> 2.6.37 (pre-release obviously), I need to fix xf86-input-wacom.  We
> could remap these new values to a tablet_id of 0xd0 always or I'll
> probably just find a way to remove the check altogether.

Sounds like we need you to fix xf86-input-wacom's check tablet_id then.

> BTW, have the users mentioned any differences to these tablets;
> especially on maximum X/Y values?  They can look at their Xorg.0.log
> file for similar line:
>
> Wacom Bamboo 2FG 4x5 Pen eraser: top X=0 top Y=0 bottom X=14720 bottom
> Y=9200 resol X=2540 resol Y=2540
>
> When they are patching wacom_wac.c file to add their USB ID's, the
> hard coded X/Y values should match whats returned from this log file.

Seems to be working OK.

> Chris
>

Thanks

Dave

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] xf86-input-wacom: add 3-new-bambooPT-models

[Favux ...]

On Wed, Nov 10, 2010 at 10:53 PM, Peter Hutterer
 wrote:
> On Wed, Nov 10, 2010 at 03:38:09PM -0600, Chris Bagwell wrote:
>> On Wed, Nov 10, 2010 at 2:53 PM, Favux ...  wrote:
>> > For xf86-input-wacom's wcmUSB.c.
>> >
>> > Adds three new Bamboo Pen & Touch models:
>> >
>> > Bamboo Comic Medium                     (CTH661/S1; Product ID = 0xd8)
>> > Bamboo P & T Special Edition Small      (CTH461/L; Product ID = 0xdA)
>> > Bamboo P & T Special Edition Medium     (CTH661; Product ID = 0xdB)
>> >
>>
>> Special Edition?  Comic?  I feel my hardware is out dated all the sudden!
>>
>> There is 1 piece remaining in xf86-input-wacom were we check tablet_id
>> <= 0xd0 and >= 0xd3 and do something special... and I happen to just
>> have added that in this month.
>>
>> If you use linuxwacom driver then no harm.  If you instead patch Linux
>> 2.6.37 (pre-release obviously), I need to fix xf86-input-wacom.  We
>> could remap these new values to a tablet_id of 0xd0 always or I'll
>> probably just find a way to remove the check altogether.
>
> can we abstract the tablet_id checks with bitmasks?
>
> what we have in wcmDeviceTypeKeys is the right way to go, have a list of
> tablet_ids and assign various bitflags to it. Then use the bitflags instead
> of the ID.
>
> something like this should be possible here as well, isn't it? (haven't
> looked at the code in detail now)
>
>>
>> BTW, have the users mentioned any differences to these tablets;
>> especially on maximum X/Y values?  They can look at their Xorg.0.log
>> file for similar line:
>>
>> Wacom Bamboo 2FG 4x5 Pen eraser: top X=0 top Y=0 bottom X=14720 bottom
>> Y=9200 resol X=2540 resol Y=2540
>
> long-term we should probably get the resolution from the kernel driver
> instead of hardcoding it in the X driver. the ability to do that has been in
> for a few kernel versions now.
>
> Cheers,
>  Peter
>
>> When they are patching wacom_wac.c file to add their USB ID's, the
>> hard coded X/Y values should match whats returned from this log file.
>

Hi Peter,

These (the changes to wacom_wac.c and xf86-input-wacom's wcmUSB.c) are
the minimum to turn these tablets "on".  Just simple additions.  I
basically wanted to call them to the project's attention, since we're
getting more requests for support.

I didn't want to attempt to change the code logic in wcmUSB.c at about
line #498:

if ((common->tablet_id >= 0xd0) && (common->tablet_id <= 0xd3))

Especially since Chris is working on it.  I get that he wants to
exclude the Bamboo Pen (0xD4) since it's stylus only with no touch.
This also applies to a few places in linuxwacom.  After Chris or who
ever addresses this then we should probably also add to wcmValidate.c
at about line #277:

case 0xD8:  /* Bamboo with 2FGT */
case 0xDA:  /* Bamboo with 2FGT */
case 0xDB:  /* Bamboo with 2FGT */

The additions include the coordinates for the kernel.

Dave

--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH] xsetwacom: rename ClickForce to Threshold.

[Favux ...]

On Thu, Nov 18, 2010 at 4:56 PM, Ping Cheng  wrote:
> On Thu, Nov 18, 2010 at 2:49 PM, Peter Hutterer
>  wrote:
>> Click force is a normalised scale from 0 - 21 for the pressure threshold. If
>> we want to expose this, let the client UI's do this in their respective
>> interfaces, not in xsetwacom.
>>
>> Rename to Threshold, which is the normalised threshold in a 0-2048 range
>> and the data the device actually puts out.
>>
>> Signed-off-by: Peter Hutterer 
>
> Acked-by: Ping Cheng 
>
> Thank you, Peter.
>
> Ping
>
>> ---
>>  tools/xsetwacom.c |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/tools/xsetwacom.c b/tools/xsetwacom.c
>> index f75fee2..84dd188 100644
>> --- a/tools/xsetwacom.c
>> +++ b/tools/xsetwacom.c
>> @@ -534,7 +534,7 @@ static param_t parameters[] =
>>                .prop_flags = PROP_FLAG_BOOLEAN
>>        },
>>        {
>> -               .name = "ClickForce",
>> +               .name = "Threshold",
>>                .desc = "Sets tip/eraser pressure threshold "
>>                "(default is 27)",
>>                .prop_name = WACOM_PROP_PRESSURE_THRESHOLD,
>> --
>> 1.7.3.2
>>
>>
>> --
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today
>> http://p.sf.net/sfu/msIE9-sfdev2dev
>> ___
>> Linuxwacom-devel mailing list
>> Linuxwacom-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>>
>
> --
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today
> http://p.sf.net/sfu/msIE9-sfdev2dev
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

Hi,

Sorry to pester, but let me make sure I'm clear.  If my device has
2048 pressure levels I should have a default Threshold of about 27.
If 0 is a pressure level wouldn't my range be 0-2047?  Similarly if it
is reporting 1024 pressure levels the default Threshold would be about
14 with a range of 0-1023.  Do I have it right?

Dave

PS:  If this is correct, then this brings the Wacom tablet in line
with the Aiptek and WizardPen.

--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH] xsetwacom: rename ClickForce to Threshold.

[Favux ...]

On Thu, Nov 18, 2010 at 7:25 PM, Peter Hutterer
 wrote:
> On Thu, Nov 18, 2010 at 07:17:29PM -0600, Favux ... wrote:
>> On Thu, Nov 18, 2010 at 4:56 PM, Ping Cheng  wrote:
>> > On Thu, Nov 18, 2010 at 2:49 PM, Peter Hutterer
>> >  wrote:
>> >> Click force is a normalised scale from 0 - 21 for the pressure threshold. 
>> >> If
>> >> we want to expose this, let the client UI's do this in their respective
>> >> interfaces, not in xsetwacom.
>> >>
>> >> Rename to Threshold, which is the normalised threshold in a 0-2048 range
>> >> and the data the device actually puts out.
>> >>
>> >> Signed-off-by: Peter Hutterer 
>> >
>> > Acked-by: Ping Cheng 
>> >
>> > Thank you, Peter.
>> >
>> > Ping
>> >
>> >> ---
>> >>  tools/xsetwacom.c |    2 +-
>> >>  1 files changed, 1 insertions(+), 1 deletions(-)
>> >>
>> >> diff --git a/tools/xsetwacom.c b/tools/xsetwacom.c
>> >> index f75fee2..84dd188 100644
>> >> --- a/tools/xsetwacom.c
>> >> +++ b/tools/xsetwacom.c
>> >> @@ -534,7 +534,7 @@ static param_t parameters[] =
>> >>                .prop_flags = PROP_FLAG_BOOLEAN
>> >>        },
>> >>        {
>> >> -               .name = "ClickForce",
>> >> +               .name = "Threshold",
>> >>                .desc = "Sets tip/eraser pressure threshold "
>> >>                "(default is 27)",
>> >>                .prop_name = WACOM_PROP_PRESSURE_THRESHOLD,
>> >> --
>> >> 1.7.3.2
>> >>
>> >>
>>
>> Hi,
>>
>> Sorry to pester, but let me make sure I'm clear.  If my device has
>> 2048 pressure levels I should have a default Threshold of about 27.
>> If 0 is a pressure level wouldn't my range be 0-2047?
>
> oops, sorry. typo.
>
>> Similarly if it is reporting 1024 pressure levels the default Threshold
>> would be about 14 with a range of 0-1023.  Do I have it right?
>
> no, the point here is that the wacom driver normalises the pressure into the
> 0-2047 range so that _all_ devices export the same range, regardless of the
> actual hardware support.
>
> Cheers,
>  Peter
>

Thank you Peter.  That clears it up for me.   So all devices will
report having a default Threshold of 27!  That explains touch.

--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] xf86-input-wacom: wcmValidateDevice.c-add-3-new-bambooPT-models

[Favux ...]

This patch addresses the issue reported by IRIE Shinsuke in Support
Requests (tracker ID: 3104500) in his 11-19-10 post.  It prevents the
Xorg.0.log from filling with multiple repeated error lines like the
following:

[ 295.384] (EE) WACOM: No touch device found for /dev/input/event5

Reported-by: IRIE Shinsuke 
Tested-by: IRIE Shinsuke 
Signed-off-by: David Foley 

Dave
From ebe64b24a9bec5d8c4c72e675c0ac00d66c09c01 Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Sun, 21 Nov 2010 20:46:45 -0600
Subject: [PATCH] wcmValidateDevice.c:  add 3-new-bambooPT-models

Prevents the Xorg.0.log filling with multiple error lines "No touch device found".

Signed-off-by: David Foley 
---
 src/wcmValidateDevice.c |3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/src/wcmValidateDevice.c b/src/wcmValidateDevice.c
index cde194d..b9a5d70 100644
--- a/src/wcmValidateDevice.c
+++ b/src/wcmValidateDevice.c
@@ -229,6 +229,9 @@ int wcmDeviceTypeKeys(InputInfoPtr pInfo)
 		case 0xD1:  /* Bamboo with 2FGT */
 		case 0xD2:  /* Bamboo with 2FGT */
 		case 0xD3:  /* Bamboo with 2FGT */
+		case 0xD8:  /* Bamboo with 2FGT */
+		case 0xDA:  /* Bamboo with 2FGT */
+		case 0xDB:  /* Bamboo with 2FGT */
 			priv->common->tablet_type |= WCM_2FGT;
 			break;
 
-- 
1.7.1

--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH] Let PROTOCOL_GENERIC take care of future devices

[Favux ...]

Hi Chris and Ping,

No, not all models.  I have a tested by IRIE Shinsuke on the Comic and
mrermia (ubunu forums name) on the Bamboo Special Edition Small
(CTH-461SE).  But not on the Bamboo Special Edition Medium.

Dave

On Sat, Nov 27, 2010 at 2:08 PM, Ping Cheng  wrote:
> On Sat, Nov 27, 2010 at 10:07 AM, Chris Bagwell  wrote:
>> Thats why multiple eyes are good.  I kept trying to find a way to
>> identify generic devices but this way of detecting common value of
>> protocol 4/5 devices is better.
>
> This is not my ideal approach. But, we have to move on.
>
>> This change will also allow newer Bamboo's to work once submitted
>> upstream.  On that topic, should we post Dave's USB ID patches to
>> linux-input?
>
> Did we get a tested-by for each model?
>
>> Reviewed-by: Chris Bagwell 
>
> Thank you.
>
> Ping

--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Support for multiple separate pens hotplug in new X driver with wip patch

[Favux ...]

On Mon, Dec 13, 2010 at 11:17 AM, Chris Bagwell  wrote:
> On Sat, Dec 11, 2010 at 11:59 AM, Alexia Death  wrote:
>> Hi,
>>
>> Second iteration of my patches. These just concentrate on the driver
>> side config snipplet support. I belive prop system hooks and solutions
>> should be a separate issue in a separate patch after this is done. I
>> tried to fix the points Peter commented on and also incorporate
>> support for cursors.
>>
>
> I didn't really review as close as first patch but I've only a small comment.
>
> On the man page, it might be nice to give reason why this is useful.
> something along lines that applications can see unique input per tool
> this way.
>
> Also, the name "hotplug" has always bothered me here.  For some
> reason, it makes me think on-demand-when-tool-used more then creating
> all possible tool inputs when base tablet is hot-plugged in.
>
> I don't really have a better suggestion to use though.
>
> Chris
>
> --
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

> +.B Option \fI"ToolSerial"\fP \fI"number[,pen|airbrush|cursor,label];..."\fP
> +sets the list of serial numbered devices that need to be hotplugged for a 
> physical
> +device. This option is only available on wacom V devices (Intuos series and 
> Cintiq 21U).
> +To see which serial number belongs to a device, you need to run the utility 
> program,
> +xsetwacom, which comes with linuxwacom package.

Change to registered?

> +.B Option \fI"ToolSerial"\fP \fI"number[,pen|airbrush|cursor,label];..."\fP
> +sets the list of serial numbered devices that need to be registered for a 
> physical
> +device. This option is only available on wacom V devices (Intuos series and 
> Cintiq 21U).
> +To see which serial number belongs to a device, you need to run the utility 
> program,
> +xsetwacom, which comes with linuxwacom package.

Dave

--
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Bind programs to keys

[Favux ...]

Hi,

I believe Vu Ngoc San has just written a small daemon that does
something similar for his modification of Christoph Karg's userland
OLED app. for the Intuos4..  It switches the profiles, a modification
he introduced, when changing app.s as in Gimp to Inkscape.  I don't
believe he has posted it yet.

Favux

On Sun, Jan 9, 2011 at 5:01 PM, Peter Hutterer  wrote:
> On Sun, Jan 09, 2011 at 06:13:42PM +0100, Cedric Sodhi wrote:
>> Hi, this is a "wish" i had for the driver that I'd consider very useful.
>> I've recently written a simple bash script which scripts the
>> functionality of the button, an example the button on the wheel changes
>> which keycodes the wheel sumit and hence which function in cotrnols.
>>
>> If anyone is interested I'd like to share it.
>>
>> The problem is, where even that is kind of cumbersome, more complicated
>> interaction because a real pain in the arse. Since the driver will only
>> emit keyboard events, everything will go through X.
>>
>> Right now, I'm using my WM (openbox), to respond to the global keys to
>> control the behaviour. For example the touchring button emits Ctrl +
>> Shift + Alt + T which openbox catches and runs my script on, to change
>> the mappings and give feedback through osd_cat.
>>
>> And whereas I could do the same for all buttons and find the most exotic
>> keybindings to never collide with running programs, it becomes quite
>> cumbersom to continuously remap them, map the bindings in Openbox and so
>> on. The amount of required keybindings which are used NOWHERE else on
>> the system grows exponentially with functionality.
>>
>> All these problems would immediately be solved if, instead of
>> keybindings, actual programs could be bound to keys. It would greatly
>> simply certain methods and give us a great flexibilty to write our own
>> complex behaviour without any effort.
>
> it'd solve this particular problem but open up a new can of worms. Two
> things I can think of right now:
> - security: driver runs as root, so you'd need user management
> - configuration: once you allow to run programs, people will want to start
>  passing arguments, parameters, etc.
>
> besides, AFAICT it doesn't really _solve_ your problem. From what I gather,
> what you want is a application-specific key binding. The ideal way of
> integrating is to have a background daemon that talks to the WM to figure
> out which application is currently in focus and remaps the keys on the
> tablet on-the-fly. That is in fact much easier to write than any custom
> application loading in the driver.
>
> Cheers,
>  Peter
>
> --
> 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
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH] xsetwacom: fix 64-bit issues with MapToOutput

[Favux ...]

Thank you Peter.  That was quick!  :)

Favux

On Sun, Jan 9, 2011 at 8:29 PM, Peter Hutterer  wrote:
> Xlib for XI 1 expects 32 bit properties as long, even if on the given
> machine architecture the size of long is actually 64 bit. Hilarity ensues.n
>
> Convert the floats to longs before passing it to XChangeDeviceProperty.
>
> Signed-off-by: Peter Hutterer 
> ---
> this must be the 10th time this api stupidity has bitten me...
>
> sorry for the cross-post, patches should go to -devel but this is in
> response to a -discuss thread.
>
>  tools/xsetwacom.c |    9 -
>  1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/tools/xsetwacom.c b/tools/xsetwacom.c
> index 72c46ec..26d822f 100644
> --- a/tools/xsetwacom.c
> +++ b/tools/xsetwacom.c
> @@ -1966,13 +1966,15 @@ static void get_button(Display *dpy, XDevice *dev, 
> param_t *param, int argc,
>        XFlush(dpy);
>  }
>
> -static void _set_matrix_prop(Display *dpy, XDevice *dev, const float 
> matrix[9])
> +static void _set_matrix_prop(Display *dpy, XDevice *dev, const float 
> fmatrix[9])
>  {
>        Atom matrix_prop = XInternAtom(dpy, "Coordinate Transformation 
> Matrix", True);
>        Atom type;
>        int format;
>        unsigned long nitems, bytes_after;
>        float *data;
> +       long matrix[9] = {0};
> +       int i;
>
>        if (!matrix_prop)
>        {
> @@ -1980,6 +1982,11 @@ static void _set_matrix_prop(Display *dpy, XDevice 
> *dev, const float matrix[9])
>                return;
>        }
>
> +       /* XI1 expects 32 bit properties (including float) as long,
> +        * regardless of architecture */
> +       for (i = 0; i < sizeof(matrix)/sizeof(matrix[0]); i++)
> +               *(float*)(matrix + i) = fmatrix[i];
> +
>        XGetDeviceProperty(dpy, dev, matrix_prop, 0, 9, False,
>                                AnyPropertyType, &type, &format, &nitems,
>                                &bytes_after, (unsigned char**)&data);
> --
> 1.7.3.4
>
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] TPC button behaviour

[Favux ...]

"on" is default for tablet pc's.  It means that in order for your
stylus buttons to work the tip of the stylus must be in contact with
the screen/digitizer.  "off" is the hover mode where the stylus
buttons will work with the stylus tip in proximity but not actually
touching.

Favux

On Sun, Jan 9, 2011 at 9:56 PM, Peter Hutterer  wrote:
> Can someone explain the intended behaviour of the TPC button to me?
> It doesn't seem to do anything at all and the code for it is a tad
> confusing. Since I don't want to break behaviour, it'd be nice to know what
> I'm actually aiming for when cleaning up this code.  thanks.
>
> Cheers,
>  Peter
>
> --
> 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
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] TPC button behaviour

[Favux ...]

Using xev running linuxwacom 0.8.8-10.

Pressing tablet pc stylus tip to screen.
- just pressing the tip is button 1 press
- releasing the tip is button 1 release

ButtonPress event, serial 32, synthetic NO, window 0x541,
root 0x1a7, subw 0x0, time 1422666889, (68,144), root:(730,200),
state 0x0, button 1, same_screen YES

ButtonRelease event, serial 32, synthetic NO, window 0x541,
root 0x1a7, subw 0x0, time 1422667185, (55,136), root:(717,192),
state 0x100, button 1, same_screen YES


Pressing the tip with stylus button already pressed and releasing it.
- pressing the tip with any other button is that other button but not button
 1
- releasing that button is ???

ButtonPress event, serial 32, synthetic NO, window 0x5c1,
root 0x1a7, subw 0x0, time 1424266672, (98,70), root:(918,376),
state 0x0, button 3, same_screen YES

ButtonRelease event, serial 32, synthetic NO, window 0x5c1,
root 0x1a7, subw 0x0, time 1424266940, (97,74), root:(917,380),
state 0x400, button 3, same_screen YES


Pressing  tablet pc stylus tip to screen & and then pressing stylus button.
- pressing another button with tip already down is that other button
- releasing that other button then is ???

ButtonPress event, serial 35, synthetic NO, window 0x5a1,
root 0x1a7, subw 0x0, time 1423719270, (108,36), root:(917,553),
state 0x0, button 1, same_screen YES

ButtonRelease event, serial 35, synthetic NO, window 0x5a1,
root 0x1a7, subw 0x0, time 1423719326, (106,43), root:(915,560),
state 0x100, button 1, same_screen YES

ButtonPress event, serial 35, synthetic NO, window 0x5a1,
root 0x1a7, subw 0x0, time 1423719326, (106,43), root:(915,560),
state 0x0, button 3, same_screen YES

ButtonRelease event, serial 35, synthetic NO, window 0x5a1,
root 0x1a7, subw 0x0, time 1423719651, (91,59), root:(900,576),
state 0x400, button 3, same_screen YES

On Sun, Jan 9, 2011 at 10:18 PM, Peter Hutterer
 wrote:
>
> right, with current git I don't see any difference in behaviour at all.
>
> a few more detailed questions
> - just pressing the tip is button 1 press
> - releasing the tip is button 1 release
> - pressing the tip with any other button is that other button but not button
>  1
> - releasing that button is ???
> - releasing the tip with any other button pressed is ???
> - pressing another button with tip already down is that other button
> - releasing that other button then is ???
>
> I have my guesses for the three, but I want to hear some independent
> confirmation.
>
> Cheers,
>  Peter
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] Bamboo P&T touch broken with new commits?

[Favux ...]

Cloning the git repository with the latest commits up to and including
"fix logic detecting ABS_MT_SLOT" breaks touch on my Bamboo P&T.  When
the tablet is touched with a finger the pointer immediately slams into
the left side of the monitor along a horizontal line at the height of
wherever the pointer happened to be.  I've never seen that before.  In
other words it doesn't go into a corner, like the left upper corner.

Stylus and pad seem to work fine.

In addition with 'make' there are new warnings:

Making all in tools
make[2]: Entering directory `/home/dave/Desktop/xf86-input-wacom/tools'
  CC xsetwacom.o
xsetwacom.c: In function ‘list_mod’:
xsetwacom.c:908: warning: format ‘%d’ expects type ‘int’, but argument
2 has type ‘long unsigned int’
xsetwacom.c:912: warning: format ‘%d’ expects type ‘int’, but argument
2 has type ‘long unsigned int’
  CCLD   xsetwacom
  CC isdv4-serial-debugger.o
  CCLD   isdv4-serial-debugger
make[2]: Leaving directory `/home/dave/Desktop/xf86-input-wacom/tools'

This is in Ubuntu Maverick (2.6.35 and Xorg 1.9) 64-bit.

Favux

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Bamboo P&T touch broken with new commits?

[Favux ...]

Hi Peter,

Bisection shows it is the 12-21-10 "Merge branch 'multimonitor-purge'"
commit.  Its snapshot xf86-input-wacom-68351da breaks touch.  Although
rather than slamming to the left it jitters horizontally in place over
about 1.5 cm.  The prior commit of the same date "Bamboo tablet does
not report device_id anymore" snapshot xf86-input-wacom-2b9eb3d still
has working touch.

Favux

On Sun, Jan 9, 2011 at 11:53 PM, Peter Hutterer
 wrote:
>
> can you run a bisect over the code to identify which commit broke it?
> three different features got merged, multimonitor removal, the scrollring
> fixes and chris' bamboo patches. Not sure which one caused the bug.
>
> Cheers,
>  Peter
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Bamboo P&T touch broken with new commits?

[Favux ...]

Hi Chris,

I'm pretty sure that's the right commit.  But it was getting awfully late so...

Yes I'm testing input-wacom-0.10.10-1.

Favux

On Mon, Jan 10, 2011 at 8:48 AM, Chris Bagwell  wrote:
> Oh, if I do two finger touch, I'm able to get device type to change to
> 2 but I also get an additional interesting message (the last line in
> this snippet):
>
> [1084191.183] (II) /dev/input/event6 (10:wcmEvent): channel = 0
> [1084191.183] (II) /dev/input/event6 (10:wcmEvent): c=0 i=3 t=2 s=1 x=9130 
> y=701
> 2 b=0 p=0 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=1 st=1084190800 cs=4
> [1084191.183] (II) /dev/input/event6 (10:wcmFilterCoord):
> common->wcmRawSample = 4
> [1084191.183] (II) /dev/input/event6 (10:wcmCheckSuppress): level = 2
> return value = 2
> [1084191.183] (II) /dev/input/event6 (10:commonDispatchDevice): device type = 
> 2
> [1084191.183] (II) /dev/input/event6 (10:commonDispatchDevice): Ignore
> non-movement relative data
>
> So perhaps touch device was set to relative mode at some point during
> init phase.
>
> Chris
>
> On Mon, Jan 10, 2011 at 8:45 AM, Chris Bagwell  wrote:
>> Something about that bi-sect doesn't make sense.  Your pointing to a
>> commit that contains no code.
>>
>> I only have a few minutes with touch pad right now but tried git and
>> can also reproduce.
>>
>> The only thing that looked suspicious in log files is this:
>>
>> [1082669.808] (II) /dev/input/event6 (10:commonDispatchDevice): device type 
>> = 4
>>
>> I believe that says its detected as a cursor device?  There is a case
>> statement for ABS_MT_SLOT that is supposed to set that value correctly
>> that seems not to be working now.
>>
>> Can you confirm if your using wacom-input Bamboo drivers as well?
>> This may be MT specific (I hope).
>>
>> Chris
>>
>> On Mon, Jan 10, 2011 at 2:22 AM, Favux ...  wrote:
>>> Hi Peter,
>>>
>>> Bisection shows it is the 12-21-10 "Merge branch 'multimonitor-purge'"
>>> commit.  Its snapshot xf86-input-wacom-68351da breaks touch.  Although
>>> rather than slamming to the left it jitters horizontally in place over
>>> about 1.5 cm.  The prior commit of the same date "Bamboo tablet does
>>> not report device_id anymore" snapshot xf86-input-wacom-2b9eb3d still
>>> has working touch.
>>>
>>> Favux
>>>
>>> On Sun, Jan 9, 2011 at 11:53 PM, Peter Hutterer
>>>  wrote:
>>>>
>>>> can you run a bisect over the code to identify which commit broke it?
>>>> three different features got merged, multimonitor removal, the scrollring
>>>> fixes and chris' bamboo patches. Not sure which one caused the bug.
>>>>
>>>> Cheers,
>>>>  Peter
>>>>
>>>
>>> --
>>> 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
>>> Linuxwacom-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>>>
>>
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Bamboo P&T touch broken with new commits?

[Favux ...]

Hi Chris,

Pad was switched to absolute device.  See the 12-15-10 commit "Switch
the pad to forced absolute mode":
http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/xf86-input-wacom;a=commit;h=ce98b0a20862291892fc7a3110e4779cd69dd5ba
 And the commits around it.

Favux

On Mon, Jan 10, 2011 at 9:39 AM, Chris Bagwell  wrote:
> In reply to myself... oh yeah, the touchpad is a relative device. :-)
>
> but maybe something in this area has changed slightly and needs a look
> at.  I'll try to dig deeper when I have a minute.
>
> Chris
>
> On Mon, Jan 10, 2011 at 8:48 AM, Chris Bagwell  wrote:
>> Oh, if I do two finger touch, I'm able to get device type to change to
>> 2 but I also get an additional interesting message (the last line in
>> this snippet):
>>
>> [1084191.183] (II) /dev/input/event6 (10:wcmEvent): channel = 0
>> [1084191.183] (II) /dev/input/event6 (10:wcmEvent): c=0 i=3 t=2 s=1 x=9130 
>> y=701
>> 2 b=0 p=0 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=1 st=1084190800 cs=4
>> [1084191.183] (II) /dev/input/event6 (10:wcmFilterCoord):
>> common->wcmRawSample = 4
>> [1084191.183] (II) /dev/input/event6 (10:wcmCheckSuppress): level = 2
>> return value = 2
>> [1084191.183] (II) /dev/input/event6 (10:commonDispatchDevice): device type 
>> = 2
>> [1084191.183] (II) /dev/input/event6 (10:commonDispatchDevice): Ignore
>> non-movement relative data
>>
>> So perhaps touch device was set to relative mode at some point during
>> init phase.
>>
>> Chris
>>
>> On Mon, Jan 10, 2011 at 8:45 AM, Chris Bagwell  wrote:
>>> Something about that bi-sect doesn't make sense.  Your pointing to a
>>> commit that contains no code.
>>>
>>> I only have a few minutes with touch pad right now but tried git and
>>> can also reproduce.
>>>
>>> The only thing that looked suspicious in log files is this:
>>>
>>> [1082669.808] (II) /dev/input/event6 (10:commonDispatchDevice): device type 
>>> = 4
>>>
>>> I believe that says its detected as a cursor device?  There is a case
>>> statement for ABS_MT_SLOT that is supposed to set that value correctly
>>> that seems not to be working now.
>>>
>>> Can you confirm if your using wacom-input Bamboo drivers as well?
>>> This may be MT specific (I hope).
>>>
>>> Chris
>>>
>>> On Mon, Jan 10, 2011 at 2:22 AM, Favux ...  wrote:
>>>> Hi Peter,
>>>>
>>>> Bisection shows it is the 12-21-10 "Merge branch 'multimonitor-purge'"
>>>> commit.  Its snapshot xf86-input-wacom-68351da breaks touch.  Although
>>>> rather than slamming to the left it jitters horizontally in place over
>>>> about 1.5 cm.  The prior commit of the same date "Bamboo tablet does
>>>> not report device_id anymore" snapshot xf86-input-wacom-2b9eb3d still
>>>> has working touch.
>>>>
>>>> Favux
>>>>
>>>> On Sun, Jan 9, 2011 at 11:53 PM, Peter Hutterer
>>>>  wrote:
>>>>>
>>>>> can you run a bisect over the code to identify which commit broke it?
>>>>> three different features got merged, multimonitor removal, the scrollring
>>>>> fixes and chris' bamboo patches. Not sure which one caused the bug.
>>>>>
>>>>> Cheers,
>>>>>  Peter
>>>>>
>>>>
>>>> --
>>>> 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
>>>> Linuxwacom-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>>>>
>>>
>>
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Bamboo P&T touch broken with new commits?

[Favux ...]

Never mind.  While it's on the same usb channel as touch it would be a
different event, wouldn't it.

On Mon, Jan 10, 2011 at 10:16 AM, Favux ...  wrote:
> Hi Chris,
>
> Pad was switched to absolute device.  See the 12-15-10 commit "Switch
> the pad to forced absolute mode":
> http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/xf86-input-wacom;a=commit;h=ce98b0a20862291892fc7a3110e4779cd69dd5ba
>  And the commits around it.
>
> Favux
>
> On Mon, Jan 10, 2011 at 9:39 AM, Chris Bagwell  wrote:
>> In reply to myself... oh yeah, the touchpad is a relative device. :-)
>>
>> but maybe something in this area has changed slightly and needs a look
>> at.  I'll try to dig deeper when I have a minute.
>>
>> Chris
>>
>> On Mon, Jan 10, 2011 at 8:48 AM, Chris Bagwell  wrote:
>>> Oh, if I do two finger touch, I'm able to get device type to change to
>>> 2 but I also get an additional interesting message (the last line in
>>> this snippet):
>>>
>>> [1084191.183] (II) /dev/input/event6 (10:wcmEvent): channel = 0
>>> [1084191.183] (II) /dev/input/event6 (10:wcmEvent): c=0 i=3 t=2 s=1 x=9130 
>>> y=701
>>> 2 b=0 p=0 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=1 st=1084190800 cs=4
>>> [1084191.183] (II) /dev/input/event6 (10:wcmFilterCoord):
>>> common->wcmRawSample = 4
>>> [1084191.183] (II) /dev/input/event6 (10:wcmCheckSuppress): level = 2
>>> return value = 2
>>> [1084191.183] (II) /dev/input/event6 (10:commonDispatchDevice): device type 
>>> = 2
>>> [1084191.183] (II) /dev/input/event6 (10:commonDispatchDevice): Ignore
>>> non-movement relative data
>>>
>>> So perhaps touch device was set to relative mode at some point during
>>> init phase.
>>>
>>> Chris
>>>
>>> On Mon, Jan 10, 2011 at 8:45 AM, Chris Bagwell  wrote:
>>>> Something about that bi-sect doesn't make sense.  Your pointing to a
>>>> commit that contains no code.
>>>>
>>>> I only have a few minutes with touch pad right now but tried git and
>>>> can also reproduce.
>>>>
>>>> The only thing that looked suspicious in log files is this:
>>>>
>>>> [1082669.808] (II) /dev/input/event6 (10:commonDispatchDevice): device 
>>>> type = 4
>>>>
>>>> I believe that says its detected as a cursor device?  There is a case
>>>> statement for ABS_MT_SLOT that is supposed to set that value correctly
>>>> that seems not to be working now.
>>>>
>>>> Can you confirm if your using wacom-input Bamboo drivers as well?
>>>> This may be MT specific (I hope).
>>>>
>>>> Chris
>>>>
>>>> On Mon, Jan 10, 2011 at 2:22 AM, Favux ...  wrote:
>>>>> Hi Peter,
>>>>>
>>>>> Bisection shows it is the 12-21-10 "Merge branch 'multimonitor-purge'"
>>>>> commit.  Its snapshot xf86-input-wacom-68351da breaks touch.  Although
>>>>> rather than slamming to the left it jitters horizontally in place over
>>>>> about 1.5 cm.  The prior commit of the same date "Bamboo tablet does
>>>>> not report device_id anymore" snapshot xf86-input-wacom-2b9eb3d still
>>>>> has working touch.
>>>>>
>>>>> Favux
>>>>>
>>>>> On Sun, Jan 9, 2011 at 11:53 PM, Peter Hutterer
>>>>>  wrote:
>>>>>>
>>>>>> can you run a bisect over the code to identify which commit broke it?
>>>>>> three different features got merged, multimonitor removal, the scrollring
>>>>>> fixes and chris' bamboo patches. Not sure which one caused the bug.
>>>>>>
>>>>>> Cheers,
>>>>>>  Peter
>>>>>>
>>>>>
>>>>> --
>>>>> 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
>>>>> Linuxwacom-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>>>>>
>>>>
>>>
>>
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Bamboo P&T touch broken with new commits?

[Favux ...]

No change in behavior using the wacom.ko from linuxwacom 0.8.8-10.
Same commit still breaks touch.

Favux

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Bamboo P&T touch broken with new commits?

[Favux ...]

Hi Chris,

I think you're on to something.  Here's what my logs are saying.

Both touch and pad are on:

[21.120] (**) Option "Device" "/dev/input/event6"

Xorg.0.log

[21.180] (--) Wacom BambooFun 2FG 4x5 Finger touch: Wacom USB
Bamboo tablet maxX=480 maxY=320 resX=25 resY=25
[21.230] (--) Wacom BambooFun 2FG 4x5 Finger pad: Wacom USB Bamboo
tablet maxX=480 maxY=320 resX=25 resY=25
[21.450] (--) Wacom BambooFun 2FG 4x5 Finger touch: top X=0 top
Y=0 bottom X=480 bottom Y=320 resol X=25 resol Y=25


Xorg.0.log.old

[21.720] (--) Wacom BambooFun 2FG 4x5 Finger touch: Wacom USB
Bamboo tablet maxX=480 maxY=320 resX=25 resY=25
[21.750] (--) Wacom BambooFun 2FG 4x5 Finger pad: Wacom USB Bamboo
tablet maxX=480 maxY=320 resX=25 resY=25
[22.120] (--) Wacom BambooFun 2FG 4x5 Finger touch: top X=0 top
Y=0 bottom X=480 bottom Y=320 resol X=25 resol Y=25


Xorg.1.log

[28.072] (--) Wacom BambooFun 2FG 4x5 Finger touch: Wacom USB
Bamboo tablet maxX=0 maxY=0 maxZ=1023 resX=2540 resY=2540
tilt=disabled
[28.142] (--) Wacom BambooFun 2FG 4x5 Finger pad: Wacom USB Bamboo
tablet maxX=480 maxY=320 maxZ=1023 resX=2540 resY=2540  tilt=disabled
[28.342] (--) Wacom BambooFun 2FG 4x5 Finger touch: top X=0 top
Y=0 bottom X=480 bottom Y=320 resol X=2540 resol Y=2540

It looks like the last two digits of resolution are being cut off.

Favux

On Mon, Jan 10, 2011 at 12:38 PM, Chris Bagwell  wrote:
> I only have remote access to tablet right now but I noticed this in
> the log file:
>
> Wacom Bamboo 2FG 4x5 Finger touch: Wacom USB Bamboo tablet maxX=0
> maxY=0 maxZ=256 resX=10 resY=10  tilt=disabled
>
> I'm guessing the main issue is related to those zero values.
>
> I'll have to study this new code a little (related to PAD device
> cleanup).  I'm sure the main issue is related to how Bamboo inits
> uniquely compared to other tablets.  its really the 2nd tool that
> always calls getRanges() because of how hotplugging works.
>
> So in normal tablet, its the ERASER that calls getRanges().  In case
> of Bamboo touchpad, its the PAD device that is second and calls
> getRanges() and some 1 time init code.
>
> I see a few places if "if (!IsPad(priv))" thats probably getting
> confused and skipping some important init for touch related part.
>
> Chris
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Functional responsibility of code

[Favux ...]

Hi Peter,

It was originally posted by Christoph in linuxwacom-devel:
http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTimO9QX5%3Dx1VGNRVNkLiHLyULtvcav%3DXzimfgedx%40mail.gmail.com&forum_name=linuxwacom-devel

Sanette's modifications (two so far) are posted at Ubuntu forums.
It's one of the things I've been thinking of adding to the wiki.

Favux

On Tue, Jan 11, 2011 at 4:59 PM, Peter Hutterer
 wrote:
> On Tue, Jan 11, 2011 at 05:53:01PM +0100, Cedric Sodhi wrote:
>> I'd like to address the issue of LEDs in this separate thread. The
>> solution that is provided by Christoph Karg's utility is a great step
>> forward, given that we can now use the OLEDs at all, but it's also in
>> several areas problematic:
>>
>> -> The utility interferes with the kernel driver, requiring it to be
>> unloaded and reloaded.
>>
>> -> It might crash X, if this is done while input is read from the Wacom
>>
>> -> The utility has to be run separately, as root, and accesses the Wacom
>> directly through libusb
>
> where is this utility? is it still hiding in the ubuntuforums somewhere?
>
> Cheers,
>  Peter
>
>>
>> Given these problems and the fact, that the LEDs are an integral part of
>> the device, I plead for a better solution to be found.
>> It is my stance, and I think at least with that everyone will agree,
>> that all interaction with the device shall go through the kernel driver
>> for the device.
>>
>> It's also my opinion, and I think that is in the spirit with the clean
>> code you practice, that controling OLEDs has nothing to do with Xinput
>> and should hence not interfere with the xf86-input driver.
>>
>> But the problem with requiring root priviledges needs also to be solved.
>> I for my part find it inconsistent and cumbersome that the device
>> itsself can be used and controlled as a user (as it should be) but a few
>> integral operations, which are per se not different from others can only
>> be accessed as root?! You agree?
>>
>> I think it would be a clean, feasible and durable solution to
>>
>>
>> X11/XInput --- xf86-input-wacom --- Kernel Driver --- wcmsetled
>>                                           |
>>                                           |
>>                                     Wacom Hardware
>>
>>
>> where wcmsetled is a userspace tool that communicates with the kernel
>> driver and is part of the linux-wacom "suite".
>> And for the sake of the UNIX-philophy, the cleanness of linux-wacom,
>> against bloat and for the sake of simplicity, both wcmsetled and the
>> kerneldriver offer only an minimalist's interface, meaning they are
>> stripped off any flexibility such as converting images to the
>> appropriate format, which can all take place in userspace before
>> wcmsetled.
>>
>> I think that would make an eligible concept. Does anyone disagree?
>
>
> --
> 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
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH 4/4] compute factorX/factorY from sizeX/sizeY.

[Favux ...]

On Fri, Jan 14, 2011 at 8:42 AM, Chris Bagwell  wrote:
> On Fri, Jan 14, 2011 at 12:27 AM, Ping Cheng  wrote:
>
> I can clarify the main intent of bottomX/Y is not for fixing screen to
> tablet ratio mismatches but that it is used for that in addition to
> its other purposes.
>
>> So, does this mean that we can not scale tablet active area  to screen
>> ratio any more?

This is my question also.

> Yes.  Thats the reason for this patch.  KeepShape does not work now
> and since relative movement seemed to have its own version of
> KeepShape concept but unconditionally enabled, it broke even without
> that configuration option enabled.
>
> The intent of this patch is to align relative scaling with absolute
> KeepShape though.  If KeepShae feature ever is made to work again then
> this patch will (should) start working for relative devices as well.
> If its never made to work again then their is lots of code cleanup we
> can do for both absolute and relative devices to get rid of scaling.

I had thought we could use TopX & Y and BottomX & Y to mimic
'KeepShape" functionality.  Does it also work along side "MapToOutput"
or the 'Coordinate Transformation Matrix'?  I think that is what you
are saying Chris.  I know it works with other tablets anyway.

Favux

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH 10/11] Remove useless else block.

[Favux ...]

On Tue, Jan 18, 2011 at 8:09 PM, Chris Bagwell  wrote:
>
> Today factorX/Y will always be 1 unless user edits xorg.conf.d so no
> rounding errors.  I doubt they will do this for relative devices?
> Anyways, we can keep an eye out on it.

lol  We were actually talking about trying that to deal with the over
acceleration issue of the pointer with touch on the BambooPT.

Favux

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH 10/11] Remove useless else block.

[Favux ...]

Thank you Peter!

I like:

xinput set-prop "Wacom BambooFun 2FG 4x5 Finger touch" --type=float
"Device Accel Constant Deceleration" 2.00

Some might like 2.5 or 3.  Also adding:

xinput set-prop "Wacom BambooFun 2FG 4x5 Finger touch" --type=float
"Device Accel Velocity Scaling" 2.00

seems nice.  I'll play around with them a little more, but this is
definitely a way to go.

Favux

On Tue, Jan 18, 2011 at 9:33 PM, Peter Hutterer
 wrote:
> On Tue, Jan 18, 2011 at 08:25:53PM -0600, Favux ... wrote:
>> On Tue, Jan 18, 2011 at 8:09 PM, Chris Bagwell  wrote:
>> >
>> > Today factorX/Y will always be 1 unless user edits xorg.conf.d so no
>> > rounding errors.  I doubt they will do this for relative devices?
>> > Anyways, we can keep an eye out on it.
>>
>> lol  We were actually talking about trying that to deal with the over
>> acceleration issue of the pointer with touch on the BambooPT.
>
> the overacceleration issue in the bamboo is caused by a few other things.
> when the bamboo is initialised as relative device, the X server doesn't have
> an axis range to help scaling the movement. the bamboo, as you're probably
> aware, has a higher resolution than the average mouse, so it sends more
> events with higher data. so the default settings dont' work too well, it's
> too fast. increasing ConstantDeceleration for the device should slow it down
> to your preference.
>
> at least, I _think_ this is the crux here :)
>
> Cheers,
>  Peter
>

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] Add 2 new Bamboo Pen & Touch models.

[Favux ...]

We should add the 0xd6 and 0xd7 since they are already in
input-wacom-0.10.10-1.  Hopefully the final two models in this series.

Dave
From 1558ffeebf3cdf3194d6b65702a93c952fa845c8 Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Thu, 20 Jan 2011 13:59:20 -0600
Subject: [PATCH] wcmUSB.c:  2-new-bambooPT-models

Adds 2 new Bamboo Pen & Touch models.

Signed-off-by: David Foley 
---
 src/wcmUSB.c |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/src/wcmUSB.c b/src/wcmUSB.c
index 0d21af9..cfaf920 100644
--- a/src/wcmUSB.c
+++ b/src/wcmUSB.c
@@ -195,6 +195,8 @@ static struct
 	{ WACOM_VENDOR_ID, 0xD3, 10, 10, &usbBamboo }, /* CTL-660 */
 	{ WACOM_VENDOR_ID, 0xD2, 10, 10, &usbBamboo }, /* CTL-461/S */
 	{ WACOM_VENDOR_ID, 0xD0, 10, 10, &usbBamboo }, /* Bamboo Touch */
+	{ WACOM_VENDOR_ID, 0xD6, 10, 10, &usbBamboo }, /* CTH-460/K */
+	{ WACOM_VENDOR_ID, 0xD7, 10, 10, &usbBamboo }, /* CTH-461/S */
 	{ WACOM_VENDOR_ID, 0xD8, 10, 10, &usbBamboo }, /* CTH-661/S1 */
 	{ WACOM_VENDOR_ID, 0xDA, 10, 10, &usbBamboo }, /* CTH-461/L */
 	{ WACOM_VENDOR_ID, 0xDB, 10, 10, &usbBamboo }, /* CTH-661 */
-- 
1.7.1

--
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
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Cintiq calibration lost when hotplugging

[Favux ...]

That sounds good.  Or you can create a little daemon.  Cyberfish came
up with this about 2 years ago.  Call it monitor_wacom.c:

#include 
#include 
#include 
#include 
#include 
#include 

void log_msg(const char *msg) {

FILE *log_file = fopen(".monitor_wacom.log", "a");

if (log_file) {
time_t time_g;
time(&time_g);
char date_str[100];
strcpy(date_str, asctime(localtime(&time_g)));
date_str[strlen(date_str) - 1] = '\0'; /* get rid of the \n */
fprintf(log_file, "%s : %s\n", date_str, msg);
}

fclose(log_file);
}

void run_script(const char *filename) { /* only run xsetwacom lines */
FILE *script_file = fopen(filename, "r");

if (!script_file) {
log_msg("Failed to open script (double check your entry in 
Startup
Applications). Terminating.");
exit(1);
}

char buf[1024];
char l_buf[1024];
int count = 0;
while ((fgets(buf, 1023, script_file))) {
if (strstr(buf, "xsetwacom")) {
int r = system(buf);
if (r != 0) {
sprintf(buf, "xsetwacom returned error on line 
- %s", buf);
log_msg(l_buf);
}
++count;
}
}

sprintf(l_buf, "Script ran. %d matching lines executed.", count);

log_msg(l_buf);
}

int main(int argc, char **argv) {

char script_name[1024];

if (argc != 2) {
log_msg("Script not specified, using .xinitrc");
strcpy(script_name, ".xinitrc");
} else {
strcpy(script_name, argv[1]);
}

run_script(script_name);

FILE* in = popen("dbus-monitor --session
type='signal',interface='org.gnome.ScreenSaver',member='ActiveChanged'",
"r");

if (!in) {
log_msg("Cannot spawn dbus-monitor process. Terminating.");
return 1;
}

while (1) {
char buf[1024];
assert(fgets(buf, 1023, in));

if (buf[0] == 's' /* early exit optimization */ && strstr(buf,
"ActiveChanged") != NULL) {
assert(fgets(buf, 1023, in));
if (strstr(buf, "false") != NULL) {
/* resumed */
log_msg("Exit from screensaver detected. 
Running script.");
run_script(script_name);
} else {
    /* put to sleep */
}
}
}
}


gcc -O2 monitor_wacom.c -o .monitor_wacom

And then in Startup Applications:

/home/yourusername/.monitor_wacom /home/yourusername/.xinitrc

Favux

On Tue, Jan 25, 2011 at 2:06 PM, Cedric Sodhi  wrote:
> Hello, this is the same for all devices, I think. At least it's the same
> for my Intuos4. But I think that's okay.
>
> It's not the responsibility of the driver to re-initialize the device
> with the old settings - the driver is simply the method to communicate
> with it, it shall not offer any "special service" such as remembering
> options. You should use a dedicated tool for that.
>
> There is a certain problem though, which, however, is not to blame on
> the wacom but rather on X11 polcies, that is, usually UDEV should handle
> hotplugging these days but udev (or anything started from it) will have
> problems with setting xinput props because it lacks the authz to do so.
>
> I suggest you set up a simple bash script which is started with xinit
> and will listen for the wacom being plugged or not. Most easily, you
> could do this by setting up an udev rules which provides a user-readable
> switch (such as a file /tmp/wacom_is_plugged) when the wacom is up and
> removes it if it isnt.
>
> The bash script can simply run in a loop (with sleep 1000 or so) and
> execute your wacom_set_props.sh script if udev communicates it that the
> device has been plugged.
>
> I've a similar setup (not for the wacom but for an external) monitor and
> it works flawlessly and, best of all, is very flexible.
>
> regards,
> Cedric
>
> On Tue, Jan 25, 2011 at 11:48:53AM -0800, Steven L. Seed wrote:
>>    Has anyone noticed that when you hotplug a Cintiq that has been calibrated
>>    with the wacomcpl, you lose the calibration (it resets) after you hotplug
>>    the tablet? This is particularly problematic in ou

Re: [Linuxwacom-devel] Cintiq calibration lost when hotplugging

[Favux ...]

Great.  Thanks for the code update.

On Tue, Jan 25, 2011 at 6:35 PM, Steven L. Seed
 wrote:
> Here is our modified version of the monitor_wacom.c code. His original code
> was checking for the screen saver to go off to load the settings. In our
> case, we want to load the settings whenever the tablet is plugged in, so we
> modified it to listen on the org.freedesktop.Hal.Manager interface for the
> "DeviceAdded" singal.
>
> #include 
> #include 
> #include 
> #include 
> #include 
> #include 
>
> void log_msg(const char *msg) {
>
>
> FILE *log_file = fopen("/tmp/monitor_wacom.log", "a");
>
> if (log_file) {
> time_t time_g;
> time(&time_g);
> char date_str[100];
> strcpy(date_str, asctime(localtime(&time_g)));
> date_str[strlen(date_str) - 1] = '\0'; /* get rid of the \n
> */
> fprintf(log_file, "%s : %s\n", date_str, msg);
> }
>
> fclose(log_file);
> }
>
> void run_script(const char *filename) { /* only run xsetwacom lines */
> FILE *script_file = fopen(filename, "r");
>
> if (!script_file) {
> log_msg("Failed to open script (double check your entry in
> Startup Applications). Terminating.");
> exit(1);
> }
>
> char buf[1024];
> char l_buf[1024];
> int count = 0;
> while ((fgets(buf, 1023, script_file))) {
> if (strstr(buf, "xsetwacom")) {
> int r = system(buf);
> if (r != 0) {
> sprintf(buf, "xsetwacom returned error on
> line - %s", buf);
> log_msg(l_buf);
> }
> ++count;
> }
> }
>
> sprintf(l_buf, "Script ran. %d matching lines executed.", count);
>
> log_msg(l_buf);
> }
>
> int main(int argc, char **argv) {
>
> char script_name[1024];
>
> if (argc != 2) {
> log_msg("Script not specified, using .xinitrc");
> strcpy(script_name, ".xinitrc");
> } else {
> strcpy(script_name, argv[1]);
> }
>
> run_script(script_name);
>
> FILE* in = popen("dbus-monitor --system
> type='signal',interface='org.freedesktop.Hal.Manager',member='DeviceAdded'",
> "r");
>
> if (!in) {
> log_msg("Cannot spawn dbus-monitor process. Terminating.");
> return 1;
> }
> while (1) {
> char buf[1024];
> assert(fgets(buf, 1023, in));
>
> if (buf[0] == 's' /* early exit optimization */ &&
> strstr(buf, "DeviceAdded") != NULL) {
> /* resumed */
> log_msg("Device plugged in. Running
> script.");
> run_script(script_name);
> }
> }
> }
>
>

--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Cintiq calibration lost when hotplugging

[Favux ...]

Hi Cedric,

I'm probably misunderstanding what you are asking.  But you can use
Options with the same syntax as in xorg.conf in xorg.conf.d.  e.g.:
Option "Button2" "3"
Option "TopX" "0"
After the Driver line in the relevant snippet.  Maybe you're running
into the the fact the udev currently can't configure dependent
devices?  Like the early days of HAL before wacom-to-hal.  I'm pretty
sure that's been addressed upstream.  Peter gave an example snippet
for a dependent device a while ago.  He can tell us when to expect it.
 I actually thought it might be in 1.9.

In the meantime you have to use xsetwacom scripts or the xorg.conf for
dependent devices.

Favux

On Wed, Jan 26, 2011 at 2:04 AM, Cedric Sodhi  wrote:
> Hello Peter,
>
> could you tell us how in particular udev can set Properties? I've been
> very concerned with this topic for quite a while and in the end I had to
> conclude that it's *not* possible to use udev in the same manner as hal
> used to work.
> I did *not* find any way to communicate settings to xorg apart from
> manually xauthing and using xset/xinput to do that.
>
> If you know how udev (possibly to custom attributes) can configure xorg
> please explain it!
>
>
> On Wed, Jan 26, 2011 at 03:53:05PM +1000, Peter Hutterer wrote:
>> On Tue, Jan 25, 2011 at 09:06:18PM +0100, Cedric Sodhi wrote:
>> > Hello, this is the same for all devices, I think. At least it's the same
>> > for my Intuos4. But I think that's okay.
>>
>> it's the same for all devices and can largely be blamed on wacomcpl.
>> wacomcpl changes X input properties which are only valid for the lifetime of
>> the device. wacomcpl is essentially a fancy version of the "xinput" or
>> "xsetwacom" tools (in fact, wacomcpl uses xsetwacom).
>>
>> for permanent storage, the tool needs to either reapply the settings
>> whenever a new device was detected or write them to permanent storage
>> (xorg.conf or in newer servers xorg.conf.d).
>>
>> > It's not the responsibility of the driver to re-initialize the device
>> > with the old settings - the driver is simply the method to communicate
>> > with it, it shall not offer any "special service" such as remembering
>> > options. You should use a dedicated tool for that.
>> >
>> > There is a certain problem though, which, however, is not to blame on
>> > the wacom but rather on X11 polcies, that is, usually UDEV should handle
>> > hotplugging these days but udev (or anything started from it) will have
>> > problems with setting xinput props because it lacks the authz to do so.
>>
>> udev (and HAL) can both set options from their respective configuration
>> files. In fact, servers 1.5, 1.6 and 1.7 need HAL's fdi configuration for
>> input.x11_driver and input.x11_options.
>>
>> these options are permanent and apply to hotplugged devices as well.
>> wacomcpl doesn't talk that configuration though.
>>
>> Cheers,
>>   Peter
>>
>> > I suggest you set up a simple bash script which is started with xinit
>> > and will listen for the wacom being plugged or not. Most easily, you
>> > could do this by setting up an udev rules which provides a user-readable
>> > switch (such as a file /tmp/wacom_is_plugged) when the wacom is up and
>> > removes it if it isnt.
>> >
>> > The bash script can simply run in a loop (with sleep 1000 or so) and
>> > execute your wacom_set_props.sh script if udev communicates it that the
>> > device has been plugged.
>> >
>> > I've a similar setup (not for the wacom but for an external) monitor and
>> > it works flawlessly and, best of all, is very flexible.
>> >
>> > regards,
>> > Cedric
>> >
>> > On Tue, Jan 25, 2011 at 11:48:53AM -0800, Steven L. Seed wrote:
>> > >    Has anyone noticed that when you hotplug a Cintiq that has been 
>> > > calibrated
>> > >    with the wacomcpl, you lose the calibration (it resets) after you 
>> > > hotplug
>> > >    the tablet? This is particularly problematic in our environment where 
>> > > the
>> > >    tablets are attached via kvm switches to work with multiple systems. 
>> > > We
>> > >    are on RHEL6 running Xorg 1.7.7-26 and the wacom driver version 
>> > > 0.10.5-8.
>> > >
>> > >    --
>> > >    [1][IMG]
>> > >
>> > > References
>> > >
>> > >    Visible links
>&

Re: [Linuxwacom-devel] [PATCH 00/10] xsetwacom UI changes

[Favux ...]

I for one am not excited by the proposed changes.  I just finished
updating most of the xsetwacom scripts to be xf86-input-wacom
compatible and going through that again does not appeal.  I've had
enough folks bewildered or complaining about the switch from
ClickForce to Threshold.

I definitely see the benefit of going to more naturally readable
names.  But the motivation for some changes escape me.  Why add a
whitespace and make for e.g. Button2 become Button 2?  Yes it is a
little more readable but that breaks all stylus button and tablet
(pad) button scripts.

However if Peter feels the changes are necessary...ok.  While I
realize it would be a major pain would it be possible for a transition
period?  Say 6 months or even longer.  Where both versions would work
and the transition is documented in 'man xsetwacom'?  Yes, crufty
code, but with a deadline.  And say implemented at a point release?

Favux

On Thu, Feb 3, 2011 at 12:38 PM, Ping Cheng  wrote:
> On Wed, Feb 2, 2011 at 9:13 PM, Peter Hutterer  
> wrote:
>>
>> This series will be more controversial than the last 8 but let's see. The
>> patches here change the xsetwacom parameter names into something that's
>> slighly more self-explanatory.
>>
>> Yes, we know what "RelWDn" means, but I'm sure my great-grandfather, if I had
>> one, would throwing his false teeth at me for making no sense.
>> "RelWheelDown", otoh, is a parameter name we can believe in.
>> Same goes for all the other names, except the Button mapping change which is
>> mostly to keep the code a bit simpler and not keep 32 near-identical structs
>> around.
>>
>> FAQ:
>> - Won't this break user's scripts?
>>  Yes, such is life.
>> - But they relied on xsetwacom's interface to be stable!
>>  Yes, I can see the problem right there. It isn't.
>> - Will the world end because of this?
>>  Unlikely, but if it does you'll get your money back.
>
> >From a pure developer's perspective, I have no preference. But I work
> for the users. When a decision affects them, I'd like to know what
> they think. Let's "poll the audience" to see if they want to bid on
> the money back or not ;).
>
> "Audience", please share your thoughts with us so we may make a
> decision that satisfies most users.
>
> Thank you.
>
> Ping
>
> --
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH 00/10] xsetwacom UI changes

[Favux ...]

> would something like:
>xsetwacom get  RelWUp
>"RelWUp is obsolete. Please use RelWheelUp instead"
>
> be acceptable? A mapping table like this is easy to maintain.

Sure, good idea!  That would give folks at least something to work
with.  So I'm definitely in favor of that.

I know you know but just to be clear, a lot of users aren't aware of
the get command or 'man xsetwacom' or much of anything to do with the
command line now days.  :)

Favux

--
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] 0.10.11 release coming up - nominate fixes now

[Favux ...]

Andrzej Giniewicz nominates fixing Super:  "I'm glad it will be fixed
in next release, it will
decrease number of patches needed on OS side. Actually from 10 patches
we have there, only the xsetwacom fix for Super will have to remain
after next release (just curious, would it be possible to still
squeeze it into 0.10.11? I mean the issue fixed by Przemo on 4'th Jan:

http://sourceforge.net/mailarchive/forum.php?thread_name=m3y6718oy1.fsf%40who-t.net&forum_name=linuxwacom-devel

I know there are better solutions, but it would make it work)"

https://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTimUh%3DZT_e44Os5gg9kOLbUaj4SreZ4hwcV-qm8D%40mail.gmail.com&forum_name=linuxwacom-devel

On Thu, Feb 10, 2011 at 6:44 PM, Chris Bagwell  wrote:
> On Thu, Feb 10, 2011 at 5:46 PM, Peter Hutterer
>  wrote:
>> I'm planning to release 0.10.11 next week, so I'll be more cautious to merge
>> patches for a few days. If you have any big issues with the current state of
>> the repo (crashes, device not working, regressions) please let us know so we
>> can give those priority.
>
> It seems like a good point to do it.  Its been stable for a couple of
> weeks now. :-)
>
> There was a good chunk of patches that finally made it over to visible
> repo this week so I'll try to give today's git a once over.
>
> Chris
>
> --
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] bamboo p&t 0.10.11 regression. Pad keys stop sending events after Touch is used

[Favux ...]

Hi,

Parameter names have changed with 0.10.11.  Button1 is now Button 1
and Button2 is now Button 2 and so on.  See xsetwacom in the
mediawiki:  
http://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Xsetwacom

e.g. stylus button set would now be Button 2  "3"

So check out the changes and see if that has something to do with it.

Favux

Favux

On Thu, Feb 17, 2011 at 8:00 AM, Andrzej Giniewicz  wrote:
>> I'll see if I can reproduce it soon.  In mean time, can you please
>> send command you use to disable touch.  I do not normally do this.
>
> sure, here it goes:
>
> xsetwacom set "Wacom Bamboo 2FG 4x5 Finger touch" Touch "off"
>
> Andrzej.
>
> --
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] xsetwacom.c: Correct typo-spelling

[Favux ...]

Minor and self explanatory.

Dave

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] xsetwacom.c: Correct typo-spelling

[Favux ...]

Patch
From 6e682f268416db29cb178f1f7f734b7687081d29 Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Thu, 17 Feb 2011 20:57:38 -0600
Subject: [PATCH] xsetwacom.c:  Correct typo/spelling

Reported by: Vu Ngoc San 
Signed-off-by: David Foley 
---
 tools/xsetwacom.c |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/tools/xsetwacom.c b/tools/xsetwacom.c
index 4529545..6713a97 100644
--- a/tools/xsetwacom.c
+++ b/tools/xsetwacom.c
@@ -427,7 +427,7 @@ is_deprecated_parameter(const char *name)
 	}
 
 	if (is_deprecated)
-		printf("Paramater '%s' is no longer in use. "
+		printf("Parameter '%s' is no longer in use. "
 			"It was replaced with '%s'.\n", name, d->replacement);
 
 	return is_deprecated;
-- 
1.7.1

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH 2/2] Doxygen: add description on the main html page

[Favux ...]

Speaking of which, is the intention to keep the download link pointing
at the 0.10.9 tar?

On Thu, Feb 17, 2011 at 7:30 PM, Gaetan Nadon  wrote:
> Rather than staring at a blank screen.
> To be completed.
>
> Signed-off-by: Gaetan Nadon 
> ---
>  include/Xwacom.h |    8 
>  1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/include/Xwacom.h b/include/Xwacom.h
> index a6a4546..163726d 100644
> --- a/include/Xwacom.h
> +++ b/include/Xwacom.h
> @@ -17,6 +17,14 @@
>  * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
>  */
>
> +/** \mainpage
> + * \section intro Introduction
> + * The Linux Wacom Project manages the drivers, libraries, and documentation
> + * for configuring and running Wacom tablets under the Linux operating 
> system.
> + * It contains diagnostic applications as well as updated kernel drivers
> + * and XFree86/X.Org X input drivers.
> + */
> +
>  #ifndef __XORG_XWACOM_H
>  #define __XORG_XWACOM_H
>
> --
> 1.6.0.4
>
>
> --
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] Sample xsetwacom scripts vetting

[Favux ...]

Hi,

Peter would like these scripts vetted.  So if you get a chance please
review them and comment.

This is a sample of the the sample scripts.  The idea is to provide a
text file as a framework to alter the tablet settings, similar to what
wacomcpl would have produced in its xsetwacom script file .xinitrc.
Except it is broken into input tool sections.  This makes it easier
for the user to see what parameter adjustments are useful for a given
input tool.  The pad section attempts to "mimic" the physical button
layout for the tablet.  I use the generic name .xsetwacom.sh for them.

The defaults are used and stated with the ranges in the comments for
ease of use.  This is obviously a hack while we wait for tablet gui's
for Gnome and KDE and the rest.  As an aside I noticed the plan for
the Gnome gui is to be for tablets only, not tablet PCs.  Hopefully
they will be able to use it anyway.

Right now the pre-0.10-11 parameter names are used as the majority of
users are probably still pre-0.10-11 and will be until Natty, Fedora
15, etc. are released in a few months.

The user can go on to use a subset of the script, usually the pad
button assignments with maybe stylus pressure etc., to generate a
profile for various programs such as Gimp if they desire.  Which is
one of the reasons for showing alternate button assignment examples
for specific graphics programs.

The general tablet script is placed in a start up file and the
profiles in launchers.

We've been using them on Ubuntu forums since Lucid (10.04) X server
1.7 released April 2010.

Thank you.

Favux


Cintiq.sh
Description: Bourne shell script


Intuos4.sh
Description: Bourne shell script


BambooPT.sh
Description: Bourne shell script


TabletPC-1FGT.sh
Description: Bourne shell script


TabletPC-2FGT.sh
Description: Bourne shell script
--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev ___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Sample xsetwacom scripts vetting

[Favux ...]

o just "device
name"?

> ok, my main issue with the scripts is that they duplicate the device names
> heavily, which makes them hard to update (yes, search/replace, I know) and
> hard to read. worse, TabletPC-1FGT.sh mixes IDs and device names.
>
> one approach would be:
>
>    DEV="Wacom Cintiq 12UX2"
>    STYLUS="$DEV stylus"
>    PAD="$DEV pad"
>
>    xsetwacom set "$STYLUS" Suppress 4
>    xsetwacom set "$STYLUS" RawSample 2
>    ...

No objection to this in principle.  I thought it probably better to
imitate wacompl's .xinitrc and stick to the xsetwacom command format
the user would use to change an individual parameter, rather than add
another seeming xsetwacom format into the mix.  While some users,
especially long time ones, have learned the xsetwacom commands, that
doesn't mean they've learned BASH scripting.  So the directions would
have to be clear.

> once you start looking at that, you notice that the scripts are mostly
> identical. At which point I'm starting to wonder why we have 5 different
> scripts?

Well of course they're nearly identical.  Any default setup should be,
whether gui or whatever.  It's only when the user starts adding
customizations that the variations occur.  Especially tablets with
pads.  The question is how much to provide?  Build from the man pages
or give examples they can assemble into their own individualized
script?

> as with all scripts, forcing defaults to the default value is generally a
> bad idea.

The general idea is to have the tablet behave as the default setup.
The user then choses what to customize.  Say she's experiencing the
the line lag with the stylus seen by some in Gimp because of the long
standing GTK CPU usage bug.  Then she'd want to up her RawSample for
her stylus.  The script shows that RawSample applies to the stylus,
the default, and the allowed range she has to work with.  Sure all in
the man page.  The idea is convenience.

> It means that if we change the defaults in the driver to improve
> the behaviour users won't notice because they're blindly applying some
> settings. It also means we won't get user feedback because they don't even
> know anything has changed.

That is a valid concern.  But please notice the dichotomy between your
concern about getting user feed back on parameter default changes in
the driver v.s. user concern about the UI abruptly changing on them
and rendering their efforts in mastering the xsetwacom command
parameters useless until they learn the new ones.  Not that the
reasons for changing the UI interface weren't good, just that it is a
two way street.

> I'm not sure why there is a "alternative pad button assignment examples"
> section.  Surely users who figure out Button2 "key ctrl" also figure out
> "key shift" without having someone pre-fill those in?

I have a user asking me right now why setting a Button to "f1" isn't
working.  Despite having a script as a template.

> and some of the settings are confusing at best. BambooPT's button
> assignments are rather random and that's afaict the only thing that's not
> set to the defaults.

The BambooPT script was originally written to duplicate the default
Wacom tablet button assignment in Windows XP.  Except
xf86-input-wacom-0.10.5's xsetwacom could not assign a left click to
Button4 so back a page in Firefox was chosen.  The point is to provide
examples.  The user is free to change the settings.

> Cheers,
>  Peter

I've been tracking this discussion in its various forms for about a
year and it continues to remind me of Voltaire's aphorism:  "The
perfect is the enemy of the good."  :)  Meanwhile, depending how you
want to count it, the Linux Wacom Project for "modern" systems is at 9
months without a configuration gui and counting.  Despite a lot of
needed hard work.

No doubt the scripts could benefit from some clean up.

Favux

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Sample xsetwacom scripts vetting

[Favux ...]

everyone is using 2.6.37+ kernels.
>
> Some of the stylus buttons fall into #2 as well.  Based on scripts,
> looks like we are inconsistent in what generates button #3 click.
> Lets say stylus only has one button.  What does user expect that to
> do?  Button #3?  Today its probably button #2.  If its rocker button,
> do they still expect same behavior?

Most with a single stylus button prefer it to be a right click.  That
is a perennial question/request.  A patch to make Button 2 3 the
default was committed months ago.  Most with two stylus buttons
including rockers prefer Button 2 3 and Button 3 2.  But not all.

> I'll kinda ignore the rest of buttons because I'm not sure how people
> use "pad" buttons.

Hence the need for graphic professional input.  I've included some of
the feed back I've gotten in the scripts and alternate examples.  The
point is there is no standard.  Different folks are going to want
different settings in Gimp, Inkscape, MyPaint, Blender, etc. depending
on their usage and preferences.  And that's why the 'profile' concept
is important.

> Chris

Favux

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Sample xsetwacom scripts vetting

[Favux ...]

Hi Chris,

Actually you're up to speed I think.  They're meant to be a stop gap
for the user while we're waiting for a gui.  They're examples that can
be used currently with the intention of the user modifying the
parameter values to what they want/require.

Since they essentially duplicate wacomcpl's backend .xinitrc,
solutions like daemons that worked for it will work for the
.xsetwacom.sh scripts too.

You're just going further along the road Peter started and actually
coming up with a replacement for wacomcpl.  Just needs a simple gui
slapped on it.

Favux

On Wed, Feb 23, 2011 at 3:35 PM, Chris Bagwell  wrote:
>
> OK.  I guess I'm missing parts of this topic.  Sometimes it sounds
> like these are examples only but other times it sounds like its meant
> to be ran by some daemon backend or similar during hotplugs.
>
> If they are ever meant to be plugged into a backend then I'd assume
> most the hard stuff like xsetwacom_version or $STYLUS are
> automatically set for user.  But then again, I'd go the easier route
> for user and just have them set things like:
>
> TOUCH_THRESHOLD=27
> STYLUS_PRESSURECURVE=0 0 100 100
> STYLUS_THRESHOLD=27
>
> Then user doesn't even now they are really a bash script and looks
> dangerously close to windows *.INI they may already be familiar with
> for same types of stuff.
>
> At plugin time, source the above file, and start updating everything
> optionally and one by one:
>
> if xinput list | grep $HOTPLUG_NAME | grep touch; then
> TOUCH="$HOTPLUG_NAME touch"
> fi
> if [ "${TOUCH}x" != "x" ]; then
>  if [ "${TOUCH_THRESHOLD" != "x" ]; then
>    xsetwacom $TOUCH $threshold_name[$xsetwacom_version] $TOUCH_TRESHOLD
>  fi
> fi
>
> Then you are at long term easier to maintain all-in-one script as
> Peter suggestions.
>
> But I think I must be missing overall intent here.
>
> Chris
>

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Sample xsetwacom scripts vetting

[Favux ...]

Hi Peter, Chris, Ping, and interested readers,

Thank you everyone.  I've tried to take the comments into account and
come up with an action plan.  It avoids sample scripts set to default.

Again this is just a stop gap until a gui comes along.  And might
result in some usable feed back for the gui.  Given the manpower
shortage I'd prefer all of you working on the driver anyway and not on
a configuration gui.  You've got enough to do already.  Hopefully some
more developers interested in working on the gui will step up shortly.

Also to clarify my sloppy writing, when I was referring to man
xsetwacom I was including 'xsetwacom list parameters' etc. as part of
the "manual".

ACTION PLAN
1)  Delete the two configuration pages.
2)  Consolidate them to one HOW TO page.  Title - Tablet Configuration
?  (Don't really like it, suggestions?)

3)  Introduction on how to use xsetwacom and the man pages.
4)  Show example sections i.e. modular format:
  stylus
  eraser
  cursor
  touch
1 FG
2 FG
using 0.10.11 parameter names.  This would show all valid settings
(eventually) for each input tool.  All set to default with default and
range in the comments.

5)  Separate pad section.  This would contain a sample selection of
various tablet model pads.
6)  What values should be used for the tablet buttons?  Any
suggestions?  Or leave blank?

7)  One sample script using the BambooPT combining some of the above
but using only best guess as to what parameters a user would typically
want to change and the values they might pick.  This would be an
example of how to combine the modules.  And make a point of it
starting with #!/bin/bash.
Include tips on what parameters to change for known bugs.
Keep it as standard xsetwacom commands without any BASH optimizations like:
  DEV="Wacom Cintiq 12UX2"
  STYLUS="$DEV stylus"
  PAD="$DEV pad"

  xsetwacom set "$STYLUS" Suppress 4
  xsetwacom set "$STYLUS" RawSample 2
can always change to them later if desired.

8)  Instructions on how to add the user's script to start up.
9)  Instructions on how to make 'profiles' and place in Launchers.

10)  Should I add instructions on how to make settings permanent, i.e.
static configuration?  Using say a 52-wacom-options.conf in
/etc/X11/xorg.conf.d/ for X server 1.8 and up?  Still can't configure
dependent devices in X server 1.9.  But for e.g. the BambooPT can be
split into Pen and Finger snippets.  Something like:

Section "InputClass"
Identifier "Wacom class options"
MatchProduct "Wacom BambooFun 2FG 4x5 Pen"
MatchDevicePath "/dev/input/event*"
# Add Options below.
Option "Area" 0 0 14720 9200
EndSection

Section "InputClass"
Identifier "Wacom class options"
MatchProduct "Wacom BambooFun 2FG 4x5 Finger"
MatchDevicePath "/dev/input/event*"
# Add Options below.
Option "Area" 0 0 480 320
EndSection


Would the above be acceptable?

Favux

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Sample xsetwacom scripts vetting

[Favux ...]

Hi Peter,

FYI the Tablet Configuration HOWTO is essentially complete.  You can
remove the Tablet PC Configuration and Wacom Tablet Configuration
pages whenever you are ready to.

The 52-wacom-options.conf is a template.  I won't add it to
Configuring X until you've had a chance to review it.

Favux

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Sample xsetwacom scripts vetting

[Favux ...]

Hi Peter,

Sounds good.

I like the MatchDriver idea.

Favux

On Sun, Feb 27, 2011 at 8:59 PM, Peter Hutterer
 wrote:
> On Sun, Feb 27, 2011 at 02:13:14PM -0600, Favux ... wrote:
>> Hi Peter,
>>
>> FYI the Tablet Configuration HOWTO is essentially complete.  You can
>> remove the Tablet PC Configuration and Wacom Tablet Configuration
>> pages whenever you are ready to.
>>
>> The 52-wacom-options.conf is a template.  I won't add it to
>> Configuring X until you've had a chance to review it.
>
>
> thanks. As you can see from the history, I'd like to make this new page the
> main [[xorg.conf.d]] page and link to it from Configuring_X. there's plenty
> of information we should provide that it warrants a separate page.
> especially since we have different configurations for 1.8, 1.9 and 1.10.
>
> I haven't really finished with it yet though, I'll try to edit it over the
> next few days.
>
> The main plan is:
> - use MatchDriver instead of duplicating the matches (for server 1.9+)
> - don't tell users to search for the right snippets (they stack anyway),
>  just explain how they can write one that applies to their device
>
> Cheers,
>  Peter
>

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Sample xsetwacom scripts vetting

[Favux ...]

I'm liking the look of the Table of Contents above a header less overview.

Do you want to make it part of the linuxwacom project mediawiki style?

Favux

On Sun, Feb 27, 2011 at 8:59 PM, Peter Hutterer
 wrote:
>
> thanks. As you can see from the history, I'd like to make this new page the
> main [[xorg.conf.d]] page and link to it from Configuring_X. there's plenty
> of information we should provide that it warrants a separate page.
> especially since we have different configurations for 1.8, 1.9 and 1.10.
>
> I haven't really finished with it yet though, I'll try to edit it over the
> next few days.
>
> The main plan is:
> - use MatchDriver instead of duplicating the matches (for server 1.9+)
> - don't tell users to search for the right snippets (they stack anyway),
>  just explain how they can write one that applies to their device
>
> Cheers,
>  Peter
>

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Sample xsetwacom scripts vetting

[Favux ...]

Hi Peter,

Xorg.conf.d is "finished".  Please review it when you get a chance.

Favux

>> On Sun, Feb 27, 2011 at 8:59 PM, Peter Hutterer
>>  wrote:
>> >
>> > thanks. As you can see from the history, I'd like to make this new page the
>> > main [[xorg.conf.d]] page and link to it from Configuring_X. there's plenty
>> > of information we should provide that it warrants a separate page.
>> > especially since we have different configurations for 1.8, 1.9 and 1.10.
>> >
>> > I haven't really finished with it yet though, I'll try to edit it over the
>> > next few days.
>> >
>> > The main plan is:
>> > - use MatchDriver instead of duplicating the matches (for server 1.9+)
>> > - don't tell users to search for the right snippets (they stack anyway),
>> >  just explain how they can write one that applies to their device
>> >
>> > Cheers,
>> >  Peter
>> >

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Sample xsetwacom scripts vetting

[Favux ...]

Alright, looks good.  I think I like the new tip appearance.  Intriguing anyway.

If we do a separate Bamboo page do we pull the examples along and put
new examples in the Xorg.conf.d?

Favux

On Tue, Mar 1, 2011 at 5:36 PM, Peter Hutterer  wrote:
> On Tue, Mar 01, 2011 at 12:19:42PM -0600, Favux ... wrote:
>> Xorg.conf.d is "finished".  Please review it when you get a chance.
>
> Done, I think. Please let me know if I culled too much. IMO, one example is
> enough and we should rely on our users being smart enough to interpolate
> from the examples.
>
> Cheers,
>  Peter
>
>> >> On Sun, Feb 27, 2011 at 8:59 PM, Peter Hutterer
>> >>  wrote:
>> >> >
>> >> > thanks. As you can see from the history, I'd like to make this new page 
>> >> > the
>> >> > main [[xorg.conf.d]] page and link to it from Configuring_X. there's 
>> >> > plenty
>> >> > of information we should provide that it warrants a separate page.
>> >> > especially since we have different configurations for 1.8, 1.9 and 1.10.
>> >> >
>> >> > I haven't really finished with it yet though, I'll try to edit it over 
>> >> > the
>> >> > next few days.
>> >> >
>> >> > The main plan is:
>> >> > - use MatchDriver instead of duplicating the matches (for server 1.9+)
>> >> > - don't tell users to search for the right snippets (they stack anyway),
>> >> >  just explain how they can write one that applies to their device
>> >> >
>> >> > Cheers,
>> >> >  Peter
>> >> >
>>
>

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Small patch to improve comment

[Favux ...]

Hi,

I'm not sure that follows our little naming convention for wcmUSB.c.
I believe that model was first reported by Tobias Verbeke (12-4-10) as
the Bamboo P&T Special Edition medium CTH-661/L.  Tobias is also the
tested-by on at least the linux-input patch.  If we change it we
should change it to:

/* CTH-661/L */

To bring it into conformity with the /* CTH-461/L */.

We call it the "Wacom Bamboo 2FG 6x8 SE" in wacom_wac.c.

Favux

On Tue, Mar 1, 2011 at 4:32 PM, Peter Hutterer  wrote:
> On Tue, Mar 01, 2011 at 09:58:40AM +0100, Pander wrote:
>> Hi all,
>>
>> Small patch to improve comment in src/wcmUSB.c
>>
>> line 200 CTH-661 -> Bamboo Fun CTH-661SE-NL
>>
>> See attachment. Can someone take this patch under consideration?
>>
>> I also have a question related to this model. Is it correct that the new
>> series Bamboo Fun (the one above with Touch and Pen and Gesture)  are
>> &usbBamboo and the older Bamboo Fun are &usbBambooFun?
>>
>> Thanks,
>>
>> Pander
>
>> --- src/.wcmUSB.c     2011-03-01 09:44:04.274570995 +0100
>> +++ src/wcmUSB.c      2011-03-01 09:45:58.944570994 +0100
>> @@ -200,7 +200,7 @@ static struct
>>       { WACOM_VENDOR_ID, 0xD7, 10, 10, &usbBamboo     }, /* 
>> CTH-461/S */
>>       { WACOM_VENDOR_ID, 0xD8, 10, 10, &usbBamboo     }, /* 
>> CTH-661/S1 */
>>       { WACOM_VENDOR_ID, 0xDA, 10, 10, &usbBamboo     }, /* 
>> CTH-461/L */
>> -     { WACOM_VENDOR_ID, 0xDB, 10, 10, &usbBamboo     }, /* CTH-661 
>> */
>> +     { WACOM_VENDOR_ID, 0xDB, 10, 10, &usbBamboo     }, /* Bamboo 
>> Fun CTH-661SE-NL */
>>
>>       { WACOM_VENDOR_ID, 0x20, 10, 10, &usbIntuos     }, /* Intuos 
>> 4x5 */
>>       { WACOM_VENDOR_ID, 0x21, 10, 10, &usbIntuos     }, /* Intuos 
>> 6x8 */
>
> Chris or Ping, can I have your ACK on this, you know the bamboos better.
> Pander - please submit as a signed-off, git-formatted patch as outlined in
> https://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Submitting_Patches
>
> Cheers,
>  Peter
>
> --
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Small patch to improve comment

[Favux ...]

Hi Chris,

We got it from the label on the back of the tablet to start
distinguishing them from the previous 5 models.  Because some of the
Bamboo models were overlapping.

Pander, the Ubuntu community wikis are maintained by Ubuntu users, not
the linux wacom project.  Loic2 is no longer maintaining the Wacom
wiki pages.  His thread associated with the wiki is here:
http://ubuntuforums.org/showthread.php?t=967147  At least one other
person has done an update.  You could start updating them if you
wanted to.

I'll submit a patch for /* CTH-661/L */ if wanted.

Favux

On Wed, Mar 2, 2011 at 9:56 AM, Pander  wrote:
> On 2011-03-02 16:17, Chris Bagwell wrote:
>> Dave, can you comment on this?  I tend to rely on the information
>> you've collected in Ubuntu forum (probably its in wiki now?).  See
>> below.
>>
>> On Tue, Mar 1, 2011 at 4:32 PM, Peter Hutterer  
>> wrote:
>>> On Tue, Mar 01, 2011 at 09:58:40AM +0100, Pander wrote:
>>>> Hi all,
>>>>
>>>> Small patch to improve comment in src/wcmUSB.c
>>>>
>>>> line 200 CTH-661 -> Bamboo Fun CTH-661SE-NL
>>>>
>>>> See attachment. Can someone take this patch under consideration?
>>>>
>>>> I also have a question related to this model. Is it correct that the new
>>>> series Bamboo Fun (the one above with Touch and Pen and Gesture)  are
>>>> &usbBamboo and the older Bamboo Fun are &usbBambooFun?
>>>>
>>>> Thanks,
>>>>
>>>> Pander
>>>
>>>> --- src/.wcmUSB.c     2011-03-01 09:44:04.274570995 +0100
>>>> +++ src/wcmUSB.c      2011-03-01 09:45:58.944570994 +0100
>>>> @@ -200,7 +200,7 @@ static struct
>>>>       { WACOM_VENDOR_ID, 0xD7, 10, 10, &usbBamboo     }, /* 
>>>> CTH-461/S */
>>>>       { WACOM_VENDOR_ID, 0xD8, 10, 10, &usbBamboo     }, /* 
>>>> CTH-661/S1 */
>>>>       { WACOM_VENDOR_ID, 0xDA, 10, 10, &usbBamboo     }, /* 
>>>> CTH-461/L */
>>>> -     { WACOM_VENDOR_ID, 0xDB, 10, 10, &usbBamboo     }, /* 
>>>> CTH-661 */
>>>> +     { WACOM_VENDOR_ID, 0xDB, 10, 10, &usbBamboo     }, /* Bamboo 
>>>> Fun CTH-661SE-NL */
>>>>
>>>>       { WACOM_VENDOR_ID, 0x20, 10, 10, &usbIntuos     }, /* Intuos 
>>>> 4x5 */
>>>>       { WACOM_VENDOR_ID, 0x21, 10, 10, &usbIntuos     }, /* Intuos 
>>>> 6x8 */
>>>
>>> Chris or Ping, can I have your ACK on this, you know the bamboos better.
>>
>> The following is from info Dave collected:
>>
>> Bamboo P & T Special Edition Small (CTH461/L; Product ID = 0xdA)
>> Bamboo P & T Special Edition Medium (CTH661/L; Product ID = 0xdB)
>>
>> I'm not sure where the pre-existing convention of "/L", "/S1", etc
>> comes from since my Bamboo is simply CTH-460.  Is it from output of
>> lsusb (iProduct) or is it from back of tablet?
>>
>> Following the convention of Small Special Edition tablet, it should
>> read "CTH-661/L".
>
> Hi all, It is fine by me if it is the project's naming convention.
>
> The USB ID list here:
>  https://usb-ids.gowdy.us/read/UD/056a
> has been created without any conventions by many different users. If it
> is necessary, perhaps supply the maintainer of https://usb-ids.gowdy.us
> with a bulk update per email. I understand that technically this might
> not be necessary but documentation wise it could be good to do anyway to
> avoid misunderstandings.
>
> Does anyone have advise on how to troubleshoot stylus and eraser
> pressure levels? In GIMP and Inkscape I ony get nothing or 100% even
> though I followed the instructions from
> https://help.ubuntu.com/community/Wacom
>
> Regards,
>
> Pander
>
>> Chris
>
>
> --
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Patches for supporting Wacom Bamboo Fun CTH-661SE-NL

[Favux ...]

On Wed, Mar 2, 2011 at 4:22 PM, Peter Hutterer  wrote:
> On Tue, Mar 01, 2011 at 01:41:54PM -0800, Ping Cheng wrote:
>> On Sun, Feb 27, 2011 at 12:16 PM, Pander wrote:
>> > Please let me know what to add to
>> >  /lib/udev/rules.d/69-xserver-xorg-input-wacom.rules
>> > for this Wacom Bamboo Fun (pen and touch)
>>
>>
>> This could be something we care. But I am not sure where we need to include
>> it: xf86-input-wacom, the X server driver for version 1.7 and later does
>> not include the .rules file any more. Let's ask the list to see what they
>> want.
>>
>> Do we still need the .rules for static defined devices in xorg.conf?
>
> I'm rather against them. it's much easier these days configuring devices
> through hotplugging (and I think the majority of ppl does just that).
> maintaining a huge list of udev rules seems unnecessary in this regard -
> those who really need them can quickly set them up based on their local
> configurations.
>
> Cheers,
>  Peter

Oops.

Pander, just updated the wacom.rules for your model BambooPT.  See the
mediawiki "Fixed device files with udev":
http://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Fixed_device_files_with_udev

But as Peter points out they are not needed any more unless you are
using the xorg.conf to configure for some reason and want wacom
symlinks.

Favux

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] conf: Add Fujitsu ISDV4 device ID FUJ02e9 to matches

[Favux ...]

Inadvertently left out.

Favux
From 6884bdf00857a93a1c56c74067d324fba73fde41 Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Fri, 4 Mar 2011 12:50:39 -0600
Subject: [PATCH] conf:  Add Fujitsu ISDV4 device ID FUJ02e9 to matches
 Signed-off-by: David Foley 

---
 conf/50-wacom.conf |2 +-
 conf/wacom.fdi |2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/conf/50-wacom.conf b/conf/50-wacom.conf
index b1742bc..dc0bfc0 100644
--- a/conf/50-wacom.conf
+++ b/conf/50-wacom.conf
@@ -16,7 +16,7 @@ EndSection
 
 Section "InputClass"
 Identifier "Wacom serial class identifiers"
-MatchProduct "WACf|FUJ02e5|FUJ02e7"
+MatchProduct "WACf|FUJ02e5|FUJ02e7|FUJ02e9"
 Driver "wacom"
 EndSection
 
diff --git a/conf/wacom.fdi b/conf/wacom.fdi
index 984eaf9..f35d6a5 100644
--- a/conf/wacom.fdi
+++ b/conf/wacom.fdi
@@ -8,7 +8,7 @@
   
 
 
-  
+  
 	input
 	wacom
 	serial.device
-- 
1.7.1

--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] wcmUSB.c: Update BambooPT 0xDB identifier comment

[Favux ...]

Brings it into conformity with the 0xDA and makes it unique.

Favux
From 122cbe6c9abd657999db0151cb0ac045da8d0b63 Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Fri, 4 Mar 2011 13:28:24 -0600
Subject: [PATCH] wcmUSB.c:  Update BambooPT identifier comment

Change 0xDB from CTH-661 to CTH-661/L.

Reported-by: Pander 
Signed-off-by: David Foley 
---
 src/wcmUSB.c |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/src/wcmUSB.c b/src/wcmUSB.c
index db74b15..e1997aa 100644
--- a/src/wcmUSB.c
+++ b/src/wcmUSB.c
@@ -200,7 +200,7 @@ static struct
 	{ WACOM_VENDOR_ID, 0xD7, 10, 10, &usbBamboo }, /* CTH-461/S */
 	{ WACOM_VENDOR_ID, 0xD8, 10, 10, &usbBamboo }, /* CTH-661/S1 */
 	{ WACOM_VENDOR_ID, 0xDA, 10, 10, &usbBamboo }, /* CTH-461/L */
-	{ WACOM_VENDOR_ID, 0xDB, 10, 10, &usbBamboo }, /* CTH-661 */
+	{ WACOM_VENDOR_ID, 0xDB, 10, 10, &usbBamboo }, /* CTH-661/L */
 
 	{ WACOM_VENDOR_ID, 0x20, 10, 10, &usbIntuos }, /* Intuos 4x5 */
 	{ WACOM_VENDOR_ID, 0x21, 10, 10, &usbIntuos }, /* Intuos 6x8 */
-- 
1.7.1

--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] xsetwacom.man: Add 5 parameters

[Favux ...]

Adds 5 parameter descriptions to the xsetwacom manual:  Mode,
PressureCurve, Rotate, TabletPCButton, and Threshold.

Favux
From 94a49c70ab1ecad0edbc393ddca0765d5f32a5ae Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Sun, 6 Mar 2011 14:23:11 -0600
Subject: [PATCH] xsetwacom.man:  Add 5 parameters

Add Mode, PressureCurve, Rotate, TabletPCButton, and Threshold.  Fix typos.

Signed-off-by: David Foley 
---
 man/xsetwacom.man |   48 ++--
 1 files changed, 46 insertions(+), 2 deletions(-)

diff --git a/man/xsetwacom.man b/man/xsetwacom.man
index 67f8439..0ce154e 100644
--- a/man/xsetwacom.man
+++ b/man/xsetwacom.man
@@ -66,7 +66,8 @@ Get the current settings for the parameter on the given device. Note that
 not all parameters are available on all device types. The special parameter
 name "all" may be provided to display all current settings on the device.
 .TP
-By default, options are printed on the commandline in the respective format. The output format may be altered with one of the following options:
+By default, options are printed on the commandline in the respective format.
+The output format may be altered with one of the following options:
 .TP
 \fB-s, --shell\fR
 Display the output in shell format, i.e. as shell commands to xsetwacom to
@@ -105,12 +106,41 @@ the keyboard layout changes.
 Map the tablet's input area to the given output (e.g. "VGA1"). The output
 must specify one of those available through the XRandR extension. A list of
 outputs may be obtained with the xrandr tool. The output mapping
-configuration is a once-off setting and does not track output
+configuration is a once-of setting and does not track output
 reconfigurations; the command needs to be re-run whenever the output
 configuration changes. When used with tablet rotation, the tablet must be
 rotated before it is mapped to the new screen.
 This parameter is write-only and cannot be queried.
 .TP
+\fBMode\fR Absolute|Relative
+Sets the device mode as either Relative (default for the cursor and tablet touch)
+or Absolute (default for the stylus, eraser, and tablet PC touch). Relative
+means pointer tracking for the device will function like a mouse, whereas
+Absolute means the pointer corresponds to the device's actual position on
+the tablet or tablet PC screen.
+.TP
+\fBPressureCurve\fR x1 y1 x2 y2
+A Bezier curve of third order, composed of two anchor points (0,0 & 100,100)
+and two control points that define the curve's shape.  The default curve is
+linear with the two user modifiable control points (x1 y1 x2 y2) having the
+same values as the anchor points, reflecting the tablet's designed pressure
+response (e.g. 0-1023).  Raise the curve (x1y1 x2>y2) for a "firmer" feel.  Sigmoid shaped curves
+are permitted (x1>y1 x2y2).  A valid Bezier curve setting in
+xf86-input-wacom must have all four values between 0 and 100.  Applies only
+to the input tools stylus and eraser.
+.TP
+\fBRotate\fR none|half|cw|ccw
+The wacom driver supports rotation by 90 degree angles.  The valid settings are:
+  none: the tablet is not rotated and uses its natural rotation (the default)
+  half: the tablet is rotated by 180 degrees (upside-down)
+  cw: the tablet is rotated 90 degrees clockwise
+  ccw: the tablet is rotated 90 degrees counter-clockwise
+
+Rotation is tool-specific, rotation of one does not affect other input tools.
+To rotate the complete tablet, rotate all applicable tools (e.g. stylus, eraser,
+cursor, touch).
+.TP
 \fBTabletDebugLevel\fR level
 Set the debug level for this tablet to the given level. This only affects
 code paths that are shared between several tools on the same physical
@@ -118,6 +148,20 @@ tablet. A higher level means more fine-grained debug messages, a level of 0
 turns debugging off for this tool. Requires the driver to be built with
 debugging enabled. See also ToolDebugLevel.
 .TP
+\fBTabletPCButton\fR on|off
+If on, the stylus must be in contact with the screen for any stylus button
+to work.  If off, stylus buttons will work once the stylus is in proximity
+of the tablet (regardless of whether it is touching the screen).  On by default
+for Tablet PCs and off for all other models.  The TabletPCButton parameter
+is only available in xf86-input-wacom-0.10.10 or later.
+.TP
+\fBThreshold\fR level
+Sets the minimum pressure necessary to generate a Button event for the stylus
+tip, eraser, or touch.  The default is 27 with a range of 0 to 2047 (the
+pressure levels of all tablets are normalized to 2048 levels irregardless
+of the actual hardware supported levels).  This parameter is independent of
+the PressureCurve parameter.
+.TP
 \fBToolDebugLevel\fR level
 Set the debug level for this tool to the given level. This only affects code
 paths that are specific to a given tool. A higher level means
-- 
1.7.1

--
What You Don't

Re: [Linuxwacom-devel] Intuos4 L on Ubuntu 10.04

[Favux ...]

HI Ping,

It has been reported by others.  The "fix" has been to go back to
xf86-input-wacom-0.10.8 in Lucid (2.6.32) or update to a release with
X server 1.9, i.e. Maverick (I think 1.8 would work too).  The default
xf86-input-wacom in Lucid (10.04) is 0.10.5.

Favux

On Sun, Mar 6, 2011 at 3:30 PM, Ping Cheng  wrote:
> On Sun, Mar 6, 2011 at 1:53 AM, Eduard Hasenleithner 
> wrote:
>>
>> 2011/3/6 Ping Cheng :
>> > Which X server version are you running? Please post the output of "X
>> > -version" from your system here. If you are running a server older than
>> > 1.7,
>> > you need linuxwacom-0.8.8-11 instead.
>>
>> I'm using the default X server from Ubuntu 10.04:
>>
>> $ X -version
>> X.Org X Server 1.7.6
>> Release Date: 2010-03-17
>>
>> I assume I have to use xf86-input-wacom since the x server is not
>> "older than 1.7".
>
>
> Yes, you need xf86-input-wacom.
>
>>
>> Just as a note: I compiled xf86-input-wacom-0.10.8 which is the last
>> release before commit 19c24dc4e852bae384f16411d5f59add487be5f0 and it
>> appears to work correctly.
>
>
> Oh, too bad. I wonder why the others have not seen the issue yet. Do you
> have multi-monitor setup? It's a mapping issue for sure.
>
> Ping
>
> --
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>
>

--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] [Patch v2 1/1] xsetwacom.man: Add 5 parameters

[Favux ...]

Hi Peter,

Made the suggested changes.

Favux
From aafa3b221888cc8c97b244010842cbaa96ac5951 Mon Sep 17 00:00:00 2001
From: David 
Date: Mon, 7 Mar 2011 12:56:35 -0600
Subject: [Patch v2 1/1] xsetwacom.man:  Add 5 parameters

Add Mode, PressureCurve, Rotate, TabletPCButton, and Threshold.  And other changes.

Signed-off-by: David Foley 
---
 man/xsetwacom.man |   66 -
 1 files changed, 55 insertions(+), 11 deletions(-)

diff --git a/man/xsetwacom.man b/man/xsetwacom.man
index 67f8439..05e3450 100644
--- a/man/xsetwacom.man
+++ b/man/xsetwacom.man
@@ -66,7 +66,8 @@ Get the current settings for the parameter on the given device. Note that
 not all parameters are available on all device types. The special parameter
 name "all" may be provided to display all current settings on the device.
 .TP
-By default, options are printed on the commandline in the respective format. The output format may be altered with one of the following options:
+By default, options are printed on the commandline in the respective format.
+The output format may be altered with one of the following options:
 .TP
 \fB-s, --shell\fR
 Display the output in shell format, i.e. as shell commands to xsetwacom to
@@ -84,16 +85,20 @@ not all parameters are writable, some are read-only and result in an error
 when trying to be modified.
 
 .SH "PARAMETERS"
+.LP
+Not all parameters are available on all tools.  Use the get command with the
+parameter or "all" parameter for specific input tool applicable parameters
+and current settings.
 .TP
 \fBArea\fR x1 y1 x2 y2
-Specify the tablet input area in device coordinates in the form top left
+Set the tablet input area in device coordinates in the form top left
 x/y and bottom right x/y. Top left and bottom right are defined in the
 device's native orientation, regardless of the actual rotation currently
-applied. Input outside of these coordinates will be clipped
-to the edges of the area defined.
+applied. Input outside of these coordinates will be clipped to the edges
+of the area defined.  Default:  0 0 x2 y2; with x2 and y2 tablet specific.
 .TP
 \fBButton\fR button-number [mapping]
-Get or set the specified button. The mapping may be a button number to map
+Set the specified button. The mapping may be a button number to map
 the physical button to. e.g. a mapping of button 1 to 3 means
 a button 1 press will be interpreted as right click. Alternatively, a
 mapping in the form of "key +a +shift b -shift -a" converts the button into a series
@@ -105,25 +110,64 @@ the keyboard layout changes.
 Map the tablet's input area to the given output (e.g. "VGA1"). The output
 must specify one of those available through the XRandR extension. A list of
 outputs may be obtained with the xrandr tool. The output mapping
-configuration is a once-off setting and does not track output
+configuration is a onetime setting and does not track output
 reconfigurations; the command needs to be re-run whenever the output
 configuration changes. When used with tablet rotation, the tablet must be
 rotated before it is mapped to the new screen.
 This parameter is write-only and cannot be queried.
 .TP
+\fBMode\fR Absolute|Relative
+Set the device mode as either Relative or Absolute. Relative means pointer
+tracking for the device will function like a mouse, whereas Absolute means
+the pointer corresponds to the device's actual position on the tablet or
+tablet PC screen.  Default:  Absolute for stylus, eraser and tablet PC touch;
+Relative for cursor and tablet touch.
+.TP
+\fBPressureCurve\fR x1 y1 x2 y2
+A Bezier curve of third order, composed of two anchor points (0,0 and 100,100)
+and two user modifiable control points that define the curve's shape.  Raise
+the curve (x1y1 x2>y2)
+for a "firmer" feel.  Sigmoid shaped curves are permitted (x1>y1 x2y2).  Default:  0 0 100 100, a linear curve; range of 0 to 100 for
+all four values.
+.TP
+\fBRotate\fR none|half|cw|ccw
+Set the tablet to the given rotation:
+  none: the tablet is not rotated and uses its natural rotation
+  half: the tablet is rotated by 180 degrees (upside-down)
+  cw: the tablet is rotated 90 degrees clockwise
+  ccw: the tablet is rotated 90 degrees counter-clockwise
+
+Rotation is tool-specific, rotation of one does not affect other input tools.
+When the tablet is physically rotated, rotate all tools to the corresponding
+orientation.  Default:  none
+.TP
 \fBTabletDebugLevel\fR level
 Set the debug level for this tablet to the given level. This only affects
 code paths that are shared between several tools on the same physical
 tablet. A higher level means more fine-grained debug messages, a level of 0
 turns debugging off for this tool. Requires the driver to be built with
-debugging enabled. See also ToolDebugLevel.
+debugging enabled. See also ToolDebugLevel.  Default:  0, range of 0 to 12.
+.TP
+\fBTabletPCBu

Re: [Linuxwacom-devel] Intuos4 L on Ubuntu 10.04

[Favux ...]

Status update:  Patch "Accepted xorg-server into lucid-proposed".
Eduard already tested and it works.  See Launchpad bug report:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/730488

Favux

On Tue, Mar 8, 2011 at 5:47 PM, TImo Aaltonen  wrote:
>
> There are ways to help ubuntu-x@ make that happen. First file a bug,
> then attach relevant information to fix it, like a link to/hash of a
> commit in a newer release. If it's something that applies relatively
> cleanly and doesn't look too scary, it could even get accepted. Then it
> takes some time to get a proposed fix out for testing, and after it has
> been confirmed to work without regressions it's released to the public.
>

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH 4/4] Require RawSample to be at least 1

[Favux ...]

Hi Chris,

Now you tell me.  :)

Actually I vaguely remember that patch.  Appreciate it if you could
refresh my memory and direct me to it.  I have some probable testers,
because they are complaining of stylus "jitters".  Let me quote
BackBONE7:

 > Than's for the tip! Hover works great.

> The jumps seem to be independet from RawSample, Suppress and Threshold.
>I even switched gestures off, and did a reset of the Tablet Area.

> If there would be a filter that ignores events that are further away from the 
> last cursor position as, lets say 30 to 80 Pixels, that might help. I 
> downloaded the Source and thought maybe i can do a quick hack to test it, but 
> i > don't understand all of it, needles to say i'm not a good programmer.

> I am sure there is a solution, i'm still frustraded thou.

And we now know why RawSample wasn't doing anything.

Favux

On Wed, Mar 9, 2011 at 10:41 AM, Chris Bagwell  wrote:
> On Tue, Mar 8, 2011 at 8:50 PM, Peter Hutterer  
> wrote:
>> On Tue, Mar 08, 2011 at 05:50:45PM -0800, Jason Gerecke wrote:
>>> I made the mistake of setting this to zero and then bringing my
>>> pen into proximity. Ooops. X crashed. Looks like mathematics
>>> still can't handle getting the average of zero things ;)
>>>
>>> Signed-off-by: Jason Gerecke 
>>> ---
>>>  src/wcmXCommand.c |    2 +-
>>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/src/wcmXCommand.c b/src/wcmXCommand.c
>>> index 4207dbe..e589e37 100644
>>> --- a/src/wcmXCommand.c
>>> +++ b/src/wcmXCommand.c
>>> @@ -620,7 +620,7 @@ int wcmSetProperty(DeviceIntPtr dev, Atom property, 
>>> XIPropertyValuePtr prop,
>>>               if ((values[0] < 0) || (values[0] > 100))
>>>                       return BadValue;
>>>
>>> -             if ((values[1] < 0) || (values[1] > XWACOM_MAX_SAMPLES))
>>> +             if ((values[1] < 1) || (values[1] > XWACOM_MAX_SAMPLES))
>>>                       return BadValue;
>>>
>>>               if (!checkonly)
>>> --
>>> 1.7.1
>>
>> doesn't this need the same check in wcmParseOptions?
>
> Yes, the whole if() should be added to new RawSample (patch 3 of 4).
>
>>
>> also, out of interest - what does RawSample actually do? there's nothing in
>> the man page.
>
> Perhaps we can rename the option while we are here?
>
> Its value is the window size on sliding window average done on
> incoming raw samples with default of 4.  SampleWindow or SampleCount
> may be better names.
>
> If someone makes a man page patch, its probably worth noting that
> ISDv4 do not currently do averaging.  I had a patch that enables that
> but needs testing by someone with said device.  I'm a little confused
> why ISDv4 people are not complaining about non-smooth drawing.
>
> Chris
>
> --
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH] remove per-device filter function

[Favux ...]

Hi Chris,

BackBONE7 reports the patch didn't work for his stylus issue.  Sounds
more like jumps than jitters.

He sees:
(WW) Serial Wacom Tablet stylus: bad data at 7 v=91 l=9
(WW) Serial Wacom Tablet stylus: bad data at 7 v=91 l=9
(WW) Serial Wacom Tablet stylus: bad data at 8 v=91 l=9
With both ToolDebugLevel for stylus and TabletDebugLevel.

I don't know if I'm seeing jumps in his debug Xorg.0.logs or not. What
I do notice is that it'll often hold the same x & y locations for 2 to
5 times and then go to the next one.  Since he updated to
xf86-input-wacom-0.10.11+ I'm wondering if the filter is holding onto
old values too long. Maybe the serial tablets don't stream in as much
data as the usb ones do? So the filtering window or average is wrong
for them? Or maybe it's just a few serial digitizers like his. A
sample of what I'm talking about is attached.  He supplied a complete
Xorg.0.log with both ToolDebugLevel for stylus and TabletDebugLevel
turned up.

Favux


BackBONE7_ISDV4-Toshiba-Portege-M700 _debug.logs
Description: Binary data
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH] remove per-device filter function

[Favux ...]

Hi Chris,

My fault.  Yes the Toshiba Portege M700 and M750's are serial
tabletPCs with 1FGT.  So good guess.  I believe the M750's can have
2FGT also, depending on what was ordered.

I suggested your change.  Hopefully he'll want to try it.

Dave

On Fri, Mar 11, 2011 at 10:30 AM, Chris Bagwell  wrote:
> On Thu, Mar 10, 2011 at 2:26 PM, Favux ...  wrote:
>> Hi Chris,
>>
>> BackBONE7 reports the patch didn't work for his stylus issue.  Sounds
>> more like jumps than jitters.
>>
>> He sees:
>>    (WW) Serial Wacom Tablet stylus: bad data at 7 v=91 l=9
>>    (WW) Serial Wacom Tablet stylus: bad data at 7 v=91 l=9
>>    (WW) Serial Wacom Tablet stylus: bad data at 8 v=91 l=9
>> With both ToolDebugLevel for stylus and TabletDebugLevel.
>
> In what context are these messages seen?  I recall something about
> right when stylus is hovering between in and out of proximity?
>
> The above says it received a packet of length 7 and 8 when it was
> expecting a packet of length 9.
>
> There is some logic in wcmISDV4.c related to packet length size and
> its based on status of proximity.  That might be get confused by
> hovering.
>
> Length of 7 is valid packet size for pen+touch tablets.  Is this one
> such device?  And the v=91 value also looks touch-ish.
>
> Also, I'm wondering if wcmSerialValidate should return a value of
> "n-1" instead of "n" so that it attempts to restart at what looks like
> a new header?  If it becomes confused on 1 packet length, it looks
> like it may feed on itself and ignore several?  I could be misreading
> here.
>
> If the user wants to try it, shouldn't hurt much.  Try editing
> wcmISDV4.c line #182 and change "return n;" to "return n-1;".
>
>>
>> I don't know if I'm seeing jumps in his debug Xorg.0.logs or not. What
>> I do notice is that it'll often hold the same x & y locations for 2 to
>> 5 times and then go to the next one.
>
> One thing I notice during the hangs from snippet you emailed is that
> it hangs until this happens a couple of times:
>
> (II) /dev/ttyS0 (10:wcmReadPacket): buffer has 8 bytes
>
> Packets of 9 and 7 are OK but not 8.  Something is going wrong but
> eventually cleans up after itself.  The above "n-1" change may allow
> it to correct faster and less jumps.
>
>> Since he updated to
>> xf86-input-wacom-0.10.11+ I'm wondering if the filter is holding onto
>> old values too long. Maybe the serial tablets don't stream in as much
>> data as the usb ones do? So the filtering window or average is wrong
>> for them? Or maybe it's just a few serial digitizers like his. A
>> sample of what I'm talking about is attached.  He supplied a complete
>> Xorg.0.log with both ToolDebugLevel for stylus and TabletDebugLevel
>> turned up.
>
> I'm currently guessing its because of discarded data but I could be
> totally wrong of course.  I think it may take a developer with tablet
> to figure this out totally.
>
> Chris
>

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] [PATCH] xsetwacom.man: add RawSample and Suppress parameters

[Favux ...]

Adds the RawSample and Suppress parameters to the xsetwacom manual.

Dave
From eb726c7a8202800ce799cabcc58650f087b61e68 Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Sun, 13 Mar 2011 17:57:10 -0500
Subject: [PATCH] xsetwacom.man:  add RawSample and Suppress parameters

Add RawSample and Suppress to parameter description table.  Fix whitespace issue.

Signed-off-by: David Foley 
---
 man/xsetwacom.man |   10 --
 1 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/man/xsetwacom.man b/man/xsetwacom.man
index c5494bc..a94b3a2 100644
--- a/man/xsetwacom.man
+++ b/man/xsetwacom.man
@@ -131,6 +131,9 @@ for a "firmer" feel.  Sigmoid shaped curves are permitted (x1>y1 x2y2).  Default:  0 0 100 100, a linear curve; range of 0 to 100 for
 all four values.
 .TP
+\fBRawSample\fR level
+Set the sample window size (a sliding average sampling window) for incoming input tool raw data points.  Default:  4, range of 1 to 100.
+.TP
 \fBRotate\fR none|half|cw|ccw
 Set the tablet to the given rotation:
   none: the tablet is not rotated and uses its natural rotation
@@ -142,6 +145,9 @@ Rotation is tool-specific, rotation of one does not affect other input tools.
 When the tablet is physically rotated, rotate all tools to the corresponding
 orientation.  Default:  none
 .TP
+\fBSuppress\fR level
+Set the delta (difference) cutoff level for further processing of incoming input tool coordinate values.  For example a X or Y coordinate event will be sent only if the change between the current X or Y coordinate and the previous one is greater than the Suppress value.  The same applies to pressure level (Z coordinate) and Tilt rotation values.  With a current absolute wheel (AbsWheel) or Tilt value the delta between it and the previous value must be equal to or greater than the Suppress value in order to be sent on.  Suppress is a tablet wide parameter.  A specified delta level for one input tool is applied to all input tool coordinates.  To disable suppression use a level of 0.  Default:  2, range of 0 to 20.
+.TP
 \fBTabletDebugLevel\fR level
 Set the debug level for this tablet to the given level. This only affects
 code paths that are shared between several tools on the same physical
@@ -152,8 +158,8 @@ debugging enabled. See also ToolDebugLevel.  Default:  0, range of 0 to 12.
 \fBTabletPCButton\fR on|off
 If on, the stylus must be in contact with the screen for a stylus side button
 to work.  If off, stylus buttons will work once the stylus is in proximity
-of the tablet (regardless of whether it is touching the screen).  Default:
-on for Tablet PCs; off for all other models.
+of the tablet (regardless of whether it is touching the screen).  Default:  on
+for Tablet PCs; off for all other models.
 .TP
 \fBThreshold\fR level
 Set the minimum pressure necessary to generate a Button event for the stylus
-- 
1.7.1

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [draft-patch] OLED setting for xsetwacom

[Favux ...]

Hi,

usbfs was deprecated in kernel 2.6.31 I think.  Certainly by 2.6.32
Ubuntu (Lucid 10.04) and several other distributions dropped it.  This
all happened at about the same time.  There was some conflict with
changes in udev.  Apparently since usbfs implicitly changes event
behavior it was breaking the newer udev.  Hence Christoph Karg's
userland OLED app. (he just posted an update in linuxwacom-devel) and
San's modifications of it for profiles and other stuff.

Favux

On Wed, Mar 23, 2011 at 12:53 PM, Ping Cheng  wrote:
> On Wed, Mar 23, 2011 at 3:36 AM, Eduard Hasenleithner 
> wrote:
>>
>> 2011/3/23 Peter Hutterer :
>> > On Tue, Mar 22, 2011 at 10:47:12PM +0100, Eduard Hasenleithner wrote:
>> >> For accessing USB-FS, I already considered libusb, just to find out
>> >> that it does not (yet?) provide the USBDEVFS_IOCTL. Ideal would be
>> >> IOCTL tunneling through the linux event subsystem in the kernel, but
>> >> this is not supported by the linux event subsystem.
>> >
>> > can we make it so in the kernel?
>> > (of course, by "we" I mean "you" ;)
>>
>> On one hand I consider my skills sufficient for adding an "ioctl
>> passthrough" to the event subsystem. On a few occasions in the past,
>> patches written by myself already went into the linux kernel. But on
>> the other hand, I have no "channel" to the kernel maintainers of the
>> input (and event) subsystem. From the kernel maintainers I often get
>> the feeling they want as much as possible being done in Userspace.
>> Therefore I would prefer - at least for now - not to rely on kernel
>> infrastructure changes.
>>
>> >> >> * Can we use the rendering capabilities of the X-server and send an
>> >> >> PIXMAP by means of XChangeDeviceProperty?
>> >> >
>> >> > I think this may be the best option though I need some confirmation
>> >> > from the
>> >> > graphics guys. That way the property code would be quite simple too,
>> >> > the
>> >> > property data is simply the drawable ID.
>> >>
>> >> One question is what happens to the drawable when xsetwacom exits.
>> >
>> > Depends on whether we want it to be write-only or read-write. if it's
>> > write-only, we can delete it. otherwise, we need to leave it around so
>> > that
>> > you can read it later.
>> > Pixmaps usually get deleted, but can be made permanent with
>> > XSetCloseDownMode, afaict.
>>
>> >From my point of view, the image has also to be permanent for the
>> write-only case. Changing a single image involves (like for the button
>> actions) following steps
>> 1. Read the list of Atoms
>> 2. Change the Atom of the Image you want to change
>> 3. Write the list of atoms again
>>
>> When the x11 wacom driver gets the new list of atoms, it also has to
>> check the "untouched" images for changes. If they are already gone
>> this might cause a problem. Or worse, wrong images are loaded onto the
>> keys due to ID space collisions between subsequent xsetwacom
>> invocations.
>>
>> It does not have to be that way, it is just that my X11 programming
>> knowlege is now two weeks old, and is therefore not very solid.
>>
>> >> Another question is, if the drawable (4-bit gray) is supported by all
>> >> (relevant) X-Servers and their display drivers (assuming that we don't
>> >> want to write an additional display driver for the OLEDs of the
>> >> tablet). PIXMAPs (1-bit) are supposed to be supported by all X-Servers
>> >> though. Having written this, and although it might fit very well into
>> >> the X11 Protocol semantics, using in-client rendering might be much
>> >> easier and have less potential compatibility and handling problems.
>> >
>> > the important thing here: the pixmap does not necessarily have to be in
>> > the
>> > same format as the driver requires. the driver could do the pixel
>> > transformation in-driver to support a more standard format 8 bit for
>> > example (or even multiple formats if necessary).
>>
>> If this can be handled "straight-forward" in about 200 lines of code -
>> fine. If it needs considerably more, or if the code is very fragile
>> (e.g. breaks often due to XOrg code/driver changes) i'm hesitant to go
>> that way.
>>
>> >> >> +#define WACOM_SET_LED_IMG _IOW(0x00, 0x00, struct wacom_led_img)
>> >> >> +#define WACO

Re: [Linuxwacom-devel] [draft-patch] OLED setting for xsetwacom

[Favux ...]

Interesting.  That's why I didn't say anything earlier.  Supposedly
you could use some symlinks to get around the lack of a /proc/bus/usb,
but we could never get that working.

Launchpad bug report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/488274

Favux

On Wed, Mar 23, 2011 at 1:56 PM, Eduard Hasenleithner
 wrote:
> 2011/3/23 Favux ... :
>> usbfs was deprecated in kernel 2.6.31 I think.  Certainly by 2.6.32
>> Ubuntu (Lucid 10.04) and several other distributions dropped it.  This
>> all happened at about the same time.  There was some conflict with
>> changes in udev.  Apparently since usbfs implicitly changes event
>> behavior it was breaking the newer udev.  Hence Christoph Karg's
>> userland OLED app. (he just posted an update in linuxwacom-devel) and
>> San's modifications of it for profiles and other stuff.
>
> Very strange. I'm developing the xsetwacom led extensions on my Lucid
> (kernel 2.6.32) install. And it works like a charm. Maybe there is
> some misunderstanding about "dropped usbfs". In fact, usbfs was
> dropped in the sense, that it is no longer possible to mount it on
> /proc/bus/usb. Nevertheless, the functionality is still available
> using /dev/bus/usb.
>
> br,
> Eduard
>

--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [RFC] wdaemon on linuxwacom.sf.net

[Favux ...]

Hi Peter,

That sounds reasonable to me given that we are still linking to Aris'
repository in the mediawiki's Linuxwacom HOWTO and FAQ:
http://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Linuxwacom_HOWTO#Hotplugging_the_device

Favux

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Cintiq: TabletPCButton = on?

[Favux ...]

Hi Jason,

It should be off for a Cintiq as far as I know.  Maybe WCM_LCD and
WCM_TPC are getting confabulated somewhere?

Favux

On Mon, Apr 11, 2011 at 1:33 PM, Jason Gerecke  wrote:
> Right now the man page indicates that TabletPCButton is 'on' for
> TabletPCs and 'off' for everything else. It appears that this option
> is also 'on' for my Cintiq 21UX. Is this just less-than-clear
> documentation, or a driver bug? I was leaning to the first (as they're
> both "transparent" tablets), but the default behavior under Windows
> appears to be equivalent to 'off'.
>
> Jason
>
> ---
> Day xee-nee-svsh duu-'ushtlh-ts'it;
> nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it.
> Huu-chan xuu naa~-gha.
>
> --
> Forrester Wave Report
> Recovery time is now measured in hours and minutes not days.
> key insights are discussed in the 2010 Forrester Wave Report as
> part of an in-depth evaluation of disaster recovery service providers.
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH 2/4] man: Fix hyphenation error

[Favux ...]

Onetime does not require a hyphen.  Either usage is correct:
http://www.merriam-webster.com/dictionary/onetime  It was substituted
as a synonym for one-off (once-off in Australian).

I feel silly talking about this again.  :(

On Tue, Apr 12, 2011 at 2:06 PM, Jason Gerecke  wrote:
> What else needs to be said?
>
> Signed-off-by: Jason Gerecke 
> ---
>  man/xsetwacom.man |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/man/xsetwacom.man b/man/xsetwacom.man
> index 910f873..5e6c3f0 100644
> --- a/man/xsetwacom.man
> +++ b/man/xsetwacom.man
> @@ -117,7 +117,7 @@ be present in one action if desired: for example "key 
> +ctrl button 5 key -ctrl".
>  Map the tablet's input area to the given output (e.g. "VGA1"). The output
>  must specify one of those available through the XRandR extension. A list of
>  outputs may be obtained with the xrandr tool. The output mapping
> -configuration is a onetime setting and does not track output
> +configuration is a one-time setting and does not track output
>  reconfigurations; the command needs to be re-run whenever the output
>  configuration changes. When used with tablet rotation, the tablet must be
>  rotated before it is mapped to the new screen.
> --
> 1.7.4.1
>
>
> --
> Forrester Wave Report - Recovery time is now measured in hours and minutes
> not days. Key insights are discussed in the 2010 Forrester Wave Report as
> part of an in-depth evaluation of disaster recovery service providers.
> Forrester found the best-in-class provider in terms of services and vision.
> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] Rotate parameter

[Favux ...]

While preparing to modify the Rotate parameter entries in the
mediawiki to bring them up to date with 0.11.0 I tested the parameter.
 It is not tablet wide with a Bamboo Pen & Touch.  Rotating the stylus
does rotate the eraser but not touch and rotating touch does not
rotate the stylus or eraser.  I suspect this is true of any usb tablet
with touch.  I assume touch is rotated with a ISDV4 device when the
stylus is rotated but I guess I'd like that confirmed.

It appears we may need to modify Rotate in man xsetwacom again.  Something like:
Rotation  is a device-wide option: rotation of one parent or dependent
input tool affects all other tools associated with the same device.
Most tablets have only one device so for them the parameter amounts to
a tablet-wide option.  However usb tablets with touch have two
devices, i.e. a parent tool (stylus) and a second parent tool (touch)
and each needs a separate rotation command.  When the tablet is
physically rotated, rotate any parent or dependent tool for a device
to the corresponding orientation.

Favux

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Intelligent solution to gestures?

[Favux ...]

If you have Ubuntu Natty (11.04) or the equivalent (Xserver 1.10,
kernel 2.6.37 or 38) you can place your BambooPT touch on the Synaptic
driver if you prefer.

Favux

--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] wcmCommon.c: fix cw and ccw swap

[Favux ...]

Responding to reports involving the recent Ubuntu release discovered
cw and ccw have been reversed since the "Rework rotation and scaling
into tablet areas." commit:
http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/xf86-input-wacom;a=commit;h=19c24dc4e852bae384f16411d5f59add487be5f0

This patch returns cw and ccw to the expected behavior.

Dave
From 03d6d3d64acf838ed6f91743a6baf1e8166d4174 Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Thu, 12 May 2011 14:19:28 -0500
Subject: [PATCH] wcmCommon.c:  fix cw and ccw swap

Return cw and ccw to expected behavior.

Tested-by: Buran Ayuthia 
Signed-off-by: David Foley 
---
 src/wcmCommon.c |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/wcmCommon.c b/src/wcmCommon.c
index 7f8dfb1..c8aa9e4 100644
--- a/src/wcmCommon.c
+++ b/src/wcmCommon.c
@@ -479,9 +479,9 @@ void wcmRotateAndScaleCoordinates(InputInfoPtr pInfo, int* x, int* y)
    axis_x->max_value, axis_x->min_value);
 	}
 
-	if (common->wcmRotate == ROTATE_CCW)
+	if (common->wcmRotate == ROTATE_CW)
 		*y = axis_y->max_value - (*y - axis_y->min_value);
-	else if (common->wcmRotate == ROTATE_CW)
+	else if (common->wcmRotate == ROTATE_CCW)
 		*x = axis_x->max_value - (*x - axis_x->min_value);
 	else if (common->wcmRotate == ROTATE_HALF)
 	{
-- 
1.7.1

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] wcmValidateDevice.c: Add 0xE6

[Favux ...]

Adds the E6 2FGT tablet PC digitizer.  Currently represented by the
Lenovo X220t, which is the first USB ThinkPad I am aware of.

Dave
From f2ecccaf2d668424715645fc377b11c89b9d370e Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Tue, 24 May 2011 17:12:22 -0500
Subject: [PATCH] wcmValidateDevice.c:  Add 0xE6

Adds the E6 2FGT tablet PC.

Tested-by: Ethan Schoonover 
Signed-off-by: David Foley 
---
 src/wcmValidateDevice.c |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/src/wcmValidateDevice.c b/src/wcmValidateDevice.c
index b177713..409a42f 100644
--- a/src/wcmValidateDevice.c
+++ b/src/wcmValidateDevice.c
@@ -254,6 +254,7 @@ int wcmDeviceTypeKeys(InputInfoPtr pInfo)
 
 		case 0xE2: /* TPC with 2FGT */
 		case 0xE3: /* TPC with 2FGT */
+		case 0xE6: /* TPC with 2FGT */
 			priv->common->tablet_type = WCM_TPC;
 			priv->common->tablet_type |= WCM_LCD;
 			break;
-- 
1.7.1

--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] input-wacom_wacom_wac.c: Add 0xE6

[Favux ...]

Adds the E6 2FGT tablet PC digitizer to input-wacom.  Already in at
least the 2.6.38 kernel.

Dave
From fc495f75d7f2f8501ff2921c2a4cbc836df0f7d9 Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Tue, 24 May 2011 18:48:39 -0500
Subject: [PATCH] input-wacom_wacom_wac.c:  Add 0xE6

Adds the E6 2FGT tablet PC.

Signed-off-by: David Foley 
---
 2.6.30/wacom_wac.c |3 +++
 2.6.36/wacom_wac.c |3 +++
 2 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/2.6.30/wacom_wac.c b/2.6.30/wacom_wac.c
index 5cb8e6f..7188a54 100755
--- a/2.6.30/wacom_wac.c
+++ b/2.6.30/wacom_wac.c
@@ -1431,6 +1431,8 @@ static const struct wacom_features wacom_features_0xE2 =
 	{ "Wacom ISDv4 E2",   WACOM_PKGLEN_TPC2FG,26202, 16325,  255,  0, TABLETPC2FG };
 static const struct wacom_features wacom_features_0xE3 =
 	{ "Wacom ISDv4 E3",   WACOM_PKGLEN_TPC2FG,26202, 16325,  255,  0, TABLETPC2FG };
+static const struct wacom_features wacom_features_0xE6 =
+	{ "Wacom ISDv4 E6",   WACOM_PKGLEN_TPC2FG,27760, 15694,  255,  0, TABLETPC2FG };
 static const struct wacom_features wacom_features_0x47 =
 	{ "Wacom Intuos2 6x8",WACOM_PKGLEN_INTUOS,20320, 16240, 1023, 31, INTUOS };
 static const struct wacom_features wacom_features_0x6004 =
@@ -1521,6 +1523,7 @@ const struct usb_device_id wacom_ids[] = {
 	{ USB_DEVICE_WACOM(0x9F) },
 	{ USB_DEVICE_WACOM(0xE2) },
 	{ USB_DEVICE_WACOM(0xE3) },
+	{ USB_DEVICE_WACOM(0xE6) },
 	{ USB_DEVICE_WACOM(0x47) },
 	{ USB_DEVICE_LENOVO(0x6004) },
 	{ }
diff --git a/2.6.36/wacom_wac.c b/2.6.36/wacom_wac.c
index 6f71659..aac8fda 100644
--- a/2.6.36/wacom_wac.c
+++ b/2.6.36/wacom_wac.c
@@ -1381,6 +1381,8 @@ static const struct wacom_features wacom_features_0xE2 =
 	{ "Wacom ISDv4 E2",   WACOM_PKGLEN_TPC2FG,26202, 16325,  255,  0, TABLETPC2FG };
 static const struct wacom_features wacom_features_0xE3 =
 	{ "Wacom ISDv4 E3",   WACOM_PKGLEN_TPC2FG,26202, 16325,  255,  0, TABLETPC2FG };
+static const struct wacom_features wacom_features_0xE6 =
+	{ "Wacom ISDv4 E6",   WACOM_PKGLEN_TPC2FG,27760, 15694,  255,  0, TABLETPC2FG };
 static const struct wacom_features wacom_features_0x47 =
 	{ "Wacom Intuos2 6x8",WACOM_PKGLEN_INTUOS,20320, 16240, 1023, 31, INTUOS };
 static const struct wacom_features wacom_features_0xD0 =
@@ -1491,6 +1493,7 @@ const struct usb_device_id wacom_ids[] = {
 	{ USB_DEVICE_WACOM(0x9F) },
 	{ USB_DEVICE_WACOM(0xE2) },
 	{ USB_DEVICE_WACOM(0xE3) },
+	{ USB_DEVICE_WACOM(0xE6) },
 	{ USB_DEVICE_WACOM(0x47) },
 	{ USB_DEVICE_LENOVO(0x6004) },
 	{ }
-- 
1.7.1

--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH 2/2] Add support for Device Product ID property.

[Favux ...]

On Thu, Jun 2, 2011 at 6:13 PM, Peter Hutterer  wrote:
> On Thu, Jun 02, 2011 at 09:19:34AM -0500, Chris Bagwell wrote:
>> For the Fujitsu table, I'm thinking we should set it WACOM vendor_id
>> because we are setting tablet_id to values only meaningful when
>> product_id is WACOM.
>
> are the tablets 100% compatible though?
>

The Fujitsu tablets seem fine once they get initialized.  That's the
main problem they seem to have.  A lot of them have to restart X
before the digitizer starts working.  It won't work after a reboot.
This is sort of a pain for them.  Especially since the key combination
to restart X is no longer enabled by default.

Favux

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] 50-wacom-conf issues

[Favux ...]

Just a heads up.  We just finished setting up unclepedro's Thinkpad
X220t (first usb instead of ISDV4 Thinkpad) in Ubuntu 11.04 (Natty
Narwhal) on Ubuntu forums.  According to xinput list the kernel is
exporting the two parent devices as:

ISD-V4 Pen
ISD-V4 Finger

So we had to add the keyword ISD-V4 to the MatchProduct line:

MatchProduct "Wacom|WACOM|ISD-V4|Hanwang"

Any thoughts on how to handle this?


Also the Waltop tablets seem to be working fine on xf86-input-wacom
with kernel 2.6.38 thanks to Nikolai Kondrashov's kernel patches.  I'm
thinking it is time to add Waltop back into the match line:

MatchProduct "Wacom|WACOM|WALTOP|Hanwang"

Any objections?

Favux

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] 50-wacom-conf issues

[Favux ...]

On Tue, Jun 21, 2011 at 12:25 AM, Ping Cheng  wrote:
> On Mon, Jun 20, 2011 at 11:24 AM, Favux ...  wrote:
>>
>> Just a heads up.  We just finished setting up unclepedro's Thinkpad
>> X220t (first usb instead of ISDV4 Thinkpad) in Ubuntu 11.04 (Natty
>> Narwhal) on Ubuntu forums.  According to xinput list the kernel is
>> exporting the two parent devices as:
>>
>> ISD-V4 Pen
>> ISD-V4 Finger
>>
>> So we had to add the keyword ISD-V4 to the MatchProduct line:
>
> ISD-V4 is from the wacom kernel driver. It is for the USB tablet in Lenovo
> laptop.
>
> Ping
>
>>
>> MatchProduct "Wacom|WACOM|ISD-V4|Hanwang"
>>
>> Any thoughts on how to handle this?

In that case should ISD-V4 be added as a keyword to the match line?

Favux

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] 50-wacom-conf issues

[Favux ...]

Thank you Ping.  Will do.  WALTOP and ISD-V4 both.

>From Ethan Schoonover's X220t in Arch:
http://sourceforge.net/mailarchive/forum.php?thread_name=BANLkTi%3DgPGTuwn-6kv4AuKSuit4xD_-kjw%40mail.gmail.com&forum_name=linuxwacom-discuss

Bus 002 Device 003: ID 056a:00e6 Wacom Co., Ltd

P: /devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input7/event7
N: input/event7
S: input/tablet-tpc-e6-touch
S: input/wacom-touch
S: input/by-id/usb-Tablet_ISD-V4-event-if01
S: input/by-path/pci-:00:1d.0-usb-0:1.5:1.1-event
E: UDEV_LOG=3
E: 
DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input7/event7
E: MAJOR=13
E: MINOR=71
E: DEVNAME=/dev/input/event7
E: SUBSYSTEM=input
E: WACOM_TYPE=touch
E: ID_INPUT=1
E: ID_INPUT_TOUCHSCREEN=1
E: ID_VENDOR=Tablet
E: ID_VENDOR_ENC=Tablet
E: ID_VENDOR_ID=056a
E: ID_MODEL=ISD-V4
E: ID_MODEL_ENC=ISD-V4
E: ID_MODEL_ID=00e6
E: ID_REVISION=0139
E: ID_SERIAL=Tablet_ISD-V4
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_USB_INTERFACES=:03:
E: ID_USB_INTERFACE_NUM=01
E: ID_USB_DRIVER=wacom
E: ID_PATH=pci-:00:1d.0-usb-0:1.5:1.1
E: DEVLINKS=/dev/input/tablet-tpc-e6-touch /dev/input/wacom-touch
/dev/input/by-id/usb-Tablet_ISD-V4-event-if01
/dev/input/by-path/pci-:00:1d.0-usb-0:1.5:1.1-event

I asked Peter to confirm the lsusb on his X220t in Ubuntu Natty.

Favux

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] 50-wacom-conf issues

[Favux ...]

Hi Ping,

That would make sense.  The E6 would then have the same name type as
the E3 and the others, i.e. "Wacom ISDv4 E6".  What kernel is that?  I
checked the Ubuntu 2.6.38 kernel source code.  In the static const
struct I see both the 0xE6 and 0x0064 identified as the new "ISD-V4"
along with a new Lenovo USB_Vendor define.

Favux

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] 50-wacom-conf issues

[Favux ...]

Ah.  Mystery solved.  Ubuntu did it.  Thanks Ping!

Favux

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] 50-wacom-conf issues

[Favux ...]

Hi Peter,

Right, since the Ubuntu kernel doesn't use wacom for the E6, for you
it would be:  grep ISD-V4 /var/log/messages

Favux

--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] conf: Add WALTOP back into MatchProduct

[Favux ...]

The WALTOP kernel driver patches are in the mainline lk now.

Dave
From 0e0c1dc96612a6a50d70e6d00709479a2cd4de80 Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Tue, 21 Jun 2011 21:14:49 -0500
Subject: [PATCH] conf:  Add WALTOP back into MatchProduct

Signed-off-by: David Foley 
---
 conf/50-wacom.conf |5 +
 1 files changed, 1 insertions(+), 4 deletions(-)

diff --git a/conf/50-wacom.conf b/conf/50-wacom.conf
index dc0bfc0..2c9ccb6 100644
--- a/conf/50-wacom.conf
+++ b/conf/50-wacom.conf
@@ -1,9 +1,6 @@
 Section "InputClass"
 	Identifier "Wacom class"
-# WALTOP needs a patched kernel driver, that isn't in mainline lk yet,
-# so for now just let it fall through and be picked up by evdev instead.
-#	MatchProduct "Wacom|WALTOP|WACOM"
-	MatchProduct "Wacom|WACOM|Hanwang"
+	MatchProduct "Wacom|WACOM|WALTOP|Hanwang"
 	MatchDevicePath "/dev/input/event*"
 	Driver "wacom"
 EndSection
-- 
1.7.1

--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Linuxwacom-devel] Add 3 new models: 6A, 6B, and 97

[Favux ...]

Some new models for inclusion.

Dave
From fd22dca9479759172bffc8155d590ad28e2a164b Mon Sep 17 00:00:00 2001
From: David Foley 
Date: Mon, 27 Jun 2011 20:43:58 -0500
Subject: [PATCH] Add 3 new models: 6A, 6B, and 97

Adds the new Bamboo1 small (6A) and medium (6B).  Adds a slate form factor tablet PC (97).

Tested-by: Alex Tervoort  for 6A
Signed-off-by: David Foley 
---
 src/wcmUSB.c|3 +++
 src/wcmValidateDevice.c |1 +
 2 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/src/wcmUSB.c b/src/wcmUSB.c
index 30f7c07..17551ad 100644
--- a/src/wcmUSB.c
+++ b/src/wcmUSB.c
@@ -242,6 +242,8 @@ static struct
 
 	{ WACOM_VENDOR_ID, 0x65, 10, 10, &usbBamboo }, /* Bamboo */
 	{ WACOM_VENDOR_ID, 0x69,  39842,  39842, &usbBamboo1}, /* Bamboo1 */
+	{ WACOM_VENDOR_ID, 0x6A, 10, 10, &usbBamboo1}, /* Bamboo1 4x6 */
+	{ WACOM_VENDOR_ID, 0x6B, 10, 10, &usbBamboo1}, /* Bamboo1 5x8 */
 
 	{ WACOM_VENDOR_ID, 0xB0, 20, 20, &usbIntuos3}, /* Intuos3 4x5 */
 	{ WACOM_VENDOR_ID, 0xB1, 20, 20, &usbIntuos3}, /* Intuos3 6x8 */
@@ -265,6 +267,7 @@ static struct
 
 	{ WACOM_VENDOR_ID, 0x90, 10, 10, &usbTabletPC   }, /* TabletPC 0x90 */
 	{ WACOM_VENDOR_ID, 0x93, 10, 10, &usbTabletPC   }, /* TabletPC 0x93 */
+	{ WACOM_VENDOR_ID, 0x97, 10, 10, &usbTabletPC   }, /* TabletPC 0x97 */
 	{ WACOM_VENDOR_ID, 0x9A, 10, 10, &usbTabletPC   }, /* TabletPC 0x9A */
 	{ WACOM_VENDOR_ID, 0x9F, 10, 10, &usbTabletPC   }, /* CapPlus  0x9F */
 	{ WACOM_VENDOR_ID, 0xE2, 10, 10, &usbTabletPC   }, /* TabletPC 0xE2 */
diff --git a/src/wcmValidateDevice.c b/src/wcmValidateDevice.c
index 456a113..2a6c0bf 100644
--- a/src/wcmValidateDevice.c
+++ b/src/wcmValidateDevice.c
@@ -261,6 +261,7 @@ int wcmDeviceTypeKeys(InputInfoPtr pInfo)
 		case 0x93: /* TPC with 1FGT */
 		case 0x9A: /* TPC with 1FGT */
 		case 0x90: /* TPC */
+		case 0x97: /* TPC */
 			TabletSetFeature(priv->common, WCM_TPC);
 			break;
 
-- 
1.7.1

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Serial rules file issues and fixes

[Favux ...]

Well both the new protocol 4 wacom_serial.ko and protocol 5
wacom_serial5.ko are using:

ACTION=="add|change", SUBSYSTEM=="pnp", ENV{PRODUCT}='13/3d/*',
ENV{NAME}=="Wacom protocol IV serial
tablet",SYMLINK+="input/wacom",ENV{ID_INPUT}="1",ENV{ID_INPUT_TABLET}="1"

So maybe that needs to be looked at.

What horrendous mistakes would I be making if I used?

SUBSYSTEM="tty", SUBSYSTEMS="pnp", ATTRS{id}=="PNP0501",
ENV{ID_MODEL}="Serial Wacom Tablet", ENV{ID_INPUT}="1",
ENV{ID_INPUT_TABLET}="1"

And by the way shouldn't

ENV{ID_MODEL}="Serial Wacom Tablet $attr{id}"

be

ENV{ID_MODEL}="Serial Wacom Tablet PC $attr{id}"

for WACf* and FUJ*?

Favux

--
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks & Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] Serial rules file issues and fixes

[Favux ...]

On Wed, Jul 20, 2011 at 12:16 AM, Peter Hutterer
 wrote:
>> What horrendous mistakes would I be making if I used?
>>
>> SUBSYSTEM="tty", SUBSYSTEMS="pnp", ATTRS{id}=="PNP0501",
>> ENV{ID_MODEL}="Serial Wacom Tablet", ENV{ID_INPUT}="1",
>> ENV{ID_INPUT_TABLET}="1"
>
> looks good to me though I would recommend using the $attr{id} in the
> ID_MODEL as well. Lennart?

OK, thanks.  I suppose I should show you what I'm working from:

udevadm info -a -p $(udevadm info -q path -n /dev/ttyS0)

  looking at device '/devices/pnp0/00:08/tty/ttyS0':
KERNEL=="ttyS0"
SUBSYSTEM=="tty"
DRIVER==""

  looking at parent device '/devices/pnp0/00:08':
KERNELS=="00:08"
SUBSYSTEMS=="pnp"
DRIVERS=="serial"
ATTRS{id}=="PNP0501"

  looking at parent device '/devices/pnp0':
KERNELS=="pnp0"
SUBSYSTEMS==""
DRIVERS==""

> Note that this rule removes the symlink to /dev/input/wacom that you have in
> the above rule. Fair decision, but should be intentional ;)

So maybe?

SUBSYSTEM="tty", SUBSYSTEMS="pnp", ATTRS{id}=="PNP0501",
ENV{ID_MODEL}="Serial Wacom Tablet $attr{id}", SYMLINK+="input/wacom",
ENV{ID_INPUT}="1", ENV{ID_INPUT_TABLET}="1"

I've been trying to get the following to work without any luck.

Section "InputClass"
Identifier "Wacom legacy serial class"
MatchPnPID "PNP0501"
Driver "wacom"
Option "ForceDevice" "Serial"
EndSection

Of course you wouldn't need the ForceDevice option using the wacom_serial.ko.

>> And by the way shouldn't
>>
>> ENV{ID_MODEL}="Serial Wacom Tablet $attr{id}"
>>
>> be
>>
>> ENV{ID_MODEL}="Serial Wacom Tablet PC $attr{id}"
>>
>> for WACf* and FUJ*?
>
> IMO no. Currently, all WACf and FUJ serial tablets are built into Tablet PCs
> but we don't know if that's the case in the future. They will remain Wacom
> tablets however (well, at least while handled by the ruleset).

Good point!  I withdraw the remark.

Favux

--
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks & Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] RFC: how to report a new value to XInput

[Favux ...]

Are we giving up on Eduard's sysfs solution?  It's been 3 months since
the last patch set and if there has been any activity I haven't seen
it.  It sure seemed like that approach had approval.

https://patchwork.kernel.org/patch/765792/

--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] RFC: how to report a new value to XInput

[Favux ...]

Not sure about that.

I just double checked on the thread where Vu Ngoc San (aka sanette)
and the rest were testing Eduard's patch set.  It apparently works for
the LEDs too.  To get his Intuos4 small, which just has the LEDs,
working theOGRE only had to change line 689 of wacom_sys.c from
replace >= INTUOS4 to >= INTUOS4S.

And jon.k's zsh & xdotool script shows the LEDs changing along with
the OLEDs, but I really didn't look into what he was doing:
http://www.youtube.com/watch?v=Yc7N8NwYgrE

Favux

--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] RFC: how to report a new value to XInput

[Favux ...]

Gottcha.  Thanks Ping.

--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH v2] make gesture distances be relative to hw maximums.

[Favux ...]

Sure Chris.  I've been following these with interest.

I assume you want me to test against the kernel and not input-wacom?
I'll have to check which wacom.ko I'm currently running on my 2.6.38
install.   I'm doing some other stuff so it might be while, but not
too long.

By the way anything about getting you one of the new BambooPTs so you
can figure out the new usb protocol?

Favux

--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-devel] [PATCH v2] make gesture distances be relative to hw maximums.

[Favux ...]

Hi Chris,

Testing the tag gesture3 with Natty's 2.6.38.11 kernel's wacom.ko I'd
say both scroll and zoom responsiveness are improved.

There's less lag, and while there is still a little pointer jumping
once you get the "feel" you can keep it where you want it while
zooming.

I do have a question about the scroll implementation.  Once the scroll
gesture is recognized the "momentum" carries it to the end of the
contents.  That doesn't seem to be natural to me.  There doesn't
appear to be a way to stop in a document or thread.  And the speed
means you had better be a very fast reader.

I'll test input-wacom-0.11.1 next.  Do you need the single finger
patches tested?

Favux

--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel