On 19/04/13 06:58, Greg KH wrote:
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
Nope, just a vehicle for experiments.
Greg KH wrote:
>On Thu, Apr 18, 2013 at 11:00:27PM -0700, H. Peter Anvin wrote:
>> The only real use for command line options is to be able to get users
>> to test something during troubleshooting.
>
>Ok, but the option shouldn't be used to "solve" the
On Thu, Apr 18, 2013 at 11:00:27PM -0700, H. Peter Anvin wrote:
> The only real use for command line options is to be able to get users
> to test something during troubleshooting.
Ok, but the option shouldn't be used to "solve" the problem.
greg k-h
--
To unsubscribe from this list: send the
The only real use for command line options is to be able to get users to test
something during troubleshooting.
Greg KH 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
The only real use for command line options is to be able to get users to test
something during troubleshooting.
Greg KH gre...@linuxfoundation.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
On Thu, Apr 18, 2013 at 11:00:27PM -0700, H. Peter Anvin wrote:
The only real use for command line options is to be able to get users
to test something during troubleshooting.
Ok, but the option shouldn't be used to solve the problem.
greg k-h
--
To unsubscribe from this list: send the line
Nope, just a vehicle for experiments.
Greg KH gre...@linuxfoundation.org wrote:
On Thu, Apr 18, 2013 at 11:00:27PM -0700, H. Peter Anvin wrote:
The only real use for command line options is to be able to get users
to test something during troubleshooting.
Ok, but the option shouldn't be used
On 19/04/13 06:58, Greg KH wrote:
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
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
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
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
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
12 matches
Mail list logo
