[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb2db2a1-835f-47d0-830d-0dd3785343a9@email.android.com>
Date: Thu, 18 Apr 2013 23:00:27 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Greg KH <gregkh@...uxfoundation.org>,
"Bryan O'Donoghue" <bryan.odonoghue.lkml@...us-software.ie>
CC: matt@...sole-pimps.org, matthew.garrett@...ula.com,
linux-efi@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org, darren.hart@...el.com,
josh@...htriplett.org, mingo@...nel.org, tglx@...utronix.de
Subject: Re: [PATCH] Remove warning in efi_enter_virtual_mode V2
The only real use for command line options is to be able to get users to test something during troubleshooting.
Greg KH <gregkh@...uxfoundation.org> wrote:
>On Wed, Apr 17, 2013 at 11:05:41PM +0100, Bryan O'Donoghue wrote:
>> Some EFI BIOS stores BGRT data in the wrong place and some EFI based
>> BIOS also requires mapping of boot code/data when doing
>> efi_enter_virtual_mode.
>>
>> Current code in efi_enter_virtual_mode maps both EFI_RUNTIME_MEMORY
>and
>> BIOS boot code/data.
>>
>> This patch gives the option to switch off that behavior - if your
>BIOS
>> has neither BGRT - nor bugs that require mapping of EFI boot
>code/data
>
>No, never add new boot options, no users, or distros, know to set them.
>Isn't there some way we can dynamically determine this instead?
>
>thanks,
>
>greg k-h
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists