On Fri, Oct 17, 2008 at 05:33:33PM -0700, Philip Langdale wrote:
The mouse appears as a regular PS/2 mouse and detecting that it's the
special vmmouse
a is done completely out of band; we can't change how this works for
compatibility reasons
so I've got to make do.
There's no possibility
On Mon, Oct 27, 2008 at 11:50:42AM +, Matthew Garrett wrote:
Hmm. The fdi seemed to be missing?
No it wasn't, I'm just blind. I think a better way of doing this would
be to make the callout conditional on there being a PCI device with the
vmware subsystem. Probing for a vmware mouse on
On Mon, Oct 27, 2008 at 08:35:39AM -0700, Philip Langdale wrote:
Matthew Garrett wrote:
No it wasn't, I'm just blind. I think a better way of doing this would
be to make the callout conditional on there being a PCI device with the
vmware subsystem. Probing for a vmware mouse on every
Matthew Garrett wrote:
Yeah, that looks better to me. Do you actually need to do the probing in
that case, or are there VMWare systems that will expose a PS/2 mouse
port and not allow you to run vmmouse against it?
Yes, the active check is required - it's possible to configure a VM with
the
On Fri, Oct 17, 2008 at 05:33:33PM -0700, Philip Langdale wrote:
I've attached example fdi and callout script implementations (the
vmmouse-detect
binary that is referred to is debian/ubuntu specific but that can be folded
into
a hald-probe style binary or bundled elsewhere if desired)
So,
