WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] RE: [PATCH] Paravirtual framebuffer use xvc for xenconsole [

To: "Jeremy Katz" <katzj@xxxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: [PATCH] Paravirtual framebuffer use xvc for xenconsole [4/6]
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 18 Aug 2006 22:22:40 +0100
Cc: Anthony Liguori <aliguori@xxxxxxxxxx>, Amos Waterland <apw@xxxxxxxxxx>, Markus Armbruster <armbru@xxxxxxxxxx>, Ian Pratt <ian.pratt@xxxxxxxxxxxxx>, Christian Limpach <chris@xxxxxxxxxxxxx>
Delivery-date: Fri, 18 Aug 2006 14:23:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbDCdU8M/TLWO9RTsKUAk5NuuMrAgAAZnvQ
Thread-topic: [PATCH] Paravirtual framebuffer use xvc for xenconsole [4/6]
> 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
> 
> Signed-off-by: Jeremy Katz <katzj@xxxxxxxxxx>

If we're going down the xvc0 route, wouldn't we want to change the default 
behaviour too? I believe the current patch registers as ttyS0 for dom0 and xvc0 
for other doms. Wouldn't we want to register as xvc0 regardless?

Any idea when we're hear from LANANA?

Thanks,
Ian 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>