All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: Jan Beulich <JBeulich@novell.com>
Cc: xiaofeng.ling@intel.com, xen-devel@lists.xensource.com
Subject: Re: beginnings of allowing more than the basic 80x25 VGAscreen resolution
Date: Tue, 5 Jul 2005 16:47:18 +0200	[thread overview]
Message-ID: <20050705144718.GB7009@bytesex> (raw)
In-Reply-To: <s2ca4091.019@lucius.provo.novell.com>

  Hi,

> First of all, at least grub 0.9x (which is what I think is currently in
> wide-spread use) doesn't seem to have even infrastructure to report
> video information, not to think about changing the video mode. But I
> agree that that'd be the best place for this to live.

Distributions have a graphical boot menu, so grub must do some
mode switching already.  Havn't looked at the grub code, but I
think adding that wouldn't be too hard.  Might be vanilla grub
doesn't do that so you'll have to dig into distribution patches.

> Second, simply passing on the multi-boot info to the guest kernel would
> still require that the interface between XEN and the guest kernel be
> changed.

I agree here.

> >Text mode is really simple, that is just another screen size
> >than 80x25, but completely identical otherwise.  Font stuff is
> >handled by bios and vga hardware, nothing to worry about here.
> 
> That builds on the assumption that the boot loader actually has the
> necessary infrastructure. With the assumption that it's quite far away
> from that, I would still think that XEN should try provide the ability
> to change modes (at least until the boot loader actually does).

I would try to hack grub (or syslinux, Tim's multiboot loader is
merged upstream ;) instead of adding a temporary solution to
xen.  YMMV.

> Once XEN is so stable that you can afford not seeing its initial
> messages, leaving the screen alone when in graphics mode is certainly an
> option. But I don't think that's an option right now.

For hacking on xen having a serial console is a great thing.
My xen devel machine doesn't even have a monitor connected ;)

  Gerd

-- 
panic("it works"); /* avoid being flooded with debug messages */

       reply	other threads:[~2005-07-05 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s2ca4091.019@lucius.provo.novell.com>
2005-07-05 14:47 ` Gerd Knorr [this message]
2005-07-05 14:11 beginnings of allowing more than the basic 80x25 VGAscreen resolution Jan Beulich
     [not found] <s2ca350f.097@lucius.provo.novell.com>
2005-07-05 13:28 ` Keir Fraser
2005-07-05 13:42   ` Gerd Knorr
  -- strict thread matches above, loose matches on Subject: below --
2005-07-05 13:22 Jan Beulich
2005-07-05 12:10 Ling, Xiaofeng
2005-07-05 12:58 ` Gerd Knorr
2005-07-05 13:07   ` Keir Fraser
2005-07-05 17:22     ` David Hopwood
2005-07-06  8:40       ` 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=20050705144718.GB7009@bytesex \
    --to=kraxel@suse.de \
    --cc=JBeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xiaofeng.ling@intel.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.