Re: [PATCH v2 30/32] fdt: Allow the devicetree to come from a bloblist
Hi Simon,
On Thu, 21 Sept 2023 at 04:58, Simon Glass sjg@chromium.org wrote:
Standard passage provides for a bloblist to be passed from one firmware phase to the next. That can be used to pass the devicetree along as well. Add an option to support this.
Tests for this will be added as part of the Universal Payload work.
Signed-off-by: Simon Glass sjg@chromium.org
Changes in v2:
- No changes as it still seems unclear what should be done
[...]
diff --git a/include/bloblist.h b/include/bloblist.h index 080cc46a1266..e16d122f4fb1 100644 --- a/include/bloblist.h +++ b/include/bloblist.h @@ -103,6 +103,11 @@ enum bloblist_tag_t { BLOBLISTT_ACPI_TABLES = 0x104, /* ACPI tables for x86 */ BLOBLISTT_SMBIOS_TABLES = 0x105, /* SMBIOS tables for x86 */ BLOBLISTT_VBOOT_CTX = 0x106, /* Chromium OS verified boot context */
- /*
- Devicetree for use by firmware. On some platforms this is passed to
- the OS also
- */
- BLOBLISTT_CONTROL_FDT = 0x107,
Shall we re-define all the `BLOBLISTT_` tags according to the firmware handoff spec v0.9? According to the latest discussion (in https://github.com/FirmwareHandoff/firmware_handoff/pull/19) It is preferred that generic ones to start from `0`, and Arm specific ones starts from `0x100`. In this case, the FDT should be re-defined as `1` and other existing non-arm ones (e.g. for x86 or Chromium OS) should have their placeholder before `0xff_f000`, while generic ones (e.g. for TPM) should be placed somewhere between `0` and `0x100`.
[...]
Regards, Raymond
Hi Raymond,
On Fri, 20 Oct 2023 at 15:15, Raymond Mao raymond.mao@linaro.org wrote:
Hi Simon,
On Thu, 21 Sept 2023 at 04:58, Simon Glass sjg@chromium.org wrote:
Standard passage provides for a bloblist to be passed from one firmware phase to the next. That can be used to pass the devicetree along as well. Add an option to support this.
Tests for this will be added as part of the Universal Payload work.
Signed-off-by: Simon Glass sjg@chromium.org
Changes in v2:
- No changes as it still seems unclear what should be done
[...]
diff --git a/include/bloblist.h b/include/bloblist.h index 080cc46a1266..e16d122f4fb1 100644 --- a/include/bloblist.h +++ b/include/bloblist.h @@ -103,6 +103,11 @@ enum bloblist_tag_t { BLOBLISTT_ACPI_TABLES = 0x104, /* ACPI tables for x86 */ BLOBLISTT_SMBIOS_TABLES = 0x105, /* SMBIOS tables for x86 */ BLOBLISTT_VBOOT_CTX = 0x106, /* Chromium OS verified boot context */
- /*
- Devicetree for use by firmware. On some platforms this is passed to
- the OS also
- */
- BLOBLISTT_CONTROL_FDT = 0x107,
Shall we re-define all the `BLOBLISTT_` tags according to the firmware handoff spec v0.9? According to the latest discussion (in https://github.com/FirmwareHandoff/firmware_handoff/pull/19) It is preferred that generic ones to start from `0`, and Arm specific ones starts from `0x100`. In this case, the FDT should be re-defined as `1` and other existing non-arm ones (e.g. for x86 or Chromium OS) should have their placeholder before `0xff_f000`, while generic ones (e.g. for TPM) should be placed somewhere between `0` and `0x100`.
[...]
Sure, if you like. I'm a little unclear when that stuff will land. We can always update the tag numbering along with the format changes.
Regards, Simon
participants (2)
-
Raymond Mao -
Simon Glass