All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert Mortimer" <rmortimer@bluechiptechnology.co.uk>
To: Andrew Liu <liushengping@tsinghua.org.cn>,
	xen-devel@lists.xensource.com, xen-tools@lists.xensource.com
Subject: RE: [Xen-tools] xen doesn't support "Framebuffer consolesupport"properly
Date: Mon, 24 Apr 2006 15:54:44 +0100	[thread overview]
Message-ID: <000c01c667af$05f974d0$5f00000a@rmortimer> (raw)
In-Reply-To: <345887254.15493@eyou.net>

Is this a DomU or a Dom0 kernel?

>From my scant understanding the following is true:-

only Dom0 gets to see the true hardware still runs above the hypervisor

If frambuffer mode requires direct access to hardware then it may not work.
I am not positive but does frambuffer involves direct writing to video
memory

DomU gets to see idealized Xen hardware and presumably uses some sort of Xen
video driver.

DomU does no direct rendering to screen instead it uses VNC

I may however be so so wrong as I am a bit new to this

Robert

> -----Original Message-----
>
> When I turn on the "Framebuffer console support" in compiling kernel,
> after system startup, the console doesn't work properly and the kernel
> parameter( for example: vga=719) doesn't do any effect on kernel.
>
> who can help me ?
> thanks in advance!
> Andrew Liu
>
>
>
> _______________________________________________
> Xen-tools mailing list
> Xen-tools@lists.xensource.com
> http://lists.xensource.com/xen-tools
>

  reply	other threads:[~2006-04-24 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24 22:15 xen doesn't support "Framebuffer console support"properly Andrew Liu
2006-04-24 22:15 ` Andrew Liu
2006-04-24 14:54   ` Robert Mortimer [this message]
2006-04-25  9:31     ` RE: [Xen-tools] xen doesn't support "Framebuffer consolesupport"properly Mathieu Ropert

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='000c01c667af$05f974d0$5f00000a@rmortimer' \
    --to=rmortimer@bluechiptechnology.co.uk \
    --cc=liushengping@tsinghua.org.cn \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-tools@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.