Date: Wed, 4 Mar 2009 12:00:22 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Brian Maly <bmaly@redhat.com>
Cc: Yinghai Lu <yinghai@kernel.org>, linux-kernel@vger.kernel.org,
       ying.huang@intel.com
Subject: Re: [PATCH] fix DMI for EFI
Message-ID: <20090304110022.GB18165@elte.hu>
References: <49A9F597.4010601@redhat.com> <86802c440902281856h1dc950e7me8568cd5dca59da9@mail.gmail.com> <49ADEDA3.1030406@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49ADEDA3.1030406@redhat.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1145
Lines: 39


* Brian Maly <bmaly@redhat.com> wrote:

> New patch. Its easier I think to just move efi_init() earlier. Seems  
> less risky and less drawbacks.
>
> Signed-off-by: Brian Maly <bmaly@redhat>
>
>
> setup.c |    5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
>

> --- a/arch/x86/kernel/setup.c	2009-03-03 21:24:53.000000000 -0500
> +++ b/arch/x86/kernel/setup.c	2009-03-03 21:26:00.000000000 -0500
> @@ -770,6 +770,9 @@ void __init setup_arch(char **cmdline_p)
>  
>  	finish_e820_parsing();
>  
> +	if (efi_enabled)
> +		efi_init();
> +
>  	dmi_scan_machine();

Hm, could we ever find ourselves in the positition of having to 
access the DMI strings table in the EFI init code, to implement 
a quirk? I think that's quite plausible.

OTOH, with some DMI quirks in EFI tables it's a bit of a chicken 
and egg problem. Can DMI strings ever be outside of EFI tables 
on EFI systems?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/