Attachment 845928 Details for Bug 1048681 – Kernel should use efifb even no option parameter splashimage When using EFI

[patch] Kernel should use efifb even no option parameter splashimage When using EFI

kernel_should_use_efifb.patch (text/plain), 1.34 KB, created by Luan Jianhai on 2014-01-06 05:54:48 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Luan Jianhai

Created: 2014-01-06 05:54:48 UTC

Size: 1.34 KB

patch

obsolete

>Kernel should use efifb even no option parameter splashimage When using EFI
>
>If option parameter splashimage not be set, grub will not initiation graphic 
>backend and kernel will use vesafb driver at EFI platform. We should always
>initiation graphic backend even no splashimage, so kernel will probe correct
>frambuffer driver to use. 
>
>Because grub use command-driver to operation script, no special location to 
>process the graphic. The command boot will always be executed after other 
>command, and only be execute once. So I add judge code and inition graphic 
>code into boot_func to completion the mission.
>
>Signed-off-by: Jason Luan <jianhai.luan@oracle.com>
>---
>diff -Nur grub-0.97.orig/stage2/builtins.c grub-0.97/stage2/builtins.c
>--- grub-0.97.orig/stage2/builtins.c	2013-12-31 01:13:46.888875961 -0500
>+++ grub-0.97/stage2/builtins.c	2013-12-31 01:17:20.702875553 -0500
>@@ -298,6 +298,16 @@
> boot_func (char *arg, int flags)
> {
>   struct term_entry *prev_term = current_term;
>+
>+  /* If graphic don't inition, we should be inition */
>+#ifdef SUPPORT_GRAPHICS
>+  if (!graphics_inited) 
>+    {
>+      graphics_init();
>+      graphics_cls();
>+    }
>+#endif
>+
>   /* Clear the int15 handler if we can boot the kernel successfully.
>      This assumes that the boot code never fails only if KERNEL_TYPE is
>      not KERNEL_TYPE_NONE. Is this assumption is bad?  */

Actions: View | Diff

Attachments on bug 1048681: 845928