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:
iProduct 2 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 vvvv
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 -vvvv -d 0b05:179f
Bus 002 Device 008: ID 0b05:179f ASUSTek Computer, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 16
idVendor 0x0b05 ASUSTek Computer, Inc.
idProduct 0x179f
bcdDevice 1.29
iManufacturer 1 ASUSTek Computer, Inc.
iProduct 2 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
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
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
bDescriptorType 33
bcdHID 1.10
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 201
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
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
