public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Prabhakar Kushwaha <prabhakar.pkin@gmail.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [edk2-devel] How /sys/firmware/fdt getting created
Date: Wed, 30 Oct 2019 08:12:57 +0100	[thread overview]
Message-ID: <CAKv+Gu8oUfSfMLW17QOwBCrrn+3AggHND6b0KZWfB=Npo9d8Hw@mail.gmail.com> (raw)
In-Reply-To: <ae74bb79-a68e-a319-f61c-5b93fd70ae59@gmail.com>

On Tue, 29 Oct 2019 at 18:17, Prabhakar Kushwaha
<prabhakar.pkin@gmail.com> wrote:
>
> Hi All,
>
> I am working on Ubuntu-18.04 with UEFI on ARM64(64 bit) platform. The
> UEFI used is having ACPI tables.
>
> I am trying to understand where and how /sys/firmware/fdt is getting
> created. is it created by UEFI or grub and passed to Linux?
>

Neither. It is created by Linux itself.



> below is the dts format of /sys/firmware/fdt.
>
> /dts-v1/;
>
> / {
>
>         chosen {
>                 linux,uefi-mmap-desc-ver = <0x1>;
>                 linux,uefi-mmap-desc-size = <0x30>;
>                 linux,uefi-mmap-size = <0xcc0>;
>                 linux,uefi-mmap-start = <0x0 0xeda13018>;
>                 linux,uefi-system-table = <0x0 0xfafd0018>;
>                 bootargs = "BOOT_IMAGE=/boot/vmlinuz-5.4.0-rc4+
> root=UUID=798a858c-4f20-4b99-aa40-99bff9394093 ro crashkernel=2G
> console=ttyAMA0";
>                 linux,initrd-end = <0x0 0xeb381a34>;
>                 linux,initrd-start = <0x0 0xdd5f5000>;
>         };
> };
>
> also, under what scenario/config fields is getting added fdt.
>         #size-cells = <0x02>;
>         #address-cells = <0x02>;
>
> --prabhakar (pk)
>
> 
>

  reply	other threads:[~2019-10-30  7:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 14:32 How /sys/firmware/fdt getting created prabhakar.pkin
2019-10-30  7:12 ` Ard Biesheuvel [this message]
2019-10-30  7:36   ` [edk2-devel] " Prabhakar Kushwaha
2019-10-30  7:44     ` Ard Biesheuvel
2019-10-30  8:16       ` Prabhakar Kushwaha
2019-10-31 10:07         ` Laszlo Ersek
2019-10-31 12:16           ` Leif Lindholm
2019-10-31 18:55             ` dann frazier
     [not found]             ` <15D2D0302F8A1888.21389@groups.io>
2019-10-31 20:34               ` dann frazier
2019-11-01  4:47                 ` Prabhakar Kushwaha
2019-11-01 16:25                   ` dann frazier
2019-11-04  4:11                     ` Prabhakar Kushwaha
2019-10-31 20:29         ` Bhupesh Sharma
2019-11-01  4:51           ` Prabhakar Kushwaha
2019-11-01  5:46             ` Bhupesh Sharma

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-list 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='CAKv+Gu8oUfSfMLW17QOwBCrrn+3AggHND6b0KZWfB=Npo9d8Hw@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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