On 18.12.2014 19:06, Fu Wei wrote:
>        Reason: (1)we don't need the check, actually
>                (2)it is a prerequisite for multiboot support
> 
That one is problematic. Normally execution of any kernel-loading
commands like linux resets the boot context. Exceptions are drivemap,
sendkey, acpi and memory map commands, somewhat unfortunately. I'm on
the edge as to whether we should extend this behaviour to other commands.
> Signed-off-by: Fu Wei <fu....@linaro.org>
> Reviewed-by: Leif Lindholm <leif.lindh...@linaro.org>
> ---
>  grub-core/loader/arm64/linux.c | 7 -------
>  1 file changed, 7 deletions(-)
> 
> diff --git a/grub-core/loader/arm64/linux.c b/grub-core/loader/arm64/linux.c
> index 987f5b9..e9e9a29 100644
> --- a/grub-core/loader/arm64/linux.c
> +++ b/grub-core/loader/arm64/linux.c
> @@ -185,13 +185,6 @@ grub_cmd_devicetree (grub_command_t cmd __attribute__ 
> ((unused)),
>    void *blob = NULL;
>    int size;
>  
> -  if (!loaded)
> -    {
> -      grub_error (GRUB_ERR_BAD_ARGUMENT,
> -               N_("you need to load the kernel first"));
> -      return GRUB_ERR_BAD_OS;
> -    }
> -
>    if (argc != 1)
>      return grub_error (GRUB_ERR_BAD_ARGUMENT, N_("filename expected"));
>  
> 


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Reply via email to