qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] handling SIGWINCH with qemu -nographic
Date: Tue, 16 Oct 2007 22:21:54 +0100	[thread overview]
Message-ID: <200710162221.56166.paul@codesourcery.com> (raw)
In-Reply-To: <47152451.7020803@mail.berlios.de>

> I think your question is quite reasonable. Imagine a Linux host
> running X Windows and a terminal like xterm or kconsole.
> Then run a program like "top" or "less" in this terminal.
> When a user changes the size of the console window, top, less
> and other console applications get notified of this change by SIGWINCH.
>
> Now run a similar program using QEMU's user mode emulation.
> Why should it not be possible to get SIGWINCH in QEMU and
> pass it on to the program in user mode emulation, so it can
> behave like a native Linux application and change its appearance?
>
> I don't think that implementing this is very difficult, so it will be
> done.

Try doing the same thing with a real machine connected via a serial port.
It won't work.

The difference is that for local applications (and remote terminals via telnet 
or ssh) you have OOB mechanisms to transmit event data (e.g. terminal size). 
A UART only gives you a simple serial connection. If you want things like 
terminal resizing to work you need to run some more complicated protocol over 
the serial link, with appropriate tty emulation on either end.

Paul

  reply	other threads:[~2007-10-16 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16  1:15 [Qemu-devel] handling SIGWINCH with qemu -nographic Jeff Carr
2007-10-16  2:32 ` Paul Brook
2007-10-16 18:21   ` Jeff Carr
2007-10-16 20:51     ` Stefan Weil
2007-10-16 21:21       ` Paul Brook [this message]
2007-10-20  0:24       ` Rob Landley
2007-10-16 14:04 ` Stuart Brady
2007-10-20  0:22 ` Rob Landley

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=200710162221.56166.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --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).