Le vendredi 30 décembre 2011 à 11:37 -0600, Chris Bagwell a écrit :
> On Fri, Dec 30, 2011 at 10:17 AM, Favux ... <favux...@gmail.com> 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 vvvv
> > 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/pci0000:00/0000: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-0000: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
