I don't think SeaBIOS should be altering coreboot information. (Doing
so leads to all sorts of painful debugging problems, for example.)
Well, currently it is marking at least first couple of kilobytes of
memory (4 if I recall correctly) as free to use RAM. There coreboot
tables are
On Mon, Nov 05, 2018 at 01:27:10PM +0100, Krystian Hebel wrote:
> SeaBIOS modifies its internal e820 structure, but does not propagate
> these changes back to coreboot tables. This resulted in multiple errors
> in MemTest86 when run on 2 GB platforms, probably because of some
> memory-mapped
On 11/05/18 13:32, Paul Menzel wrote:
Thank you for the patch. If it’s the common problem, then it was > fixed in “coreboot’s” MemTest86+ [1]. Can you reproduce the problem
> with that version?
Yes, it is the version on which I tested. It worked OK before [1],
because when no
coreboot
Dear Krystian,
On 11/05/18 13:27, Krystian Hebel wrote:
> SeaBIOS modifies its internal e820 structure, but does not propagate
> these changes back to coreboot tables. This resulted in multiple errors
> in MemTest86 when run on 2 GB platforms, probably because of some
> memory-mapped devices.
>
