From: Brian Maly <bmaly@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] fix DMI for EFI
Date: Sat, 28 Feb 2009 20:33:15 -0500 [thread overview]
Message-ID: <49A9E5DB.8070203@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
DMI tables are loaded by EFI, so the dmi calls must happen after
efi_init() and not before. Currently Apple hardware uses DMI to
determine the framebuffer mappings for efifb. Without DMI working you
also have no video on MacBook Pro. This patch resolves the DMI issue for
EFI hardware (DMI is now properly detected at boot), and additionally
efifb now loads on Apple hardware (i.e. video works).
Signed-off-by: Brian Maly <bmaly@redhat>
setup.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
[-- Attachment #2: fix-DMI-for-EFI-2.6.29.patch --]
[-- Type: text/x-patch, Size: 686 bytes --]
--- a/arch/x86/kernel/setup.c 2009-02-08 15:37:27.000000000 -0500
+++ b/arch/x86/kernel/setup.c 2009-03-01 01:09:41.000000000 -0500
@@ -770,10 +770,6 @@ void __init setup_arch(char **cmdline_p)
finish_e820_parsing();
- dmi_scan_machine();
-
- dmi_check_system(bad_bios_dmi_table);
-
/*
* VMware detection requires dmi to be available, so this
* needs to be done after dmi_scan_machine, for the BP.
@@ -792,6 +788,10 @@ void __init setup_arch(char **cmdline_p)
if (efi_enabled)
efi_init();
+ dmi_scan_machine();
+
+ dmi_check_system(bad_bios_dmi_table);
+
#ifdef CONFIG_X86_32
if (ppro_with_ram_bug()) {
e820_update_range(0x70000000ULL, 0x40000ULL, E820_RAM,
next reply other threads:[~2009-03-01 1:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 1:33 Brian Maly [this message]
2009-03-01 2:01 ` [PATCH] fix DMI for EFI Kyle McMartin
-- strict thread matches above, loose matches on Subject: below --
2009-03-01 2:40 Brian Maly
2009-03-01 2:56 ` Yinghai Lu
2009-03-01 3:11 ` Brian Maly
2009-03-01 3:25 ` Yinghai Lu
2009-03-01 3:58 ` Brian Maly
2009-03-04 2:55 ` Brian Maly
2009-03-04 11:00 ` Ingo Molnar
2009-03-04 15:03 ` Brian Maly
2009-03-04 17:54 ` Ingo Molnar
2009-03-04 18:00 ` Brian Maly
2009-03-04 18:02 ` Ingo Molnar
2009-03-05 1:33 ` Huang Ying
2009-03-05 10:05 ` Ingo Molnar
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=49A9E5DB.8070203@redhat.com \
--to=bmaly@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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