On Mi, 2011-02-02 at 14:48 +1000, Peter Hutterer wrote:
^^
FYI: It's been a while ...
> sorry, late again. conference last week.
>
> On Thu, Jan 27, 2011 at 02:11:35PM +0100, Gerd Hoffmann wrote:
> > Next revision the pvmouse protocol. It is quite different now, I've
> > decided t
sorry, late again. conference last week.
On Thu, Jan 27, 2011 at 02:11:35PM +0100, Gerd Hoffmann wrote:
> Next revision the pvmouse protocol. It is quite different now, I've
> decided to move to a model with one message per updated value,
> simliar to the linux input layer. There isn't a "mouse
On Thu, Jan 27, 2011 at 04:32:40PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> >>typedef struct qemu_pvmouse_ack {
> >> uint32_t features; /* qemu_pvtable_features */
> >
> >Why does this comment say "qemu_pvtable_features" and the one above
> >says "qemu_pvmouse_features"?
>
> Not intentional, w
Hi,
typedef struct qemu_pvmouse_ack {
uint32_t features; /* qemu_pvtable_features */
Why does this comment say "qemu_pvtable_features" and the one above
says "qemu_pvmouse_features"?
Not intentional, will fix. Leftover because it is misspelled (t in
table*t* missing), so the search+
On Thu, Jan 27, 2011 at 02:11:35PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> Next revision the pvmouse protocol. It is quite different now, I've
> decided to move to a model with one message per updated value,
> simliar to the linux input layer. There isn't a "mouse move"
> message any more. A mo
Hi,
Next revision the pvmouse protocol. It is quite different now, I've
decided to move to a model with one message per updated value, simliar
to the linux input layer. There isn't a "mouse move" message any more.
A mouse move event will be three messages now: one to update X, one to
upd
On Thu, Jan 13, 2011 at 11:19:52AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> Just throwing a quick writeup into the ring to kickstart the design
> discussion ;)
I apologize for not reading everything before sending, I just don't want
to forget this detail: Whatever we design needs to address having
On 01/13/11 12:01, Stefan Hajnoczi wrote:
Can you elaborate how the spice display channel comes into play? On a
physical machine you just have input devices with no notion of
display. It's up to the windowing system to process input events and
handle multihead. Why does a pv tablet tie itself
Can you elaborate how the spice display channel comes into play? On a
physical machine you just have input devices with no notion of
display. It's up to the windowing system to process input events and
handle multihead. Why does a pv tablet tie itself to a display
channel?
What about mouse whee
Hi,
Just throwing a quick writeup into the ring to kickstart the design
discussion ;)
cheers,
Gerd
#ifndef __QEMU_PVTABLET__
#define __QEMU_PVTABLET__ 1
/*
* qemu patavirtual tablet interface
*/
#include
/* our virtio-serial channel */
#define QEMU_PVTABLET_NAME "org.qemu.pvtablet.0"
10 matches
Mail list logo
