qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: ryanh@us.ibm.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [5309] Reintroduce TEXT_CONSOLE_FIXED_SIZE and TEXT_CONSOLE for resizable vc's.
Date: Sun, 2 Nov 2008 19:52:08 +0100	[thread overview]
Message-ID: <fb249edb0811021052u36a1d188of04290a83a24ee22@mail.gmail.com> (raw)
In-Reply-To: <490DF4AB.60304@web.de>

2008/11/2 Jan Kiszka <jan.kiszka@web.de>:
> Ryan Harper wrote:
>> * Andrzej Zaborowski <balrogg@gmail.com> [2008-09-23 22:37]:
>>> Revision: 5309
>>>           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5309
>>> Author:   balrog
>>> Date:     2008-09-24 03:32:33 +0000 (Wed, 24 Sep 2008)
>>>
>>> Log Message:
>>> -----------
>>> Reintroduce TEXT_CONSOLE_FIXED_SIZE and TEXT_CONSOLE for resizable vc's.
>>>
>>> This partially reverts r4812 to fix an issue highlighted by Ryan Harper
>>> with all vc's being fixed size which prevented backends with resizable
>>> window (curses) from displaying okay.
>>
>> Excellent!  This fixed -curses mode for me.
>>
>
> ...but it breaks setting the monitor etc. consoles to reasonable sizes
> in case the graphical console is too small (e.g. the Musicpal uses
> 384x192 pixels). Is there no way to address both issues?

-monitor vc:800x600 should cause the monitor to be
TEXT_CONSOLE_FIXED_SIZE, i.e. like before this commit.  Maybe
vc:80Cx25C should be default for all text consoles when using SDL and
for -curses vc should be default (currently the default is a mix).

Cheers

  reply	other threads:[~2008-11-02 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24  3:32 [Qemu-devel] [5309] Reintroduce TEXT_CONSOLE_FIXED_SIZE and TEXT_CONSOLE for resizable vc's Andrzej Zaborowski
2008-09-24 17:35 ` Ryan Harper
2008-11-02 18:42   ` [Qemu-devel] " Jan Kiszka
2008-11-02 18:52     ` andrzej zaborowski [this message]
2008-11-02 19:10       ` Jan Kiszka

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=fb249edb0811021052u36a1d188of04290a83a24ee22@mail.gmail.com \
    --to=balrogg@gmail.com \
    --cc=jan.kiszka@web.de \
    --cc=qemu-devel@nongnu.org \
    --cc=ryanh@us.ibm.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 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).