All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0/2] PV framebuffer
Date: Fri, 10 Nov 2006 09:53:44 +0100	[thread overview]
Message-ID: <87odrfptrb.fsf@pike.pond.sub.org> (raw)

Summary of changes:

* Use xenbus_device API.

  Some xm configuration magic is still missing, see below.

* Negotiate features through Xen Store.

* Key identification

  Discussed at length on this list.  I fixed sdlfb to use scan codes
  (assumes standard AT or PS/2 keyboard).  vncfb is not fixable.  See
  comments in the code.

* Drop XENKBD_TYPE_BUTTON in favour of XENKBD_TYPE_KEY.  Simpler, and
  gets rid of the three button limit.

* Support shadow translate mode guests (untested).

* Absolute mouse pointer (optional feature)

* Fix event delivery and receipt notification.

* Use __s32 for coordinates instead of __u16 and __s16 for pixel
  coordinates, to match linux/input.h, which uses int.

* Don't drop the first pointer event on the floor in vncfb.

* Backends diagnose lost kbd events.

* Some renames to make xenkbd and xenfb drivers more similar.  Sorry
  for the extra diffs, but the inconsistencies were just too
  confusing.

Known issues:

* What to do when backend closes the connection?  I guess we want to
  keep the frontend running, ready for another connection.  This works
  already, but in a rather hackish and limited way.

* What to do when the frontend closes the connection?  Make backend
  exit?

* What happens when multiple backends connect to the same frontend?
  Chaos, most likely.

* Resume not implemented.

* xm configuration magic doesn't know the new devices, yet.  I'm
  ignorant of how this magic works, perhaps somebody can lend me a
  hand with it.

  Workaround:

  - Convert /etc/xen/FOO into FOO.sxp with xm create -n.  Make sure to
    delete the junk at the beginning of the output.

  - Add
        (device (vfb ()))
        (device (vkbd ())
    and change kernel and ramdisk to point to suitable copies.

  - xm create -F FOO.sxp.

* A couple of FIXMEs are still left in the code.

Future work:

* Investigate ditching LibVNCServer.

* Use grant tables when they become capable of mapping the
  framebuffer.

* Support multiple framebuffers.

* Dynamic screen resolution.

* Support other keyboards.

             reply	other threads:[~2006-11-10  8:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10  8:53 Markus Armbruster [this message]
2006-11-10  9:32 ` [PATCH 0/2] PV framebuffer Gerd Hoffmann
2006-11-12 14:20 ` Steven Smith
2006-11-13 15:29   ` Markus Armbruster
2006-11-21 17:48   ` Markus Armbruster
2006-11-16  1:08 ` Atsushi SAKAI
2006-11-16  8:21   ` Markus Armbruster
2006-11-16 10:31     ` Atsushi SAKAI
2006-11-16 11:46       ` Markus Armbruster
2006-11-17 13:22 ` Markus Armbruster
2006-11-22 14:18   ` Steven Smith
2006-11-22 15:31     ` Markus Armbruster
2006-11-24  8:05   ` Markus Armbruster
2006-11-24  8:07     ` Markus Armbruster
2006-11-29 10:31     ` Steven Smith
2006-11-29 12:43       ` Markus Armbruster
2006-11-21  5:23 ` Kasai Takanori
2006-11-21  5:50   ` Markus Armbruster
2006-11-21  9:43     ` Ewan Mellor
2006-11-22 11:47       ` Kasai Takanori
2006-11-22 13:30         ` Markus Armbruster
2006-11-24  1:54           ` Kasai Takanori
2006-11-24  8:15             ` Markus Armbruster

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=87odrfptrb.fsf@pike.pond.sub.org \
    --to=armbru@redhat.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.