On Tue, 16 Jan 2024 at 10:37, Laszlo Ersek wrote:
>
> On 1/15/24 18:56, Ard Biesheuvel wrote:
> > On Mon, 15 Jan 2024 at 11:21, Laszlo Ersek wrote:
> >>
> >> On 1/12/24 12:37, Gerd Hoffmann wrote:
> >>> This is a little series containing the flash corruption fix sent
> >>> yesterday with an
On 1/15/24 18:56, Ard Biesheuvel wrote:
> On Mon, 15 Jan 2024 at 11:21, Laszlo Ersek wrote:
>>
>> On 1/12/24 12:37, Gerd Hoffmann wrote:
>>> This is a little series containing the flash corruption fix sent
>>> yesterday with an slightly improved commit message and some small
>>> improvements on
On Mon, 15 Jan 2024 at 11:21, Laszlo Ersek wrote:
>
> On 1/12/24 12:37, Gerd Hoffmann wrote:
> > This is a little series containing the flash corruption fix sent
> > yesterday with an slightly improved commit message and some small
> > improvements on top of this.
> >
> > Gerd Hoffmann (4):
> >
On 1/15/24 11:21, Laszlo Ersek wrote:
> - please only ever apply the bit-neg operator on values that are UINT32,
> UINTN, or UINT64. Otherwise we get sign bit flipping, and that's
> terrible. (Most people are not even aware of it happening.)
Doing this is BTW not as obvious as it might seem,
On 1/12/24 12:37, Gerd Hoffmann wrote:
> This is a little series containing the flash corruption fix sent
> yesterday with an slightly improved commit message and some small
> improvements on top of this.
>
> Gerd Hoffmann (4):
> OvmfPkg/VirtNorFlashDxe: fix shadowbuffer reads
>
This is a little series containing the flash corruption fix sent
yesterday with an slightly improved commit message and some small
improvements on top of this.
Gerd Hoffmann (4):
OvmfPkg/VirtNorFlashDxe: fix shadowbuffer reads
OvmfPkg/VirtNorFlashDxe: clarify block write logic