Re: [Linuxwacom-devel] [PATCH 2/4] Fix cursor jumping after zoom and scroll gestures when in Relative mode.
В Птн, 30/12/2011 в 13:30 -0600, Chris Bagwell пишет:
> The need for this makes sense (although I haven't tested it to much to
> see the jump).
>
> Although absolute devices don't have the same delta issue, I think its
> better to use same code flow in both cases. So I'd totally delete the
> original "if (wcmGestureMode) return;" and add the single if() inside
> wcmSendEvents().
Just tried to do what you have suggested. In that case we have broken
(in same way) Absolute mode for touch device. E.g. cursor jumps to wrong
position just after any gesture has been used, but for Absolute mode.
> I'd also limit the wcmGestureMode to wcmSendNonPadEvents() since PAD
> devices never have gestures.
Look reasonable. If no more comments on this patch, I'll repost a new
version with this only modification soon.
>
> Chris
>
> On Sat, Dec 24, 2011 at 12:18 AM, Alexey Osipov wrote:
> > When touchpad is in Relative mode of operation, we need allow driver
> > update internal old{x,y,z} variables to eliminate cursor jump after
> > gesture ended. That update performed in wcmSendEvents() function in
> > wcmCommon.c. So, when we in relative mode, allow call wcmSendEvents()
> > to update variables, but don't allow actual events sending to X server.
> >
> > Signed-off-by: Alexey Osipov
> > ---
> > src/wcmCommon.c | 13 -
> > 1 files changed, 8 insertions(+), 5 deletions(-)
> >
> > diff --git a/src/wcmCommon.c b/src/wcmCommon.c
> > index e85c6d8..d0bff63 100644
> > --- a/src/wcmCommon.c
> > +++ b/src/wcmCommon.c
> > @@ -743,10 +743,13 @@ void wcmSendEvents(InputInfoPtr pInfo, const
> > WacomDeviceState* ds)
> >valuators[4] = v4;
> >valuators[5] = v5;
> >
> > - if (type == PAD_ID)
> > - wcmSendPadEvents(pInfo, ds, 3, 3, &valuators[3]); /* pad
> > doesn't post x/y/z */
> > - else
> > - wcmSendNonPadEvents(pInfo, ds, 0, priv->naxes, valuators);
> > + /* don't move the cursor if in gesture mode */
> > + if (!(!is_absolute(pInfo) && priv->common->wcmGestureMode)) {
> > + if (type == PAD_ID)
> > + wcmSendPadEvents(pInfo, ds, 3, 3, &valuators[3]);
> > /* pad doesn't post x/y/z */
> > + else
> > + wcmSendNonPadEvents(pInfo, ds, 0, priv->naxes,
> > valuators);
> > + }
> >
> >priv->oldProximity = ds->proximity;
> >if (ds->proximity)
> > @@ -943,7 +946,7 @@ void wcmEvent(WacomCommonPtr common, unsigned int
> > channel,
> >wcmGestureFilter(priv, channel);
> >
> >/* don't move the cursor if in gesture mode */
> > - if (common->wcmGestureMode)
> > + if ((priv->flags & ABSOLUTE_FLAG) && (common->wcmGestureMode))
> >return;
> >
> >/* For touch, only first finger moves the cursor */
> > --
> > 1.7.0.4
> >
> >
> >
> >
> > --
> > Write once. Port to many.
> > Get the SDK and tools to simplify cross-platform app development. Create
> > new or port existing apps to sell to consumers worldwide. Explore the
> > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
> > http://p.sf.net/sfu/intel-appdev
> > ___
> > Linuxwacom-devel mailing list
> > Linuxwacom-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [PATCH 0/4] xf86-input-wacom touchpad improvements for Bamboo Pen Touch
Hi, Chris. Okay, I agree that I didn't done enough investigation on the case. Now I see that I reinvent "Device Accel Constant Deceleration" property. So, I remove my fourth patch from the patchset. Right now I'm not interested in providing "a good default value working in xf86-input-wacom", but maybe somewhen later I will. Thank you for pointing me to x.org wiki. Alexey. В Втр, 27/12/2011 в 15:05 -0600, Chris Bagwell пишет: > Hi Alexey, > > Welcome and thanks for sending in the patches. I should have time > soon to review them. The only one I can comment on after a quick scan > is #4. > > We do not want to adjust sensitivity this way. There are 4 X > properties already that own this function. You can see them in output > of "xinput list-props ". > > Device Accel Profile (239): 0 > Device Accel Constant Deceleration (240): 1.00 > Device Accel Adaptive Deceleration (241): 1.00 > Device Accel Velocity Scaling (242):10.00 > > If you want to know the gory details on these values, check out this wiki > page: > > http://www.x.org/wiki/Development/Documentation/PointerAcceleration > > I agree the default may not be ideal. If your interested in pursuing > further to get a good default value working in xf86-input-wacom, here > is some more info. > > If you use a synaptics-like touchpad with xf86-input-synaptics and if > it used those above default values then you would also not be happy. > There is code in xf86-input-synaptics to change away from that "Device > Accel Profile" of 0 to a custom profile and then set to some custom > values. > > Look around line #1022 of this xf86-input-synaptics to see how its > doing that. We could really stand to have similar logic in > xf86-input-wacom... but I've yet to find time to add this. > > http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/tree/src/synaptics.c > > Chris > > On Sat, Dec 24, 2011 at 12:18 AM, Alexey Osipov wrote: > > Hi. > > > > I've recently bought a wacom tablet mentioned in topic. > > > > With latest drivers from linux-wacom, it works reasonably good, except > > the touchpad. > > > > The problems I encountered: > > > > 1. Right click emulation with second finger touch sometimes produce more > > than one 'right click' within a short period of time. > > 2. After using scroll or zoom gestures, next cursor movement with > > touchpad happens from wrong place of the screen. That is - the cursor > > jumps to new position on the screen before start movement. > > 3. It's not possible to drag something with touchpad, i.e. press 'left > > button', move the cursor and then release 'left button'. Only single > > click is emulated. > > 4. In relative mode, cursor moves too fast for me and I don't find any > > sensitivity tuning in the driver. > > > > Being a programmer, I have solved all four problems. Here is a patchset > > based on current master git branch. I'll be happy if any of these > > patches will be included into mainline. > > > > If you want, I can do a video, showing using the tablet with and without > > my patches. > > > > Best regards, > > Alexey Osipov. > > > > > > -- > > Write once. Port to many. > > Get the SDK and tools to simplify cross-platform app development. Create > > new or port existing apps to sell to consumers worldwide. Explore the > > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > > http://p.sf.net/sfu/intel-appdev > > ___ > > Linuxwacom-devel mailing list > > Linuxwacom-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] Soft buttons for wacom digitazer on HP TC4200
On Fri, Dec 30, 2011 at 3:00 PM, Yaroslav Sheptykin wrote: > Hi Wacom Experts! > > I am a happy owner of an old HP TC4200 tablet. Since last two > years I have been using various versions of Ubuntu and none of > recent brought full functionality to my wacom digitizer out of > the ox (the last one got pretty close though). Different > versions led me to different hacks to get stuff to work the way > I want. One thing though always left outside of any > configuration reach - the SOFT BUTTONS. I have 3 soft buttons > available for the pen to press. They work great under windows > but show no presence of life under ubuntu. Through a long trial > of forum posts I came to a patch to your Xorg driver that was > ought to solve the issue. I compiled and installed that but no > success. Could you let me know if I am on the right path before > I dig deep into the depth of driver's source and your developer > documentation? > > Is it the resposibility of wacom-xorg driver to detect presses > on those buttons? > > I attached some files and here is uname -a output > > Linux prime 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:34:47 > UTC 2011 i686 i686 i386 GNU/Linux > > anything else? > > Thanks, I'm guessing that your have a ISDV4 interface. The following thread is someone that added support for non-standard buttons on tablet itself to ISDV4 logic. http://www.mail-archive.com/linuxwacom-devel@lists.sourceforge.net/msg03370.html I never saw the code committed to xf86-input-wacom or linux kernel. Chris -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] linuxwacom project - asustek eeenote tablet
On Fri, Dec 30, 2011 at 2:45 PM, Chris Bagwell wrote: > On Fri, Dec 30, 2011 at 2:21 PM, Mike Rolland wrote: >> Le vendredi 30 décembre 2011 à 11:37 -0600, Chris Bagwell a écrit : >> >>> * Run "dmesg | grep ASUSTek" and look for line telling if kernel >>> driver has been installed for this device. >> >> [root@hpm mike]# dmesg | grep ASUSTek >> usb 2-1.2: Manufacturer: ASUSTek Computer, Inc. >> input: ASUSTek Computer, Inc. Eee Note Digitizer as >> /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input14 >> generic-usb 0003:0B05:179F.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse >> [ASUSTek Computer, Inc. Eee Note Digitizer] on usb-:00:1d.0-1.2/input0 > > OK, this is the part I want to concentrate on. That USB HID v1.10 > Mouse part means its probably being reported to userland as a strange > mouse+pen combo device. Its related to the HID report for digitizer > declaring a mouse (required by Microsoft for tabletPC's I think even > if its not really used). > > To better see what kernel is doing, you'll need to install the > "evtest" app from your distro's repo. Run it as root and from a > console (not from X) or it will hide some stuff from you. > > evtest /dev/input/eventtX <--- The value for X is usually found from > trail and error. > > Please send what this displays. You can pipe to a file as well > (evtest /dev/input/eventX > log). > >> >>> I googled for this USB ID and got one result where it said its being >>> detected as a generic HID Mouse. This would not be a good thing and >>> all your work in xf86-input-wacom or xf86-input-evdev will be in vain >>> until kernel side issue is resolved. >> >> Not really sure about that. >> Often the problem comes only from XF86 driver, but like I told to Favux, I >> will have a look to wacom dev kernel libs. The first time I made my homebrew >> with my WALTOP tablet, I remember I change something in kernel driver. So... > > In last year, I think problem areas have moved. xf86-input-wacom and > xf86-input-evdev have become quite stable for new > digitizers/tabletPC's and touchscreens without modifications. The > issues are almost always in kernel now for new hardware. > > I see people go to great lengths though to hack up xf86-input-* > instead of fixing the real kernel side issue and try to ignore that > invalid mouse information. > > When we see the mouse+touchscreen issue in recent times, the cure is > to get the hid-multitouch driver to control the touchscreen. > > In your case, its a mouse+pen so I'm not sure what driver its supposed > to be routed to. If the Asus web page that Favux is to be trusted, > its a Wacom digitizer and so maybe it should be handled by wacom > driver. I have seen Wacom commonly use 0x81 as Endpoint address for > PEN's so thats a good sign. > > I'd try the hint given by Favux and update the file wacom_wac.c from > input-wacom package to understand Eee product ID's. If the vendor ID is not Wacom or Lenovo, you most likely need to update hid-core.c to add the new vendorID to the black/ignore list. Otherwise, the HID/mouse driver will always pick up the device before we (wacom.ko) even get to it. Ping -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [PATCH 1/4] Extra right clicks removed.
On Fri, Dec 30, 2011 at 11:21 AM, Chris Bagwell wrote: > I had wanted to change 2nd-finger tap gesture to a 2 finger tap (the > difference being that in former you leave 1st finger touching and in > later you tap both fingers and release both fingers). > > But I may never get around to that since gestures are moving outside X > soon enough. > > So in mean time, this patch looks good to remove chance of second > unwanted click. > > Reviewed-by: Chris Bagwell Acked-by: Ping Cheng Thank you, Alexey and Chris, for your support. I wish everyone a Happy New Year! Ping > On Sat, Dec 24, 2011 at 12:18 AM, Alexey Osipov wrote: >> As right click performed with second finger, then we only interested >> in second finger touch when trying to match 'right click' gesture. >> >> Signed-off-by: Alexey Osipov >> --- >> src/wcmTouchFilter.c | 2 +- >> 1 files changed, 1 insertions(+), 1 deletions(-) >> >> diff --git a/src/wcmTouchFilter.c b/src/wcmTouchFilter.c >> index 7fa2975..047490b 100644 >> --- a/src/wcmTouchFilter.c >> +++ b/src/wcmTouchFilter.c >> @@ -321,7 +321,7 @@ void wcmGestureFilter(WacomDevicePtr priv, int channel) >> goto ret; >> } >> >> - if (!(common->wcmGestureMode & (GESTURE_SCROLL_MODE | >> GESTURE_ZOOM_MODE))) >> + if (!(common->wcmGestureMode & (GESTURE_SCROLL_MODE | >> GESTURE_ZOOM_MODE)) && channel) >> wcmFingerTapToClick(priv); >> >> /* Change mode happens only when both fingers are out */ >> -- >> 1.7.0.4 >> -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] linuxwacom project - asustek eeenote tablet
On Fri, Dec 30, 2011 at 2:21 PM, Mike Rolland wrote: > Le vendredi 30 décembre 2011 à 11:37 -0600, Chris Bagwell a écrit : > >> * Run "dmesg | grep ASUSTek" and look for line telling if kernel >> driver has been installed for this device. > > [root@hpm mike]# dmesg | grep ASUSTek > usb 2-1.2: Manufacturer: ASUSTek Computer, Inc. > input: ASUSTek Computer, Inc. Eee Note Digitizer as > /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input14 > generic-usb 0003:0B05:179F.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse > [ASUSTek Computer, Inc. Eee Note Digitizer] on usb-:00:1d.0-1.2/input0 OK, this is the part I want to concentrate on. That USB HID v1.10 Mouse part means its probably being reported to userland as a strange mouse+pen combo device. Its related to the HID report for digitizer declaring a mouse (required by Microsoft for tabletPC's I think even if its not really used). To better see what kernel is doing, you'll need to install the "evtest" app from your distro's repo. Run it as root and from a console (not from X) or it will hide some stuff from you. evtest /dev/input/eventtX <--- The value for X is usually found from trail and error. Please send what this displays. You can pipe to a file as well (evtest /dev/input/eventX > log). > >> I googled for this USB ID and got one result where it said its being >> detected as a generic HID Mouse. This would not be a good thing and >> all your work in xf86-input-wacom or xf86-input-evdev will be in vain >> until kernel side issue is resolved. > > Not really sure about that. > Often the problem comes only from XF86 driver, but like I told to Favux, I > will have a look to wacom dev kernel libs. The first time I made my homebrew > with my WALTOP tablet, I remember I change something in kernel driver. So... In last year, I think problem areas have moved. xf86-input-wacom and xf86-input-evdev have become quite stable for new digitizers/tabletPC's and touchscreens without modifications. The issues are almost always in kernel now for new hardware. I see people go to great lengths though to hack up xf86-input-* instead of fixing the real kernel side issue and try to ignore that invalid mouse information. When we see the mouse+touchscreen issue in recent times, the cure is to get the hid-multitouch driver to control the touchscreen. In your case, its a mouse+pen so I'm not sure what driver its supposed to be routed to. If the Asus web page that Favux is to be trusted, its a Wacom digitizer and so maybe it should be handled by wacom driver. I have seen Wacom commonly use 0x81 as Endpoint address for PEN's so thats a good sign. I'd try the hint given by Favux and update the file wacom_wac.c from input-wacom package to understand Eee product ID's. Chris -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] linuxwacom project - asustek eeenote tablet
Hi Mike,
Well in wacom_wac.c there is also:
#define USB_DEVICE_LENOVO(prod) \
USB_DEVICE(USB_VENDOR_ID_LENOVO, prod), \
.driver_info = (kernel_ulong_t)&wacom_features_##prod
below the wacom one at about line #1522. Then there are the
appropriate entries for the Lenovo product using its Product ID.
That's what I was thinking of. So at about line #1509:
static const struct wacom_features wacom_features_0x6004 =
{ "ISD-V4", WACOM_PKGLEN_GRAPHIRE, 12800, 8000, 255,
0, TABLETPC, WACOM_INTUOS_RES, WACOM_INTUOS_RES };
And again at about line #1615:
{ USB_DEVICE_LENOVO(0x6004) },
Unfortunately your lsusb seems truncated so we don't seem to have your
max X and Y dimensions. Also it bothers me the packet length seems to
be 9. I think tablet PCs are 8. That said you'd be much better off
following Chris' guidance.
Assuming you have your kernel's source code and of course using your
kernel's version number:
cd linux-2.6.38/drivers/input/tablet
make -C/lib/modules/`uname -r`/build M=`pwd` modules
Then copy the newly compiled wacom.ko into place.
sudo cp wacom.ko /lib/modules/`uname -r`/kernel/drivers/input/tablet/
Favux
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] Soft buttons for wacom digitazer on HP TC4200
Hi Wacom Experts! I am a happy owner of an old HP TC4200 tablet. Since last two years I have been using various versions of Ubuntu and none of recent brought full functionality to my wacom digitizer out of the ox (the last one got pretty close though). Different versions led me to different hacks to get stuff to work the way I want. One thing though always left outside of any configuration reach - the SOFT BUTTONS. I have 3 soft buttons available for the pen to press. They work great under windows but show no presence of life under ubuntu. Through a long trial of forum posts I came to a patch to your Xorg driver that was ought to solve the issue. I compiled and installed that but no success. Could you let me know if I am on the right path before I dig deep into the depth of driver's source and your developer documentation? Is it the resposibility of wacom-xorg driver to detect presses on those buttons? I attached some files and here is uname -a output Linux prime 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:34:47 UTC 2011 i686 i686 i386 GNU/Linux anything else? Thanks, Happy New Year, Yarik Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice3.00 iManufacturer 3 Linux 3.0.0-14-generic ehci_hcd iProduct2 EHCI Host Controller iSerial 1 :00:1d.7 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Hub Descriptor: bLength 11 bDescriptorType 41 nNbrPorts 8 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable0x00 0x00 PortPwrCtrlMask0xff 0xff Hub Port Status: Port 1: .0100 power Port 2: .0100 power Port 3: .0100 power Port 4: .0100 power Port 5: .0100 power Port 6: .0100 power Port 7: .0100 power Port 8: .0100 power Device Status: 0x0003 Self Powered Remote Wakeup Enabled Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice3.00 iManufacturer 3 Linux 3.0.0-14-generic uhci_hcd iProduct2 UHCI Host Controller iSerial 1 :00:1d.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1
Re: [Linuxwacom-devel] linuxwacom project - asustek eeenote tablet
Effectively, wacom.h has a LENOVO line: #define USB_VENDOR_ID_LENOVO 0x17ef So I add ASUSTEK. I didn't see something else relevant in other kernel wacom libs (there is probably some). My only problem is that I absolutely don't remember how to compile a single driver in kernel tree. If someone could help. (I know, real y noob...) M. Le samedi 31 décembre 2011 à 00:21 +0400, Mike Rolland a écrit : > Le vendredi 30 décembre 2011 à 11:37 -0600, Chris Bagwell a écrit : > > > On Fri, Dec 30, 2011 at 10:17 AM, Favux ... wrote: > > > Hi Mike, > > > > > > Is this the Eee Note EA800? An e-ink e-book reader with an active > > > stylus with 256 pressure levels and no touch? > > > http://www.asus.com/Eee/Eee_Note/Eee_Note_EA800/ > > > > > > If so it apparently is a Wacom digitizer. But there is no Wacom > > > digitizer in the lsusb output? Just the "Bus 002 Device 012: ID > > > 0b05:179f ASUSTek Computer, Inc."? > > > > > > To get it working the first thing you would probably need to do is add > > > it to the wacom.ko. Using input-wacom would probably be more > > > convenient than working with your kernel. We'll need to see what the > > > experts say but something along the lines of adding the ASUSTek Vendor > > > ID like the Lenovo ID was added to, for example, wacom.h and > > > wacom_wac.c. Although the apparent digitizer is given an Asus product > > > ID, which doesn't follow Wacom conventions, I wouldn't be surprised if > > > it is in fact a Wacom (tabletPC?) digitizer already entered. > > > > > > What is your Distribution and release? Kernel, Xorg, and > > > xf86-input-wacom versions? > > > > > > Could you attach the output of: > > >lsusb > > > for the digitizer to your next post? > > > > > > Favux > > > > > > > I have two additional requests. > > > > * Please run "lsusb -vvv" as root. This is only way to get the full > > HID report. I believe this does not always work if a kernel input > > driver has latched onto the device. > > Already done. > > > * Run "dmesg | grep ASUSTek" and look for line telling if kernel > > driver has been installed for this device. > > > > [root@hpm mike]# dmesg | grep ASUSTek > usb 2-1.2: Manufacturer: ASUSTek Computer, Inc. > input: ASUSTek Computer, Inc. Eee Note Digitizer > as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input14 > generic-usb 0003:0B05:179F.0002: input,hiddev0,hidraw1: USB HID v1.10 > Mouse [ASUSTek Computer, Inc. Eee Note Digitizer] on > usb-:00:1d.0-1.2/input0 > > > > I googled for this USB ID and got one result where it said its being > > detected as a generic HID Mouse. This would not be a good thing and > > all your work in xf86-input-wacom or xf86-input-evdev will be in vain > > until kernel side issue is resolved. > > > > Not really sure about that. > Often the problem comes only from XF86 driver, but like I told to > Favux, I will have a look to wacom dev kernel libs. The first time I > made my homebrew with my WALTOP tablet, I remember I change something > in kernel driver. So... > > > Chris > > > > Chris > > -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] linuxwacom project - asustek eeenote tablet
Le vendredi 30 décembre 2011 à 11:37 -0600, Chris Bagwell a écrit : > On Fri, Dec 30, 2011 at 10:17 AM, Favux ... wrote: > > Hi Mike, > > > > Is this the Eee Note EA800? An e-ink e-book reader with an active > > stylus with 256 pressure levels and no touch? > > http://www.asus.com/Eee/Eee_Note/Eee_Note_EA800/ > > > > If so it apparently is a Wacom digitizer. But there is no Wacom > > digitizer in the lsusb output? Just the "Bus 002 Device 012: ID > > 0b05:179f ASUSTek Computer, Inc."? > > > > To get it working the first thing you would probably need to do is add > > it to the wacom.ko. Using input-wacom would probably be more > > convenient than working with your kernel. We'll need to see what the > > experts say but something along the lines of adding the ASUSTek Vendor > > ID like the Lenovo ID was added to, for example, wacom.h and > > wacom_wac.c. Although the apparent digitizer is given an Asus product > > ID, which doesn't follow Wacom conventions, I wouldn't be surprised if > > it is in fact a Wacom (tabletPC?) digitizer already entered. > > > > What is your Distribution and release? Kernel, Xorg, and > > xf86-input-wacom versions? > > > > Could you attach the output of: > >lsusb > > for the digitizer to your next post? > > > > Favux > > > > I have two additional requests. > > * Please run "lsusb -vvv" as root. This is only way to get the full > HID report. I believe this does not always work if a kernel input > driver has latched onto the device. Already done. > * Run "dmesg | grep ASUSTek" and look for line telling if kernel > driver has been installed for this device. > [root@hpm mike]# dmesg | grep ASUSTek usb 2-1.2: Manufacturer: ASUSTek Computer, Inc. input: ASUSTek Computer, Inc. Eee Note Digitizer as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input14 generic-usb 0003:0B05:179F.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [ASUSTek Computer, Inc. Eee Note Digitizer] on usb-:00:1d.0-1.2/input0 > I googled for this USB ID and got one result where it said its being > detected as a generic HID Mouse. This would not be a good thing and > all your work in xf86-input-wacom or xf86-input-evdev will be in vain > until kernel side issue is resolved. > Not really sure about that. Often the problem comes only from XF86 driver, but like I told to Favux, I will have a look to wacom dev kernel libs. The first time I made my homebrew with my WALTOP tablet, I remember I change something in kernel driver. So... > Chris > > Chris -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] linuxwacom project - asustek eeenote tablet
Le vendredi 30 décembre 2011 à 10:17 -0600, Favux ... a écrit : > Hi Mike, > > Is this the Eee Note EA800? An e-ink e-book reader with an active > stylus with 256 pressure levels and no touch? > http://www.asus.com/Eee/Eee_Note/Eee_Note_EA800/ > > If so it apparently is a Wacom digitizer. But there is no Wacom > digitizer in the lsusb output? Just the "Bus 002 Device 012: ID > 0b05:179f ASUSTek Computer, Inc."? You are right. lsusb doesn't report ditizer as wacom, but it's a quite normal, when you plug a WALTOP graphic tablet it doesn't report it as a wacom tablet. so, lussub says: iProduct2 Eee Note Digitizer > > To get it working the first thing you would probably need to do is add > it to the wacom.ko. Using input-wacom would probably be more > convenient than working with your kernel. We'll need to see what the > experts say but something along the lines of adding the ASUSTek Vendor > ID like the Lenovo ID was added to, for example, wacom.h and > wacom_wac.c. Although the apparent digitizer is given an Asus product > ID, which doesn't follow Wacom conventions, I wouldn't be surprised if > it is in fact a Wacom (tabletPC?) digitizer already entered. ASUS digitizer is some kind of LENOVO one. I don't really think Wacom will build one special device for each manufacturers. Like for olds tablePC there was only one kind of device for many manufacturer but it was still needed to invoke them separately in the xf86 driver. Nevertheless the wacom.ko could be a way to solve partly the issue. The trouble with EEE Note is make it understandable by the driver as a pen or better, a stylus. For now this is not the case. > > What is your Distribution and release? Kernel, Xorg, and > xf86-input-wacom versions? > mageia 64 (mandriva fork) X.Org X Server 1.10.1 git repos driver compiled 3.1.1 kernel ( I have 3.2.0-rc2 too) > Could you attach the output of: > lsusb 4 'v', wow, usually are enought, but if you wish > for the digitizer to your next post? > > Favux As you can see : only pen is report (i haven't catsh this ) iInterface 4 pen report data [root@hpm mike]# lsusb - -d 0b05:179f Bus 002 Device 008: ID 0b05:179f ASUSTek Computer, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize016 idVendor 0x0b05 ASUSTek Computer, Inc. idProduct 0x179f bcdDevice1.29 iManufacturer 1 ASUSTek Computer, Inc. iProduct2 Eee Note Digitizer iSerial 3 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 pen report data bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 2 Mouse iInterface 4 pen report data HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode 33 US bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 201 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0009 1x 9 bytes bInterval 4 Device Status: 0x0001 Self Powered -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [PATCH 3/4] 'Left mouse button' dragging support.
I'm glad someone decided to add this! I wanted to but been to busy.
Similar to Peter's past comments on the file wcmTouchFilter.c, this
code is almost obsolete before being published and so I'm not
reviewing very strict.
Comments below.
On Sat, Dec 24, 2011 at 12:18 AM, Alexey Osipov wrote:
> First, we define two new GESTURE_ modes:
> - GESTURE_PREDRAG_MODE - when first tap happen and we wait for second touch.
> - GESTURE_DRAG_MODE - when actual drag happening (left button pressed).
>
> Second, we define tap timeout function wcmSingleFingerTapTimer(), which
> simulate single click if no drag operation started within timeout.
>
> Third, we make an exception for GESTURE_DRAG_MODE in wcmCommon.c, because
> we actually want cursor movements while dragging.
>
> Now, to do a single tap you just tap (touch and untouch). Actual click
> happens after TapTime period.
> To drag something you make a tap (touch and untouch) and then quickly
> (in TapTime period) touch device again. Then drag.
>
> Signed-off-by: Alexey Osipov
> ---
> src/common.mk | 3 +-
> src/wcmCommon.c | 8 +++---
> src/wcmTouchFilter.c | 54 -
> src/wcmTouchFilter.h | 38 +++
> src/xf86Wacom.h | 1 -
> 5 files changed, 88 insertions(+), 16 deletions(-)
> create mode 100644 src/wcmTouchFilter.h
>
> diff --git a/src/common.mk b/src/common.mk
> index fae8d9f..7f1eadd 100644
> --- a/src/common.mk
> +++ b/src/common.mk
> @@ -12,4 +12,5 @@ DRIVER_SOURCES= \
> $(top_srcdir)/src/wcmUSB.c \
> $(top_srcdir)/src/wcmXCommand.c \
> $(top_srcdir)/src/wcmValidateDevice.c \
> - $(top_srcdir)/src/wcmTouchFilter.c
> + $(top_srcdir)/src/wcmTouchFilter.c \
> + $(top_srcdir)/src/wcmTouchFilter.h
> diff --git a/src/wcmCommon.c b/src/wcmCommon.c
> index d0bff63..0cab803 100644
> --- a/src/wcmCommon.c
> +++ b/src/wcmCommon.c
> @@ -24,6 +24,7 @@
> #include "xf86Wacom.h"
> #include "Xwacom.h"
> #include "wcmFilter.h"
> +#include "wcmTouchFilter.h"
> #include
> #include
>
> @@ -743,8 +744,8 @@ void wcmSendEvents(InputInfoPtr pInfo, const
> WacomDeviceState* ds)
> valuators[4] = v4;
> valuators[5] = v5;
>
> - /* don't move the cursor if in gesture mode */
> - if (!(!is_absolute(pInfo) && priv->common->wcmGestureMode)) {
> + /* don't move the cursor if in gesture mode (except drag mode) */
> + if (!(!is_absolute(pInfo) && priv->common->wcmGestureMode &
> ~GESTURE_DRAG_MODE)) {
> if (type == PAD_ID)
> wcmSendPadEvents(pInfo, ds, 3, 3, &valuators[3]); /*
> pad doesn't post x/y/z */
> else
> @@ -945,8 +946,7 @@ void wcmEvent(WacomCommonPtr common, unsigned int channel,
> if ((ds.device_type == TOUCH_ID) && common->wcmTouch)
> wcmGestureFilter(priv, channel);
>
> - /* don't move the cursor if in gesture mode */
> - if ((priv->flags & ABSOLUTE_FLAG) && (common->wcmGestureMode))
> + if ((priv->flags & ABSOLUTE_FLAG) && (common->wcmGestureMode &
> ~GESTURE_DRAG_MODE))
> return;
These would need to align with comment on previous patch.
And more a personal opinion, I think the wcmGestureMode values are
meant to be more internal to the touch filter engine and shouldn't be
exposed to wcmCommon.c. I'd prefer if you exported a new function
with name like wcmTouchNeedsFilter() that returns yes/no answer and
then you add exact values to check inside wcmTouchFilter.c.
>
> /* For touch, only first finger moves the cursor */
> diff --git a/src/wcmTouchFilter.c b/src/wcmTouchFilter.c
> index 047490b..c1a6071 100644
> --- a/src/wcmTouchFilter.c
> +++ b/src/wcmTouchFilter.c
> @@ -1,5 +1,6 @@
> /*
> * Copyright 2009 - 2010 by Ping Cheng, Wacom.
> + * Copyright 2011 by Alexey Osipov.
> *
> * This program is free software; you can redistribute it and/or
> * modify it under the terms of the GNU General Public License
> @@ -21,6 +22,7 @@
> #endif
>
> #include "xf86Wacom.h"
> +#include "wcmTouchFilter.h"
> #include
>
> /* Defines for 2FC Gesture */
> @@ -28,12 +30,6 @@
> #define WACOM_VERT_ALLOWED 2
> #define WACOM_GESTURE_LAG_TIME 10
>
> -#define GESTURE_NONE_MODE 0
> -#define GESTURE_TAP_MODE 1
> -#define GESTURE_SCROLL_MODE 2
> -#define GESTURE_ZOOM_MODE 4
> -#define GESTURE_LAG_MODE 8
> -
> #define WCM_SCROLL_UP 5 /* vertical up */
> #define WCM_SCROLL_DOWN 4 /* vertical down */
> #define WCM_SCROLL_LEFT 6 /* horizontal left */
> @@ -147,6 +143,23 @@ static void wcmFingerTapToClick(WacomDevicePtr priv)
> }
> }
>
> +static CARD32 wcmSingleFingerTapTimer(OsTimerPtr timer, CARD32 time, pointer
> arg)
> +{
> + WacomDevicePtr priv = (WacomDevicePtr)arg;
> + WacomCommonPtr common = priv->common;
> +
> +
Re: [Linuxwacom-devel] [PATCH 2/4] Fix cursor jumping after zoom and scroll gestures when in Relative mode.
The need for this makes sense (although I haven't tested it to much to
see the jump).
Although absolute devices don't have the same delta issue, I think its
better to use same code flow in both cases. So I'd totally delete the
original "if (wcmGestureMode) return;" and add the single if() inside
wcmSendEvents().
I'd also limit the wcmGestureMode to wcmSendNonPadEvents() since PAD
devices never have gestures.
Chris
On Sat, Dec 24, 2011 at 12:18 AM, Alexey Osipov wrote:
> When touchpad is in Relative mode of operation, we need allow driver
> update internal old{x,y,z} variables to eliminate cursor jump after
> gesture ended. That update performed in wcmSendEvents() function in
> wcmCommon.c. So, when we in relative mode, allow call wcmSendEvents()
> to update variables, but don't allow actual events sending to X server.
>
> Signed-off-by: Alexey Osipov
> ---
> src/wcmCommon.c | 13 -
> 1 files changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/src/wcmCommon.c b/src/wcmCommon.c
> index e85c6d8..d0bff63 100644
> --- a/src/wcmCommon.c
> +++ b/src/wcmCommon.c
> @@ -743,10 +743,13 @@ void wcmSendEvents(InputInfoPtr pInfo, const
> WacomDeviceState* ds)
> valuators[4] = v4;
> valuators[5] = v5;
>
> - if (type == PAD_ID)
> - wcmSendPadEvents(pInfo, ds, 3, 3, &valuators[3]); /* pad
> doesn't post x/y/z */
> - else
> - wcmSendNonPadEvents(pInfo, ds, 0, priv->naxes, valuators);
> + /* don't move the cursor if in gesture mode */
> + if (!(!is_absolute(pInfo) && priv->common->wcmGestureMode)) {
> + if (type == PAD_ID)
> + wcmSendPadEvents(pInfo, ds, 3, 3, &valuators[3]); /*
> pad doesn't post x/y/z */
> + else
> + wcmSendNonPadEvents(pInfo, ds, 0, priv->naxes,
> valuators);
> + }
>
> priv->oldProximity = ds->proximity;
> if (ds->proximity)
> @@ -943,7 +946,7 @@ void wcmEvent(WacomCommonPtr common, unsigned int channel,
> wcmGestureFilter(priv, channel);
>
> /* don't move the cursor if in gesture mode */
> - if (common->wcmGestureMode)
> + if ((priv->flags & ABSOLUTE_FLAG) && (common->wcmGestureMode))
> return;
>
> /* For touch, only first finger moves the cursor */
> --
> 1.7.0.4
>
>
>
>
> --
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. Create
> new or port existing apps to sell to consumers worldwide. Explore the
> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
> http://p.sf.net/sfu/intel-appdev
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [PATCH 1/4] Extra right clicks removed.
I had wanted to change 2nd-finger tap gesture to a 2 finger tap (the difference being that in former you leave 1st finger touching and in later you tap both fingers and release both fingers). But I may never get around to that since gestures are moving outside X soon enough. So in mean time, this patch looks good to remove chance of second unwanted click. Reviewed-by: Chris Bagwell Chris On Sat, Dec 24, 2011 at 12:18 AM, Alexey Osipov wrote: > As right click performed with second finger, then we only interested > in second finger touch when trying to match 'right click' gesture. > > Signed-off-by: Alexey Osipov > --- > src/wcmTouchFilter.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/src/wcmTouchFilter.c b/src/wcmTouchFilter.c > index 7fa2975..047490b 100644 > --- a/src/wcmTouchFilter.c > +++ b/src/wcmTouchFilter.c > @@ -321,7 +321,7 @@ void wcmGestureFilter(WacomDevicePtr priv, int channel) > goto ret; > } > > - if (!(common->wcmGestureMode & (GESTURE_SCROLL_MODE | > GESTURE_ZOOM_MODE))) > + if (!(common->wcmGestureMode & (GESTURE_SCROLL_MODE | > GESTURE_ZOOM_MODE)) && channel) > wcmFingerTapToClick(priv); > > /* Change mode happens only when both fingers are out */ > -- > 1.7.0.4 > > > > > -- > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > ___ > Linuxwacom-devel mailing list > Linuxwacom-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] linuxwacom project - asustek eeenote tablet
On Fri, Dec 30, 2011 at 10:17 AM, Favux ... wrote: > Hi Mike, > > Is this the Eee Note EA800? An e-ink e-book reader with an active > stylus with 256 pressure levels and no touch? > http://www.asus.com/Eee/Eee_Note/Eee_Note_EA800/ > > If so it apparently is a Wacom digitizer. But there is no Wacom > digitizer in the lsusb output? Just the "Bus 002 Device 012: ID > 0b05:179f ASUSTek Computer, Inc."? > > To get it working the first thing you would probably need to do is add > it to the wacom.ko. Using input-wacom would probably be more > convenient than working with your kernel. We'll need to see what the > experts say but something along the lines of adding the ASUSTek Vendor > ID like the Lenovo ID was added to, for example, wacom.h and > wacom_wac.c. Although the apparent digitizer is given an Asus product > ID, which doesn't follow Wacom conventions, I wouldn't be surprised if > it is in fact a Wacom (tabletPC?) digitizer already entered. > > What is your Distribution and release? Kernel, Xorg, and > xf86-input-wacom versions? > > Could you attach the output of: > lsusb > for the digitizer to your next post? > > Favux > I have two additional requests. * Please run "lsusb -vvv" as root. This is only way to get the full HID report. I believe this does not always work if a kernel input driver has latched onto the device. * Run "dmesg | grep ASUSTek" and look for line telling if kernel driver has been installed for this device. I googled for this USB ID and got one result where it said its being detected as a generic HID Mouse. This would not be a good thing and all your work in xf86-input-wacom or xf86-input-evdev will be in vain until kernel side issue is resolved. Chris Chris -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] linuxwacom project - asustek eeenote tablet
Hi Mike, Is this the Eee Note EA800? An e-ink e-book reader with an active stylus with 256 pressure levels and no touch? http://www.asus.com/Eee/Eee_Note/Eee_Note_EA800/ If so it apparently is a Wacom digitizer. But there is no Wacom digitizer in the lsusb output? Just the "Bus 002 Device 012: ID 0b05:179f ASUSTek Computer, Inc."? To get it working the first thing you would probably need to do is add it to the wacom.ko. Using input-wacom would probably be more convenient than working with your kernel. We'll need to see what the experts say but something along the lines of adding the ASUSTek Vendor ID like the Lenovo ID was added to, for example, wacom.h and wacom_wac.c. Although the apparent digitizer is given an Asus product ID, which doesn't follow Wacom conventions, I wouldn't be surprised if it is in fact a Wacom (tabletPC?) digitizer already entered. What is your Distribution and release? Kernel, Xorg, and xf86-input-wacom versions? Could you attach the output of: lsusb for the digitizer to your next post? Favux -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] linuxwacom project - asustek eeenote tablet
Le jeudi 29 décembre 2011 à 17:00 +, Ping Cheng a écrit : > Hi Mike, > > > > Yes, I am interested to help. And I am grateful that you have and are > interested in supporting linuxwacom project. You are the people that I > am still working on the project ;). Nice. I already done this kind of action with V4L for a DVB-T. Great experience. Diff atteched in files or at the end of threads. > > > > Please post your changes to linuxwacom-devel@lists.sourceforge.net and > cc me (pingli...@gmail.com). We’ll move forward from there. > Ok, change are in ASUS_diff.patch (I use Patcher for diff, I'm too noob for something else). What's work? double clic on pen touch button1, nothing else. Driver declare device as stylus but report this is not a stylus device. evdev says this is a touch pad: >> [ 8049.553] (II) XINPUT: Adding extended input device "ASUSTek Computer, Inc. Eee Note Digitizer" (type: TOUCHPAD) I tried many xorg config type (stylus, pen, pad, touch) and only "touch" was accepted: >> [ 1853.426] (EE) ASUSTek Computer, Inc. Eee Note Digitizer: Invalid type 'stylus' for this device. All my xorg.con.d are made like this: Section "InputClass" Identifier "Wacom class" MatchProduct "ASUSTek|Digitizer" MatchDevicePath "/dev/input/event*" Driver "wacom" #Section "InputDevice" Option "Type" "stylus" # Option "Type" "touch" # Option "Type" "pad" # Option "Type" "pen" # Option "Type" "mouse" etc... for info: lsusb reports: Bus 002 Device 012: ID 0b05:179f ASUSTek Computer, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize016 idVendor 0x0b05 ASUSTek Computer, Inc. idProduct 0x179f bcdDevice1.29 iManufacturer 1 ASUSTek Computer, Inc. iProduct2 Eee Note Digitizer iSerial 3 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 pen report data bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 2 Mouse iInterface 4 pen report data HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode 33 US bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 201 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0009 1x 9 bytes bInterval 4 Device Status: 0x0001 Self Powered > > > I do have a question for you here though. What problem related to > “have to change Graphire4 associated tablet model to Intuos4 to get > mine work”? We’d love to make the driver work better, you know ;). > I had to remember first (more than one year ago) and test again with different tablet mode. Finally issue was the button. Graphire4 model doesn't recognize secondary button. Intuos3/4 get it but think it's the "enter" key command. Didn't get success,anyway, to configure it as real secondary button (2 and 3 recognize as the same button). > > > Best regards, > > > > Ping > Hope you get what you need. The problem is that driver (evdev,wacom) blocks on TOUCHPAD reported status. Best regards. Mike. > > > From: Mike Rolland [mailto:none...@gmail.com] > Sent: Thursday, December 29, 2011 1:05 AM > To: Ping Cheng > Subject: linuxwacom project - asustek eeenote debug help > > > > > Hi, > I've recently acquire an eeenote EA800 tablet, I'm no a coder or other > linux hacker but I'm an advanced user who can understand how it's > works. > I'd previously (long time ago) change some lines in xf86WacomDefs.h, > xf86Wacom.c, wcmUSB.c to get my WALTOP tablet works, project has now > add all WALTOP tablets, even if I have to change Graphire4 associated > tablet model to Intuos4 to get mine work. > I was wondering if you, or other project members, were interested to > help me to add eeenote digitizer to the correct tablet model. > I have already add some line in xf86
