qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Support redirect -curses over a character driver
Date: Wed, 05 Mar 2008 13:38:52 -0600	[thread overview]
Message-ID: <47CEF6CC.9020300@codemonkey.ws> (raw)
In-Reply-To: <47CEF29C.9020408@qumranet.com>

Avi Kivity wrote:
> Anthony Liguori wrote:
>>
>> I'm on the fence because while I like what I've posted, I'd like to 
>> eventually tunnel the curses data over VNC in which case, having a 
>> separate option makes sense.  -curses would imply that the GUI would 
>> be rendered with curses.
>>
>
> I'm lost.  What does 'tunnel curses data over vnc' mean? A new 
> character cell based encoding (vs. pixel-based)?

Yes.  I was actually thinking of tunneling the curses data but another 
option would be a more proper character-based encoding.  The advantage 
of that is that you could also send over fonts.

>> So, 'qemu -curses' does what you think, 'qemu -cga 
>> telnet::1024,server -vnc :2' does what I want and still lets you 
>> interact with VNC, and then down the road 'qemu -cga vnc:org.qemu.vga 
>> -vnc :2' allows CGA tunneling over VNC.
>>
>
> What's -cga?

That would be the second option which controlled what the CGA data was 
sent over.  stdio would be the default.  It doesn't have to be -cga.

Regards,

Anthony Liguori

  reply	other threads:[~2008-03-05 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  2:34 [Qemu-devel] [PATCH] Support redirect -curses over a character driver Anthony Liguori
2008-03-05 11:58 ` Ian Jackson
2008-03-05 14:22   ` Anthony Liguori
2008-03-05 17:33   ` Avi Kivity
2008-03-05 19:05     ` Anthony Liguori
2008-03-05 19:21       ` Avi Kivity
2008-03-05 19:38         ` Anthony Liguori [this message]
2008-03-06  7:01           ` Avi Kivity
2008-03-06 21:19             ` 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=47CEF6CC.9020300@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).