Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-09 Thread Brad Campbell
Lonnie Mendez wrote: Please see the patch posted yesterday to this mailing list: http://gnome.dnsalias.net/patches/qemu-hidmousexp.patch Ta for that.. not sure how I missed it. Now to try and get it to work.. Sprinkling printf's around the place it inits the usb controller and mouse, regis

Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-09 Thread Lonnie Mendez
Brad Campbell wrote: Leonardo E. Reiter wrote: This is by no means a complete patch (do not apply it as it will break usb-hid.c), but it adjusts the report descriptor in usb-hid.c to provide position in 16-bits, and in absolute coordinates: Index: usb-hid.c =

Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-09 Thread Brad Campbell
Leonardo E. Reiter wrote: This is by no means a complete patch (do not apply it as it will break usb-hid.c), but it adjusts the report descriptor in usb-hid.c to provide position in 16-bits, and in absolute coordinates: Index: usb-hid.c =

Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-09 Thread andrzej zaborowski
On 09/04/06, Leonardo E. Reiter <[EMAIL PROTECTED]> wrote: > Yeah, the min/max value thing would be a pain for sure. The X server > config method seems to be the best bet. > > On another note, I am trying to imagine what would make logical sense > for say, a touch screen. For example, an LCD pane

Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-09 Thread Brad Campbell
Leonardo E. Reiter wrote: Yeah, the min/max value thing would be a pain for sure. The X server config method seems to be the best bet. On another note, I am trying to imagine what would make logical sense for say, a touch screen. For example, an LCD panel has a native resolution, say 1024x7

Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-09 Thread Leonardo E. Reiter
Yeah, the min/max value thing would be a pain for sure. The X server config method seems to be the best bet. On another note, I am trying to imagine what would make logical sense for say, a touch screen. For example, an LCD panel has a native resolution, say 1024x768. It would then emulate

Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-09 Thread Jim C. Brown
On Sat, Apr 08, 2006 at 11:36:19PM -0500, Anthony Liguori wrote: > I was looking through the Xorg evdev driver and it doesn't appear to > support absolute coordinate reporting. evdev is how the USB mouse would > show up to userspace. A little googling confirmed it for me: Doesn't look like a m

Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-08 Thread Anthony Liguori
I was looking through the Xorg evdev driver and it doesn't appear to support absolute coordinate reporting. evdev is how the USB mouse would show up to userspace. A little googling confirmed it for me: http://lists.freedesktop.org/archives/xorg/2005-September/010140.html USB wacom still seem

Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-08 Thread Leonardo E. Reiter
Brad Campbell wrote: Now it's a long time since I've hacked on it but I wrote a userspace touch screen driver for win9x years ago that did just this.. I seem to recall having to scale the real touchscreen values to between 0x0 and 0x before feeding them in to the windows message queue. Fro

Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-08 Thread Brad Campbell
Leonardo E. Reiter wrote: This is by no means a complete patch (do not apply it as it will break usb-hid.c), but it adjusts the report descriptor in usb-hid.c to provide position in 16-bits, and in absolute coordinates: Index: usb-hid.c =

Re: [Qemu-devel] Absolute USB-HID device musings (was Re: VNC Terminal Server)

2006-04-08 Thread Leonardo E. Reiter
Sorry, the patch is not only incomplete, but totally wrong :( The 0x16 should be 0x10, like this: -0x25, 0x7F, 0x75, 0x08, 0x95, 0x02, 0x81, 0x06, +0x25, 0x7F, 0x75, 0x10, 0x95, 0x02, 0x81, 0x02, I must have had a momentary lapse of [radix] reason :) - Leo Reiter -- Leonardo E. Rei