All of lore.kernel.org
 help / color / mirror / Atom feed
From: "qiang.wang" <qiang.wang@cs2c.com.cn>
To: xen-devel@lists.xensource.com
Subject: about framebuffer support in xen domain 0
Date: Thu, 08 Mar 2007 16:09:49 +0800	[thread overview]
Message-ID: <1173341389.6491.15.camel@localhost.localdomain> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1979 bytes --]

Hi, list,
I have a problem after moving the bootsplash patch into the domain 0
kernel. It doesn't work.
After digging the source code, I found that the kernel data "struct
screen_info screen_info" is set to a specific value in
arch/i386/kernel/setup-xen.c. And the info->video_type is
XEN_VGATYPE_TEXT_MODE_3, so it doesn't support framebuffer in domain 0
and the bootsplash either.

void __init setup_arch(char **cmdline_p)
{
...

if (is_initial_xendomain()) {
                /* This is drawn from a dump from vgacon:startup in
                 * standard Linux. */
                screen_info.orig_video_mode = 3;
                screen_info.orig_video_isVGA = 1;
                screen_info.orig_video_lines = 25;
                screen_info.orig_video_cols = 80;
                screen_info.orig_video_ega_bx = 3;
                screen_info.orig_video_points = 16;
                screen_info.orig_y = screen_info.orig_video_lines - 1;
                if (xen_start_info->console.dom0.info_size >=
                    sizeof(struct dom0_vga_console_info)) {
                        //const struct dom0_vga_console_info *info =
                        struct dom0_vga_console_info *info =
                                (struct dom0_vga_console_info *)(
                                        (char *)xen_start_info +
                                        xen_start_info-
>console.dom0.info_off);
                        // wangqiang
                        //info->video_type = XEN_VGATYPE_VESA_LFB;
                        dom0_init_screen_info(info);
                }
                xen_start_info->console.domU.mfn = 0;
                xen_start_info->console.domU.evtchn = 0;
        } else
                screen_info.orig_video_isVGA = 0;
...
}


it seems that the initial dom0_vga_console_info is set by
fill_console_start_info() in xen/drivers/video/vga.c
My question is that is there a particular reason to assign the
dom0_vga_console_info a specific value?

[-- Attachment #1.2: Type: text/html, Size: 4694 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

             reply	other threads:[~2007-03-08  8:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  8:09 qiang.wang [this message]
2007-03-08  8:17 ` about framebuffer support in xen domain 0 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=1173341389.6491.15.camel@localhost.localdomain \
    --to=qiang.wang@cs2c.com.cn \
    --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.