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] Xen virtual console driver question

To: Amos Waterland <apw@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen virtual console driver question
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 3 Aug 2006 09:01:15 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 03 Aug 2006 01:01:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060802214226.GA14656@xxxxxxxxxxxxxxxxxxxxx>
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: <20060802214226.GA14656@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 2 Aug 2006, at 22:42, Amos Waterland wrote:

I am currently using the below patch, but would really prefer not to.
It's basic approach is to have the Xen virtual console driver react
"gracefully" in the case that a real serial driver has already
registered ttyS0-ttyS3.  It's current behavior is to fail if the 8250
driver was initialized ahead of it, and console is lost. In the process
I found a bug in Linux, and have included the patch for it since
otherwise the Xen driver initialization will succeed but with negative
side effects in the kobject subsystem.

What is the story?

We need to obtain our own device number and then patch the driver. It'd be great if someone else wants to look into this.

 -- Keir

Xen-devel mailing list