-----Original Message----- From: Lorenzo Pieralisi [mailto:lorenzo.pieralisi@arm.com] Sent: 02 February 2022 09:30 To: Shameerali Kolothum Thodi shameerali.kolothum.thodi@huawei.com Cc: Jonathan Cameron jonathan.cameron@huawei.com; joyce.qi@linaro.org; Mike Holmes mike.holmes@linaro.org; james.morse@arm.com; Linuxarm linuxarm@huawei.com; linaro-open-discussions@op-lists.linaro.org Subject: Re: Invitation: Linaro Open Discussions @ Tue 25 Jan 2022 12pm - 1pm (CET) (jonathan.cameron@huawei.com)
On Mon, Jan 31, 2022 at 08:16:19AM +0000, Shameerali Kolothum Thodi wrote:
[...]
RMR progress.
ACPICA / IORT spec issue due to lack of backwards compatibility. AI (LP) to investigate.
Hi Lorenzo,
This is the initial implementation of ACPICA changes w.r.t revision E.c.
https://github.com/shamiali2008/acpica/commit/49ad1b2ec572e3e70557e4
4e2255c497b2639cbe
For now, I am checking the RMR node revision and limit the support to
only >=
Hi Lorenzo,
Please let me know if there is any update on this... We need to get the
ACPCIA changes
in for the kernel support ASAP. If you are Ok with the above patch I can send
a pull request
for the same.
Making the changes. Just to make sure we are on the same page, all we need is, in the RMR specific data, to add the Access Attributes at offset 28, past "Reference to Memory Range Descriptors" so that we keep the "current" layout.
Yes, I think that will do. i.e, move the "Access Attributes" and following "Reserved" bytes, after the "Reference to Memory Range Descriptors".
Something like,
typedef struct acpi_iort_rmr { UINT32 Flags; UINT32 RmrCount; UINT32 RmrOffset; UINT8 AccessAttributes; UINT8 Reserved[3];
} ACPI_IORT_RMR;
Please let me know - a respin is imminent.
Ok.
Thanks, Shameer,