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


[Xen-devel] console questions

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] console questions
From: Aron Griffis <aron@xxxxxx>
Date: Mon, 6 Aug 2007 17:29:23 -0400
Delivery-date: Mon, 06 Aug 2007 14:27:16 -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>
Mail-followup-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.16 (2007-06-11)
A couple questions regarding xvc...

1. xencons=xvc works and makes more sense than clobbering ttyS0 by
   default.  Is there some reason that the default for xencons is
   still ttyS on dom0?  Sure hvc is coming, but would it be reasonable
   to change the default for xencons in the meantime?

2. xencons=xvc1 and upward is accepted by the kernel, but it just
   changes the userland naming.  The major/minor remains the same at
   204/191.  What's the point of this?  Is there any reason to allow
   anything other than xencons=xvc or xencons=xvc0?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>