From: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] of: document /sys/firmware/fdt
Date: Wed, 28 Jun 2017 14:57:59 -0700 [thread overview]
Message-ID: <59542667.9090702@gmail.com> (raw)
In-Reply-To: <1498686837-5378-1-git-send-email-frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi Rob,
Please ignore this version, Grant replied to your v1 comment, so
I'll spin a v3.
-Frank
On 06/28/17 14:53, frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> From: Frank Rowand <frank.rowand-7U/KSKJipcs@public.gmane.org>
>
> Add ABI documentation for /sys/firmware/fdt
>
> Change obsolete contact for /sys/firmware/devicetree/* to mail list
>
> Signed-off-by: Frank Rowand <frank.rowand-7U/KSKJipcs@public.gmane.org>
> ---
>
> changes from v1:
> - Remove obsolete email address as contact for /sys/firmware/devicetree/*
> - For newly documented /sys/firmware/fdt do not include any individual
> email for Contact (only provide email list)
>
> Documentation/ABI/testing/sysfs-firmware-ofw | 27 ++++++++++++++++++++++++++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-firmware-ofw b/Documentation/ABI/testing/sysfs-firmware-ofw
> index f562b188e71d..30a6b3621828 100644
> --- a/Documentation/ABI/testing/sysfs-firmware-ofw
> +++ b/Documentation/ABI/testing/sysfs-firmware-ofw
> @@ -1,6 +1,6 @@
> What: /sys/firmware/devicetree/*
> Date: November 2013
> -Contact: Grant Likely <grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> +Contact: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> Description:
> When using OpenFirmware or a Flattened Device Tree to enumerate
> hardware, the device tree structure will be exposed in this
> @@ -26,3 +26,28 @@ Description:
> name plus address). Properties are represented as files
> in the directory. The contents of each file is the exact
> binary data from the device tree.
> +
> +What: /sys/firmware/fdt
> +Date: February 2015
> +KernelVersion: 3.19
> +Contact: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> +Description:
> + Exports the FDT blob that was passed to the kernel by
> + the bootloader. This allows userland applications such
> + as kexec to access the raw binary. This blob is also
> + useful when debugging since it contains any changes
> + made to the blob by the bootloader.
> +
> + The fact that this node does not reside under
> + /sys/firmware/device-tree is deliberate: FDT is also used
> + on arm64 UEFI/ACPI systems to communicate just the UEFI
> + and ACPI entry points, but the FDT is never unflattened
> + and used to configure the system.
> +
> + A CRC32 checksum is calculated over the entire FDT
> + blob, and verified at late_initcall time. The sysfs
> + entry is instantiated only if the checksum is valid,
> + i.e., if the FDT blob has not been modified in the mean
> + time. Otherwise, a warning is printed.
> +Users: kexec, debugging
> +
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] of: document /sys/firmware/fdt
Date: Wed, 28 Jun 2017 14:57:59 -0700 [thread overview]
Message-ID: <59542667.9090702@gmail.com> (raw)
In-Reply-To: <1498686837-5378-1-git-send-email-frowand.list@gmail.com>
Hi Rob,
Please ignore this version, Grant replied to your v1 comment, so
I'll spin a v3.
-Frank
On 06/28/17 14:53, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> Add ABI documentation for /sys/firmware/fdt
>
> Change obsolete contact for /sys/firmware/devicetree/* to mail list
>
> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
> ---
>
> changes from v1:
> - Remove obsolete email address as contact for /sys/firmware/devicetree/*
> - For newly documented /sys/firmware/fdt do not include any individual
> email for Contact (only provide email list)
>
> Documentation/ABI/testing/sysfs-firmware-ofw | 27 ++++++++++++++++++++++++++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-firmware-ofw b/Documentation/ABI/testing/sysfs-firmware-ofw
> index f562b188e71d..30a6b3621828 100644
> --- a/Documentation/ABI/testing/sysfs-firmware-ofw
> +++ b/Documentation/ABI/testing/sysfs-firmware-ofw
> @@ -1,6 +1,6 @@
> What: /sys/firmware/devicetree/*
> Date: November 2013
> -Contact: Grant Likely <grant.likely@linaro.org>
> +Contact: devicetree@vger.kernel.org
> Description:
> When using OpenFirmware or a Flattened Device Tree to enumerate
> hardware, the device tree structure will be exposed in this
> @@ -26,3 +26,28 @@ Description:
> name plus address). Properties are represented as files
> in the directory. The contents of each file is the exact
> binary data from the device tree.
> +
> +What: /sys/firmware/fdt
> +Date: February 2015
> +KernelVersion: 3.19
> +Contact: devicetree@vger.kernel.org
> +Description:
> + Exports the FDT blob that was passed to the kernel by
> + the bootloader. This allows userland applications such
> + as kexec to access the raw binary. This blob is also
> + useful when debugging since it contains any changes
> + made to the blob by the bootloader.
> +
> + The fact that this node does not reside under
> + /sys/firmware/device-tree is deliberate: FDT is also used
> + on arm64 UEFI/ACPI systems to communicate just the UEFI
> + and ACPI entry points, but the FDT is never unflattened
> + and used to configure the system.
> +
> + A CRC32 checksum is calculated over the entire FDT
> + blob, and verified at late_initcall time. The sysfs
> + entry is instantiated only if the checksum is valid,
> + i.e., if the FDT blob has not been modified in the mean
> + time. Otherwise, a warning is printed.
> +Users: kexec, debugging
> +
>
next prev parent reply other threads:[~2017-06-28 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 21:53 [PATCH v2] of: document /sys/firmware/fdt frowand.list-Re5JQEeQqe8AvxtiuMwx3w
2017-06-28 21:53 ` frowand.list
[not found] ` <1498686837-5378-1-git-send-email-frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-28 21:57 ` Frank Rowand [this message]
2017-06-28 21:57 ` Frank Rowand
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=59542667.9090702@gmail.com \
--to=frowand.list-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.