This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] Paravirt framebuffer use xvc as console [4/5]

To: Steven Smith <sos22-xen@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Paravirt framebuffer use xvc as console [4/5]
From: Jeremy Katz <katzj@xxxxxxxxxx>
Date: Tue, 05 Sep 2006 12:11:59 -0400
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Markus Armbruster <armbru@xxxxxxxxxx>, sos22@xxxxxxxxxxxxx, Amos Waterland <apw@xxxxxxxxxx>
Delivery-date: Tue, 05 Sep 2006 09:13:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060904090111.GB4812@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1157227130.11059.44.camel@xxxxxxxxxxxxxx> <20060904090111.GB4812@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2006-09-04 at 10:01 +0100, Steven Smith wrote:
> > This is the patch from Amos Waterland for the xenconsole to
> > use /dev/xvc0 instead of taking over ttys.  I've fixed a few places
> > which needed to check for XVC mode in addition to serial mode.  Also,
> > until LANANA responds with an official minor, I've adjusted it to use
> > char 250/187 (in the experimental range) as opposed to 204/187.
> > 
> > (Should be identical to this patch from last time)
> Does this have anything to do with the virtual framebuffer work, or
> does it stand alone?

It stands alone, but without it, the framebuffer bits get a little
confusing to actually try to have used as the console.

> > @@ -194,11 +209,17 @@ static int __init xen_console_init(void)
> >             kcons_info.write = kcons_write_dom0;
> >     } else {
> >             if (xc_mode == XC_DEFAULT)
> > -                   xc_mode = XC_TTY;
> > +                   xc_mode = XC_XVC;
> Not convinced we want to change the default until a little while after
> the rest of the patch gets merged.

The default *HAS* to be changed -- otherwise, the xvc console tries to
take over ttys (which is really really really wrong in the guest)


Xen-devel mailing list