All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Joe Bonasera <joe.bonasera@sun.com>
Cc: xen-devel@lists.xensource.com, edward.pilatowicz@sun.com
Subject: Re: better console support
Date: Thu, 25 Jan 2007 18:55:29 +0000	[thread overview]
Message-ID: <C1DEADA1.8401%keir@xensource.com> (raw)
In-Reply-To: <45B8FB55.1080306@sun.com>

On 25/1/07 18:47, "Joe Bonasera" <joe.bonasera@sun.com> wrote:

> The standard internal testing setup inside Sun that most
> people run with is debug Xen and debug dom0 both
> sharing either the VGA console or a single serial port console.
> We also see field support of the eventual product needing the
> ability to interact with both consoles on the same physical
> device.  So we want to make the dom0 just handle sharing the console
> as automatically as possible.

You can already detect if Xen has locked out com1 or com2: try reading one
of the UART registers (or perhaps write-then-read). If you get back all ones
then you're locked out.

Maybe a vgakeep flag would be useful. We could add a SIF_VGA_IN_USE flag or
something.

 -- Keir

  reply	other threads:[~2007-01-25 18:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1HA4sG-0007vw-5h@host-192-168-0-1-bcn-london>
2007-01-25 17:00 ` better console support Joe Bonasera
2007-01-25 17:48   ` Keir Fraser
2007-01-25 18:47     ` Joe Bonasera
2007-01-25 18:55       ` Keir Fraser [this message]
2007-01-26  0:58         ` Edward Pilatowicz
2007-01-26  9:33           ` Keir Fraser
2007-01-26 10:29             ` John Levon
2007-01-26 12:54               ` Christoph Egger
2007-01-26 13:11                 ` Keir Fraser
2007-01-26 13:50                   ` Jan Beulich
2007-01-26 13:59                     ` Keir Fraser
2007-01-26 16:01                   ` Joe Bonasera
2007-01-31 22:56                     ` Edward Pilatowicz

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=C1DEADA1.8401%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=edward.pilatowicz@sun.com \
    --cc=joe.bonasera@sun.com \
    --cc=xen-devel@lists.xensource.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 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.