From: Tang Liang <liang.tang@oracle.com>
To: mjg59@srcf.ucam.org, xen-devel@lists.xensource.com,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
konrad.wilk@oracle.com
Cc: liang.tang@oracle.com
Subject: [PATCH 5/5] Xen vga: add the xen efi video mode support
Date: Thu, 9 Feb 2012 11:33:51 +0800 [thread overview]
Message-ID: <1328758431-24339-1-git-send-email-liang.tang@oracle.com> (raw)
In-Reply-To: <1328758250-23989-1-git-send-email-liang.tang@oracle.com>
In order to add xen efi video support, it is required to add xen-efi's new
video type(XEN_VGATYPE_EFI_LFB) case handler in the function xen_init_vga
and set the video type to VIDEO_TYPE_EFI to enable efi video mode.
Signed-off-by: Tang Liang <liang.tang@oracle.com>
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
---
arch/x86/xen/vga.c | 7 +++++++
include/xen/interface/xen.h | 1 +
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/arch/x86/xen/vga.c b/arch/x86/xen/vga.c
index 1cd7f4d..6722e37 100644
--- a/arch/x86/xen/vga.c
+++ b/arch/x86/xen/vga.c
@@ -35,6 +35,7 @@ void __init xen_init_vga(const struct dom0_vga_console_info *info, size_t size)
info->u.text_mode_3.font_height;
break;
+ case XEN_VGATYPE_EFI_LFB:
case XEN_VGATYPE_VESA_LFB:
if (size < offsetof(struct dom0_vga_console_info,
u.vesa_lfb.gbl_caps))
@@ -54,6 +55,12 @@ void __init xen_init_vga(const struct dom0_vga_console_info *info, size_t size)
screen_info->blue_pos = info->u.vesa_lfb.blue_pos;
screen_info->rsvd_size = info->u.vesa_lfb.rsvd_size;
screen_info->rsvd_pos = info->u.vesa_lfb.rsvd_pos;
+
+ if (info->video_type == XEN_VGATYPE_EFI_LFB) {
+ screen_info->orig_video_isVGA = VIDEO_TYPE_EFI;
+ break;
+ }
+
if (size >= offsetof(struct dom0_vga_console_info,
u.vesa_lfb.gbl_caps)
+ sizeof(info->u.vesa_lfb.gbl_caps))
diff --git a/include/xen/interface/xen.h b/include/xen/interface/xen.h
index a890804..c84ba71 100644
--- a/include/xen/interface/xen.h
+++ b/include/xen/interface/xen.h
@@ -454,6 +454,7 @@ struct dom0_vga_console_info {
uint8_t video_type;
#define XEN_VGATYPE_TEXT_MODE_3 0x03
#define XEN_VGATYPE_VESA_LFB 0x23
+#define XEN_VGATYPE_EFI_LFB 0x70
union {
struct {
--
1.7.7.5
prev parent reply other threads:[~2012-02-09 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 3:30 [PATCH 0/5] xen: patches for supporting efi Tang Liang
2012-02-09 3:32 ` [PATCH 1/5] EFI: Provide registration for efi_init.. etc efi public function Tang Liang
2012-02-09 16:01 ` Konrad Rzeszutek Wilk
2012-02-10 16:58 ` [Xen-devel] " Jan Beulich
2012-02-09 3:32 ` [PATCH 2/5] EFI: seperate get efi table info code to single function Tang Liang
2012-02-09 3:33 ` [PATCH 3/5] EFI: add efi driver for Xen efi Tang Liang
2012-02-09 19:47 ` Matthew Garrett
2012-02-10 7:24 ` liang tang
2012-02-10 13:45 ` Matthew Garrett
2012-02-10 15:49 ` [Xen-devel] " Jan Beulich
2012-02-09 3:33 ` [PATCH 4/5] Xen efi: Add xen efi enabled detect Tang Liang
2012-02-09 3:33 ` Tang Liang [this message]
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=1328758431-24339-1-git-send-email-liang.tang@oracle.com \
--to=liang.tang@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).