[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Re: [Xen-devel] [RFC] support console resolutions better than 80x25


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Tue, 15 Aug 2006 17:38:57 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 15 Aug 2006 09:39:20 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbAiU2BjASXjyx8EduqSQAKle7CWA==
  • Thread-topic: [PATCH] Re: [Xen-devel] [RFC] support console resolutions better than 80x25



On 15/8/06 5:11 pm, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

>> * 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.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.