On Wed, Mar 23, 2011 at 11:36:25AM +0100, 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_IOC
On Wed, Mar 23, 2011 at 01:48:45PM -0500, Favux ... wrote:
> 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. Apparent
On Wed, Mar 23, 2011 at 12:55 PM, Eduard Hasenleithner
wrote:
> Now I even tested the linuxwacom/src/2.6.30 driver on a fresh
> linux-2.6.38 from kernel.org. I had to do a few minor modifications to
> the driver source (ioctl has been renamed to unlocked_ioctl in
> usb_device and input->abs is mis
Now I even tested the linuxwacom/src/2.6.30 driver on a fresh
linux-2.6.38 from kernel.org. I had to do a few minor modifications to
the driver source (ioctl has been renamed to unlocked_ioctl in
usb_device and input->abs is missing) but it works perfectly!
Apparently the driver did not diverge too
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,
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 eve
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 breaki
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. Idea
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
On Tue, Mar 22, 2011 at 10:47:12PM +0100, Eduard Hasenleithner wrote:
> 2011/3/22 Peter Hutterer :
> >> It defines a new pseudo-property "Wacom Button Image". When
> >> XChangeDeviceProperty is called with a 2049 octet data, the first
> >> octet is taken as the button number, and the remaining 2048
Hi
2011/3/22 Peter Hutterer :
>> It defines a new pseudo-property "Wacom Button Image". When
>> XChangeDeviceProperty is called with a 2049 octet data, the first
>> octet is taken as the button number, and the remaining 2048 octets are
>> taken as the image.
>
> this approach isn't all too differe
On Tue, Mar 22, 2011 at 12:13:13AM +0100, Eduard Hasenleithner wrote:
> Here I have a very early draft for setting the Intuos4 OLED display by
> means of xsetwacom.
nice work!
> It defines a new pseudo-property "Wacom Button Image". When
> XChangeDeviceProperty is called with a 2049 octet data, t
Hi
Here I have a very early draft for setting the Intuos4 OLED display by
means of xsetwacom.
It defines a new pseudo-property "Wacom Button Image". When
XChangeDeviceProperty is called with a 2049 octet data, the first
octet is taken as the button number, and the remaining 2048 octets are
taken
13 matches
Mail list logo
