All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xiaofeng.ling@intel.com, xen-devel@lists.xensource.com,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: beginnings of allowing more than the basic 80x25 VGAscreen resolution
Date: Tue, 5 Jul 2005 15:42:50 +0200	[thread overview]
Message-ID: <20050705134250.GA6059@bytesex> (raw)
In-Reply-To: <84096aa1f3e6451954dc674d5f2b29e6@cl.cam.ac.uk>

On Tue, Jul 05, 2005 at 02:28:27PM +0100, Keir Fraser wrote:
> 
> On 5 Jul 2005, at 14:22, Jan Beulich wrote:
> 
> >>GRUB has code for switching back into real mode to do bios calls. We
> >>could take that, plus video.S, and put them in Xen. Then add an info
> >>structure for passing video info up to domain0. It's pretty ugly, but
> >>I think there is no nice solution here.

Well, I'd simply leave that job completely to grub as it has to
deal with that anyway and the multiboot spec have fields to pass
on that info to the booted kernel.  Xen would simply take that
and pass it on to the Dom0 kernel, thats it.  And maybe adjust
it's own row/column counts in case it's vga text mode.

> >> Would we also need vesa/vga
> >>driver code from Linux for setting up font data in some graphics
> >modes?
> >
> >Yes that would clearly be necessary, but perhaps a much more
> >streamlined mechanism would do for XEN.
> 
> If that's the case, I'm sure Gerd can point out the 'moving parts' that 
> we actually need to get basic text output working. I was hoping video.S 
> alone would be sufficient... :-)

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.

In graphics mode you simply have a linear frame buffer and
you'll have to do everything yourself.  Linux has compiled-in
fonts for that.  Quite alot of stuff from drivers/video would
be needed to get that going in xen, but I wouldn't even try to
make xen render text in graphics mode and leave that completely
to the dom0 kernel ...

  Gerd

  reply	other threads:[~2005-07-05 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s2ca350f.097@lucius.provo.novell.com>
2005-07-05 13:28 ` beginnings of allowing more than the basic 80x25 VGAscreen resolution Keir Fraser
2005-07-05 13:42   ` Gerd Knorr [this message]
     [not found] <s2ca4091.019@lucius.provo.novell.com>
2005-07-05 14:47 ` Gerd Knorr
2005-07-05 14:11 Jan Beulich
  -- 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=20050705134250.GA6059@bytesex \
    --to=kraxel@suse.de \
    --cc=JBeulich@novell.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.