grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: leif.lindholm@linaro.org
Subject: Re: [PATCH 1/2] arm64: Move firmware fdt search into global function
Date: Sat, 12 Nov 2016 12:03:33 +0300	[thread overview]
Message-ID: <77c2cdca-3a1c-f5be-c60e-00a8051d047d@gmail.com> (raw)
In-Reply-To: <1456701744-202295-1-git-send-email-agraf@suse.de>

29.02.2016 02:22, Alexander Graf пишет:
> Searching for a device tree that EFI passes to us via configuration tables
> is nothing architecture specific. Move it into generic code.
> 
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
>  grub-core/kern/efi/init.c    | 22 ++++++++++++++++++++++
>  grub-core/loader/arm64/fdt.c | 24 +-----------------------
>  include/grub/efi/efi.h       |  2 ++
>  3 files changed, 25 insertions(+), 23 deletions(-)
> 
> diff --git a/grub-core/kern/efi/init.c b/grub-core/kern/efi/init.c
> index e9c85de..fb90ecd 100644
> --- a/grub-core/kern/efi/init.c
> +++ b/grub-core/kern/efi/init.c
> @@ -72,6 +72,28 @@ grub_machine_get_bootlocation (char **device, char **path)
>      }
>  }
>  
> +void *
> +grub_efi_get_firmware_fdt (void)
> +{
> +  grub_efi_configuration_table_t *tables;
> +  grub_efi_guid_t fdt_guid = GRUB_EFI_DEVICE_TREE_GUID;
> +  void *firmware_fdt = NULL;
> +  unsigned int i;
> +
> +  /* Look for FDT in UEFI config tables. */
> +  tables = grub_efi_system_table->configuration_table;
> +
> +  for (i = 0; i < grub_efi_system_table->num_table_entries; i++)
> +    if (grub_memcmp (&tables[i].vendor_guid, &fdt_guid, sizeof (fdt_guid)) == 0)
> +      {
> +	firmware_fdt = tables[i].vendor_table;
> +	grub_dprintf ("linux", "found registered FDT @ %p\n", firmware_fdt);
> +	break;
> +      }
> +
> +  return firmware_fdt;
> +}
> +

Is it relevant for x86? I cannot even find anything related to FDT or
"device tree" in UEFI spec, it falls under vendor extensions. What other
use it has except in Linux loader?

I really fail to see why it should be moved into core until at least one
more non-trivial caller is present.

>  void
>  grub_efi_fini (void)
>  {
> diff --git a/grub-core/loader/arm64/fdt.c b/grub-core/loader/arm64/fdt.c
> index 5202c14..db49cf6 100644
> --- a/grub-core/loader/arm64/fdt.c
> +++ b/grub-core/loader/arm64/fdt.c
> @@ -28,28 +28,6 @@
>  static void *loaded_fdt;
>  static void *fdt;
>  
> -static void *
> -get_firmware_fdt (void)
> -{
> -  grub_efi_configuration_table_t *tables;
> -  grub_efi_guid_t fdt_guid = GRUB_EFI_DEVICE_TREE_GUID;
> -  void *firmware_fdt = NULL;
> -  unsigned int i;
> -
> -  /* Look for FDT in UEFI config tables. */
> -  tables = grub_efi_system_table->configuration_table;
> -
> -  for (i = 0; i < grub_efi_system_table->num_table_entries; i++)
> -    if (grub_memcmp (&tables[i].vendor_guid, &fdt_guid, sizeof (fdt_guid)) == 0)
> -      {
> -	firmware_fdt = tables[i].vendor_table;
> -	grub_dprintf ("linux", "found registered FDT @ %p\n", firmware_fdt);
> -	break;
> -      }
> -
> -  return firmware_fdt;
> -}
> -
>  void *
>  grub_fdt_load (grub_size_t additional_size)
>  {
> @@ -65,7 +43,7 @@ grub_fdt_load (grub_size_t additional_size)
>    if (loaded_fdt)
>      raw_fdt = loaded_fdt;
>    else
> -    raw_fdt = get_firmware_fdt();
> +    raw_fdt = grub_efi_get_firmware_fdt();
>  
>    size =
>      raw_fdt ? grub_fdt_get_totalsize (raw_fdt) : GRUB_FDT_EMPTY_TREE_SZ;
> diff --git a/include/grub/efi/efi.h b/include/grub/efi/efi.h
> index 0e6fd86..2acf85e 100644
> --- a/include/grub/efi/efi.h
> +++ b/include/grub/efi/efi.h
> @@ -81,6 +81,8 @@ extern void (*EXPORT_VAR(grub_efi_net_config)) (grub_efi_handle_t hnd,
>  						char **device,
>  						char **path);
>  
> +void *EXPORT_FUNC(grub_efi_get_firmware_fdt)(void);
> +
>  grub_addr_t grub_efi_modules_addr (void);
>  
>  void grub_efi_mm_init (void);
> 



  parent reply	other threads:[~2016-11-12  9:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-28 23:22 [PATCH 1/2] arm64: Move firmware fdt search into global function Alexander Graf
2016-02-28 23:22 ` [PATCH 2/2] arm efi: Use fdt from firmware when available Alexander Graf
2016-03-10 20:00   ` Vladimir 'phcoder' Serbinenko
2016-03-13 14:44     ` Leif Lindholm
2016-11-10 12:27   ` Daniel Kiper
2016-11-12  9:03 ` Andrei Borzenkov [this message]
2016-11-15 21:00   ` [PATCH 1/2] arm64: Move firmware fdt search into global function Daniel Kiper
2016-11-15 21:07     ` Alexander Graf
2016-11-16 10:28       ` Daniel Kiper
2016-11-16 10:33         ` Alexander Graf
2016-11-16 11:05           ` Daniel Kiper

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=77c2cdca-3a1c-f5be-c60e-00a8051d047d@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=leif.lindholm@linaro.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;
as well as URLs for NNTP newsgroup(s).