All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: Keir.Fraser@cl.cam.ac.uk
Cc: xen-devel@lists.xensource.com
Subject: Re: beginnings of allowing more than the basic 80x25 VGA screen resolution
Date: Mon, 04 Jul 2005 01:28:56 -0600	[thread overview]
Message-ID: <s2c890b4.056@lucius.provo.novell.com> (raw)

>I'll happily take a patch that increases range of text modes supported

>by Xen. But why bother to propagate this info to XenLinux? You can set

>a vga-mode parameter on XenLinux's command line. To make this easier,

>we could have Xen automatically add a suitable mode parameter to 
>XenLinux command line, based on what was passed to Xen, if one wasn;t

>specified by the administrator.

Hmm, interesting. I would have hoped such thing would exist, but I
can't see how it could work, since the code affected by
CONFIG_VIDEO_SELECT (which is what in non-guest Linux deals with the
vga= option) doesn't even exist in XenLinux. Further more, since XEN is
a multiboot image, it would require infrastructure to switch back to
real mode for issuing the necessary INT10-s in the guest kernel, which I
think is neither very desirable nor existing.

So I must be missing something, but I'd need a pointer at where I would
have to look for the alternative code.

Jan

             reply	other threads:[~2005-07-04  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04  7:28 Jan Beulich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-04  8:35 beginnings of allowing more than the basic 80x25 VGA screen resolution Jan Beulich
     [not found] <s2c898b4.073@lucius.provo.novell.com>
2005-07-04  8:14 ` Keir Fraser
2005-07-04  8:51   ` Gerd Knorr
2005-07-06 21:37     ` Matthias Huber
2005-07-04  8:00 Jan Beulich
     [not found] <s2c890b4.055@lucius.provo.novell.com>
2005-07-04  7:50 ` Keir Fraser
2005-07-01 15:48 Jan Beulich
2005-07-01 15:52 ` Jon Smirl
2005-07-01 16:02 ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s2c890b4.056@lucius.provo.novell.com \
    --to=jbeulich@novell.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.