qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Port E9 hack, for debugging purposes
Date: Mon, 17 Jan 2005 23:01:16 +0100	[thread overview]
Message-ID: <41EC35AC.7090006@bellard.org> (raw)
In-Reply-To: <41EBC1FB.8050506@enix.org>

There are already similar debug features in hw/pc.c for the Bochs BIOS, 
but they are not enabled by default because I consider there were useful 
only in rare cases.

I would accept the "e9 hack" only if it was dynamically configurable and 
if it used a generic character device (as the serial or parallel ports) 
to output its results. The command line option should be '-port-e9 
stdio' or something similar.

Fabrice.

Thomas Petazzoni wrote:
> Hello,
> 
> Johannes Schindelin a écrit :
> 
>> I like it. It's simple and elegant, and your patch seems correct to me.
> 
> 
> Thanks.
> 
> After sending the patch, I thought that maybe it would be better to 
> transform the configure time option to enable/disable the port E9 hack 
> into a runtime option.
> 
> Currently, devices are not enabled/disabled through compile time 
> options, but through runtime options. Doing it the same way for port E9 
> hack may be more coherent.
> 
> What do you think ?
> 
> Thomas
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

  reply	other threads:[~2005-01-17 22:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15 17:06 [Qemu-devel] [PATCH] Port E9 hack, for debugging purposes Thomas Petazzoni
2005-01-17 13:31 ` Johannes Schindelin
2005-01-17 13:47   ` Thomas Petazzoni
2005-01-17 22:01     ` Fabrice Bellard [this message]
2005-01-26 22:24       ` Thomas Petazzoni
2005-01-26 23:57         ` James Mastros
2005-01-27  8:19           ` Thomas Petazzoni
2005-02-03 12:29         ` Thomas Petazzoni

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=41EC35AC.7090006@bellard.org \
    --to=fabrice@bellard.org \
    --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).