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: [PATCH] Re: [Xen-devel] [RFC] support console resolutions better tha

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [PATCH] Re: [Xen-devel] [RFC] support console resolutions better than 80x25
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 16 Aug 2006 08:42:07 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 15 Aug 2006 23:42:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C107B731.E91%Keir.Fraser@xxxxxxxxxxxx>
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: <44E20E65.76E4.0078.0@xxxxxxxxxx> <C107B731.E91%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> * txt_x/txt_y aren't written by Xen nor are they read by Linux -- can we
>>> kill the fields?
>> Linux actually uses orig_y (in earlyprintk.c), so I'd like to keep them and
>> at some point properly fill them so Linux can propagate these values.
>> You'll note that currently I simply set orig_y to the end of the screen, 
>> since
>> Xen is virtually guaranteed to push out at least a screenful of information
>> before starting Linux.
>> The problem here is that these fields cannot be set in fill_console_info, but
>> would need to be set once it is certain that there is not going to be any
>> more (non-debug) output from Xen.
>How will Linux know when we start filling them in properly? (0,0) would be a
>valid setting!
>We should set them to the conservative (bottom-of-screen) value in Xen and
>read the values from console_info in Linux, rather than initialising from
>hardcoded values in Linux.

That's fine with me.


Xen-devel mailing list

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