From: "Sean Rhodes" <sean@starlabs.systems>
To: "Wu, Hao A" <hao.a.wu@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/FaultTolerantWriteDxe: Don't check for address alignment
Date: Mon, 16 May 2022 08:53:59 +0100 [thread overview]
Message-ID: <CABtds-2gL7uU_wCCTpYLXVySurMaK61Rv5bgk85LxnDbPj1LXw@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB402504B09DB873C16C7D57DDCACF9@DM6PR11MB4025.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
The bug discovered was with coreboot, and the PCD values are derived from
the block size of its SMMStore (NvStorage) region. The discussion on the
patch can be found here: https://review.coreboot.org/c/coreboot/+/62990
Hacking the PCDs could work,, but why would we want to keep an incorrect
check?
Thanks!
On Mon, 16 May 2022 at 08:36, Wu, Hao A <hao.a.wu@intel.com> wrote:
> Sorry for not being clear on what I mean.
>
> Is it possible to change the platform PCD values and keep these block size
> alignment requirements.
>
>
>
> Best Regards,
>
> Hao Wu
>
>
>
> *From:* devel@edk2.groups.io <devel@edk2.groups.io> * On Behalf Of *Sean
> Rhodes
> *Sent:* Monday, May 16, 2022 3:00 PM
> *To:* Wu; Wu, Hao A <hao.a.wu@intel.com>; devel@edk2.groups.io
> *Subject:* Re: [edk2-devel] [PATCH] MdeModulePkg/FaultTolerantWriteDxe:
> Don't check for address alignment
>
>
>
> Hi Hao
>
> Yes, it does conflict - I will update the patch to fix these comments :)
>
> Thank you
>
>
>
[-- Attachment #2: Type: text/html, Size: 2920 bytes --]
next prev parent reply other threads:[~2022-05-16 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16E1B70DABEEDF46.30116@groups.io>
2022-05-16 5:41 ` [edk2-devel] [PATCH] MdeModulePkg/FaultTolerantWriteDxe: Don't check for address alignment Sean Rhodes
2022-05-16 6:54 ` Wu, Hao A
2022-05-16 6:59 ` Sean Rhodes
2022-05-16 7:36 ` Wu, Hao A
2022-05-16 7:53 ` Sean Rhodes [this message]
2022-05-16 9:03 ` Wu, Hao A
2022-05-17 11:58 ` Sheng Lean Tan
2022-05-17 15:05 ` Zeng, Star
2022-05-17 15:16 ` Sean Rhodes
2022-10-03 9:53 ` Sheng Lean Tan
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=CABtds-2gL7uU_wCCTpYLXVySurMaK61Rv5bgk85LxnDbPj1LXw@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