From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [RFC] Xen Virtual Framebuffer
Date: Mon, 05 Dec 2005 18:17:12 -0600 [thread overview]
Message-ID: <4394D888.3080200@us.ibm.com> (raw)
In-Reply-To: <4394C683.1070000@us.ibm.com>
I've made a page in the Wiki with more details:
http://wiki.xensource.com/xenwiki/VirtualFramebuffer
Regards,
Anthony Liguori
Anthony Liguori wrote:
> Now that's 3.0.0's out, I thought it would be a good time to bring up
> the topic of framebuffer virtualization.
>
> I threw together a proof-of-concept over the weekend of a simple
> virtual framebuffer/keyboard/mouse. The basic design is have a
> vmalloc()'d buffer in the guest exposed as /dev/fb0 and mmap()'d in
> dom0. There's also a simple message system for keyboard/mouse events.
>
> The first frontend is a GTK widget with python bindings (so it can
> easily be embedded in a larger management app) and a small python
> app. Right now, the VT system seems to work fine and X starts quite
> happily (using the fbdev driver). Clicking in the app captures the
> mouse/keyboard and ctrl+alt will release the capture.
>
> There's a readme and an hg bundle in the tarball below that explains
> how to set things up.
>
> Some interesting topics in this area are acceleration, whether we
> should implement our own X driver (or just enhance the fbdev driver
> since it uses no acceleration right now), and how to properly expose
> it over something like VNC.
>
> As always, feedback is greatly appreciated.
>
> http://www.cs.utexas.edu/users/aliguori/xen-vfb-20051205.tar.gz
>
> Regards,
>
> Anthony Liguori
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-12-06 0:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 23:00 [RFC] Xen Virtual Framebuffer Anthony Liguori
2005-12-06 0:17 ` Anthony Liguori [this message]
2005-12-06 0:35 ` Jon Smirl
2005-12-06 1:09 ` Anthony Liguori
2005-12-06 1:19 ` Jon Smirl
2005-12-06 1:25 ` Anthony Liguori
2005-12-06 1:31 ` Jon Smirl
2005-12-06 2:13 ` Anthony Liguori
2005-12-06 2:35 ` Jon Smirl
2005-12-06 2:55 ` Anthony Liguori
2005-12-06 3:13 ` Jon Smirl
2005-12-06 4:45 ` 答复: [Xen-devel] " 苗枫
2005-12-06 5:08 ` Anthony Liguori
2005-12-09 21:54 ` Tracy R Reed
2005-12-11 2:27 ` Jon Smirl
2005-12-16 12:14 ` Jacob Gorm Hansen
2005-12-16 15:48 ` Jon Smirl
2005-12-19 10:32 ` Jacob Gorm Hansen
2005-12-19 15:01 ` Jon Smirl
2005-12-06 0:50 ` M.A. Williamson
2005-12-06 1:19 ` Anthony Liguori
2005-12-06 10:50 ` Gerd Knorr
2005-12-06 11:06 ` Jacob Gorm Hansen
2005-12-06 14:54 ` Jon Smirl
2005-12-11 2:38 ` Jon Smirl
2005-12-16 11:20 ` Gerd Knorr
2005-12-16 16:16 ` Jon Smirl
2005-12-16 17:01 ` Gerd Knorr
2005-12-16 17:28 ` Anthony Liguori
2005-12-16 17:23 ` Anthony Liguori
2005-12-19 10:57 ` Gerd Knorr
-- strict thread matches above, loose matches on Subject: below --
2005-12-06 0:48 James Harper
2005-12-06 0:53 ` M.A. Williamson
2005-12-06 1:13 ` Jon Smirl
2005-12-06 2:51 ` M.A. Williamson
2005-12-06 1:15 ` Jon Smirl
2005-12-06 14:18 ` Charles Duffy
2005-12-06 10:59 Petersson, Mats
2005-12-06 20:41 John Byrne
2005-12-06 20:52 ` Anthony Liguori
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=4394D888.3080200@us.ibm.com \
--to=aliguori@us.ibm.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.