I'd like to summarize where we are with Eee Note's for mailing list archive.
Mike was able to log some USB packets when using tablet under Windows
and sent them to me directly. This showed that the device works
almost exactly like a Bamboo tablet. We were assuming it was more
TabletPC and thats why we were not having success.
Packets started flowing correctly after adding the USB PID to
hid-core's blacklist and then using this in Wacom driver:
+static const struct wacom_features wacom_features_0x179F =
+ { "EeeNote ASUSTek Digitizer", WACOM_PKGLEN_BBFUN, 16480, 12410, 255,
+ 0, BAMBOO_PT, WACOM_INTUOS_RES, WACOM_INTUOS_RES };
There is one outstanding issue. This device does not use the same
bits to indicate in-proximity that Bamboo's/TabletPC's are using but
everything else is the same. For the short term, you can edit the
file wacom_wac.c and modify the function wacom_bpt_pen(). Look for
line that says:
prox = (data[1] & 0x20) == 0x20; <--- Linux 3.3 or later
or
prox = (data[1] & 0x30) == 0x30; <--- Linux 3.2 or earlier
and change that to:
prox = (data[1] & 0x10) == 0x10;
I will see if there is a bit that is common between all products that
we can use for in-proximity or if there is some kind of if() statement
we can add to work with multiple product types.
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
