All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Haxby <john.haxby@oracle.com>
To: Eamon Walsh <ewalsh@tycho.nsa.gov>
Cc: Olaf Hering <olaf@aepfle.de>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] fbfront: advertise either absolute or relative coordinates
Date: Fri, 11 Mar 2011 12:43:08 +0000	[thread overview]
Message-ID: <4D7A18DC.50500@oracle.com> (raw)
In-Reply-To: <4D792D59.9040801@tycho.nsa.gov>

On 10/03/11 19:58, Eamon Walsh wrote:
> We have had an issue here where the "request-abs-pointer" key is appearing in XenStore _after_ the backend has gone to the Connected state.  Qemu xenfb.c checks for this key in the "connect()" callback, causing it to miss the key and default to relative coordinates.

This was submitted to qemu-devel ages ago -- 27-Aug-2010 according to my
archives.   That was in fact the second time it was submitted (by
Stefano) but it was never picked up despite a couple of reminders :-(

This is the original thread on xen-devel:
http://markmail.org/thread/fikfzaxgaj4ay6oe

And the resend-thread in qemu-devel:
http://lists.gnu.org/archive/html/qemu-devel/2010-08/msg01515.html

I think the patch you proposed, Eamon, is the same as the one that
didn't work properly -- it's certainly a lot simpler than the two-part
patch that I wrote (and that patch has been in production for OracleVM
for a while, it seems solid).

jch

      parent reply	other threads:[~2011-03-11 12:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 17:58 [PATCH] fbfront: advertise either absolute or relative coordinates Olaf Hering
2011-03-10 18:09 ` Stefano Stabellini
2011-03-10 18:14   ` Olaf Hering
2011-03-10 19:15     ` Stefano Stabellini
2011-03-10 19:58       ` Eamon Walsh
2011-03-11 11:58         ` Stefano Stabellini
2011-03-11 12:44           ` John Haxby
2011-03-11 12:54             ` Stefano Stabellini
2011-03-11 12:43         ` John Haxby [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D7A18DC.50500@oracle.com \
    --to=john.haxby@oracle.com \
    --cc=ewalsh@tycho.nsa.gov \
    --cc=olaf@aepfle.de \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.