All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Gerd Knorr <kraxel@suse.de>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Jon Smirl <jonsmirl@gmail.com>
Subject: Re: [RFC] Xen Virtual Framebuffer
Date: Fri, 16 Dec 2005 11:28:38 -0600	[thread overview]
Message-ID: <43A2F946.9040608@us.ibm.com> (raw)
In-Reply-To: <43A2F2E5.4030300@suse.de>

Gerd Knorr wrote:

>> Another strategy for input would be to use USB input devices and the
>> USB over IP stack (or Xen USB support) to shift the devices between
>> domains.
>
>
> To handle remote display you need a xenconsoled-like helper 
> application in domain0 anyway (which for example could export the 
> display via vnc). That gives you remote input (via vnc or whatever 
> protocol) almost for free as well, and I think application-wise it is 
> much more convinient to take this route instead of using 
> hid-over-virtualusb-over-ip.

http://hg.codemonkey.ws/vncfb/

Is my first pass at a VNC server btw.

Regards,

Anthony Liguori

>> Installing multiple keyboards, USB audio devices, mice and multiple
>> video cards is one way to achieve multiuser computing.
>
>
> It's kida silly though to assign a domain some physical keyboard and a 
> virtual framebuffer.
>
> It might suddenly make much more sense once we can assign pci devices 
> to domU's again, so you can setup a domU with both real display and 
> keyboard, but thats completely unrelated to the virtual framebuffer ;)
>
> cheers,
>
>   Gerd
>
>

  reply	other threads:[~2005-12-16 17:28 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
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 [this message]
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=43A2F946.9040608@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=jonsmirl@gmail.com \
    --cc=kraxel@suse.de \
    --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.