qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Jim C. Brown" <jma5@umd.edu>
Subject: Re: [Qemu-devel] make stdio monitor default
Date: Sun, 20 Mar 2005 11:26:12 +0000	[thread overview]
Message-ID: <200503201126.13115.paul@codesourcery.com> (raw)
In-Reply-To: <20050319041741.GA16957@jbrown.mylinuxbox.org>

> I agree that vc should be the default for Windows, but that for Linux (and
> Unix) having stdio default would be better. (This is of course a policy
> decision, not a coding or feature one, as both stdio and vc can be used in
> either Linux or Windows host). It would be nice to get other opinions on 
> this. 

I agree, although I think the proper fix is to move the logic into the 
configure script and make it a configure time option. 
ie ./configure --enable-monitor=foo would set the default.

> --- vl.c.old Fri Mar 18 23:01:24 2005
> +++ vl.c Fri Mar 18 23:02:03 2005
> @@ -3031,7 +3031,11 @@
>      has_cdrom = 1;
>      cyls = heads = secs = 0;
>      translation = BIOS_ATA_TRANSLATION_AUTO;
> +#ifndef _WIN32
>      pstrcpy(monitor_device, sizeof(monitor_device), "vc");
> +#else
> +    pstrcpy(monitor_device, sizeof(monitor_device), "stdio");
> +#endif
>  
>      pstrcpy(serial_devices[0], sizeof(serial_devices[0]), "vc");
>      for(i = 1; i < MAX_SERIAL_PORTS; i++)

Have you tested this patch? It looks like it does the opposite of what you are 
suggesting.

Paul

  reply	other threads:[~2005-03-20 11:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-19  4:17 [Qemu-devel] make stdio monitor default Jim C. Brown
2005-03-20 11:26 ` Paul Brook [this message]
2005-03-20 19:56   ` Jim C. Brown

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=200503201126.13115.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=jma5@umd.edu \
    --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).