From: Kevin O'Connor <kevin@koconnor.net>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: seabios <seabios@seabios.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [SeaBIOS] seabios serial console vs. sgabios
Date: Fri, 3 Nov 2017 16:13:19 -0400 [thread overview]
Message-ID: <20171103201319.GA26212@morn.lan> (raw)
In-Reply-To: <1509638660.11873.13.camel@redhat.com>
On Thu, Nov 02, 2017 at 05:04:20PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> One problem we have with the serial console support in seabios and
> sgabios: It can happen that both are activated. We'll go fix that in
> qemu, but that'll work for new qemu versions only, not for the old
> already released ones.
>
> So I think it would be useful if seabios makes sure sgabios and serial
> console are not both active at the same time, i.e. in case we find
> "vgaroms/sgabios.bin" being present either turn off builtin serial
> console, or don't load sgabios (and possibly also enable builtin serial
> console).
I'm not sure on this one. If qemu tells seabios to load a rom, I
think it really should do that.
If future versions of qemu will be changed to not request sgabios when
sercon is enabled, then maybe the issue isn't large enough to worry
about (it only affects no-graphics, new seabios, old qemu). If that's
not safe, perhaps we should revisit how seabios enables sercon so
there is no confusion.
-Kevin
prev parent reply other threads:[~2017-11-03 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 16:04 [Qemu-devel] seabios serial console vs. sgabios Gerd Hoffmann
2017-11-02 16:11 ` Daniel P. Berrange
2017-11-02 16:13 ` Paolo Bonzini
2017-11-03 6:49 ` Gerd Hoffmann
2017-11-03 10:10 ` Daniel P. Berrange
2017-11-03 10:43 ` Gerd Hoffmann
2017-11-06 6:09 ` Markus Armbruster
2017-11-03 20:13 ` Kevin O'Connor [this message]
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=20171103201319.GA26212@morn.lan \
--to=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.