ok，thanks：）
Joyce
在 2022年3月18日，上午12:43，Jonathan Cameron Jonathan.Cameron@huawei.com 写道：
On Thu, 17 Mar 2022 16:17:33 +0000 Lorenzo Pieralisi via Linaro-open-discussions linaro-open-discussions@op-lists.linaro.org wrote:
On Wed, Mar 16, 2022 at 09:34:49PM +0800, Joyce Qi wrote:
Hi Jonathan,Lorenzo, all
What's the topic we want to discuss next week？
I don't have any specific topic, I think though we can sync-up on a couple of items (eg PCI DOE, RMR IORT) just as a sync-up point even if it is quick.
What do you guys think ?
Sure a quick sync call seems like a good idea to me.
Jonathan
Thanks, Lorenzo
Thanks:) Joyce
在 2022年2月18日，下午6:22，joyce.qi@linaro.org 写道：
Hi Jonathan，
Thanks a lot for the feedback：）
Will cancel this month’s meeting.
Thanks Joyce
-------- 原始邮件 -------- 发件人： Jonathan Cameron Jonathan.Cameron@Huawei.com 日期： 2022年2月18日周五傍晚5:22 收件人： Joyce Qi joyce.qi@linaro.org 抄送： Lorenzo Pieralisi lorenzo.pieralisi@arm.com, Shameerali Kolothum Thodi shameerali.kolothum.thodi@huawei.com, Mike Holmes < mike.holmes@linaro.org>, james.morse@arm.com, Linuxarm <linuxarm@huawei.com
, linaro-open-discussions@op-lists.linaro.org
主题： Re: Invitation: Linaro Open Discussions @ Tue 25 Jan 2022 12pm - 1pm (CET) (jonathan.cameron@huawei.com)
On Fri, 18 Feb 2022 07:07:18 +0800 Joyce Qi <joyce.qi@linaro.org> wrote:Hi Jonathan, Lorenzo,all,
Any topic we want to discuss next Thursday?
Thanks:) Joyce
Hi Joyce, There was another thread on the open discussions mailing list in which both Lorenzo and I expressed that neither ARM nor Huawei have anything to discuss currently. So I suggests let's skip this meeting and all get the time back this month. Thanks, Jonathan在 2022年2月15日，下午8:22，Lorenzo Pieralisi <
lorenzo.pieralisi@arm.com> 写道：On Wed, Feb 02, 2022 at 10:19:42AM +0000, Shameerali Kolothum Thodi
wrote:> -----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;
Linuxarmlinaro-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.49ad1b2ec572e3e70557e4>>> 4e2255c497b2639cbe >>> >>> For now, I am checking the RMR node revision and limit the
support to> only >= >>> 2. >> >> 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.
FYI, IORT Issue E.d has been published, we should be able to
completethe upstreaming.
Thanks, Lorenzo