public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Maly <bmaly@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix DMI for EFI
Date: Sat, 28 Feb 2009 21:40:23 -0500	[thread overview]
Message-ID: <49A9F597.4010601@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 304 bytes --]

Updated patch. Might be good for someone who runs VMware to verify things still work though.
Looks right now I think.


Brian


>This init_hypervisor comment looks important, no? Possibly it needs
>to be moved after the new placement? Doesn't look like the probe_roms
>will be an issue.

>regards, Kyle


[-- Attachment #2: fix-DMI-for-EFI-2.6.29.patch --]
[-- Type: text/x-patch, Size: 941 bytes --]

--- a/arch/x86/kernel/setup.c	2009-02-08 15:37:27.000000000 -0500
+++ b/arch/x86/kernel/setup.c	2009-03-01 02:27:45.000000000 -0500
@@ -770,16 +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.
-	 */
-	init_hypervisor(&boot_cpu_data);
-
 #ifdef CONFIG_X86_32
 	probe_roms();
 #endif
@@ -792,6 +782,16 @@ void __init setup_arch(char **cmdline_p)
 	if (efi_enabled)
 		efi_init();
 
+	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.
+	 */
+	init_hypervisor(&boot_cpu_data);
+
 #ifdef CONFIG_X86_32
 	if (ppro_with_ram_bug()) {
 		e820_update_range(0x70000000ULL, 0x40000ULL, E820_RAM,

             reply	other threads:[~2009-03-01  2:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01  2:40 Brian Maly [this message]
2009-03-01  2:56 ` [PATCH] fix DMI for EFI 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
2009-03-04 17:57     ` [tip:x86/urgent] x86: fix DMI on EFI Brian Maly
  -- strict thread matches above, loose matches on Subject: below --
2009-03-01  1:33 [PATCH] fix DMI for EFI Brian Maly
2009-03-01  2:01 ` Kyle McMartin

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=49A9F597.4010601@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