Re: [coreboot] x86: best approach to debug consumer hardware?

[Nico Huber]

On 06.07.2017 07:20, Zoran Stojsavljevic wrote:
> Top of Low Usable RAM 00d0h??? Any explanation for that?

The simplest and most obvious explanation turned out to be true, the
register is encoded as multiples of 16MiB.

Nico

x86: best approach to debug consumer hardware?

[Zoran Stojsavljevic]

> The simplest and most obvious explanation turned out to be true, the register

is encoded as multiples of 16MiB.

You say (in other words) the following: Coreboot prepares the whole
populated 32 bit (physical layout) DRAM2 space for some OS, don't you?

TOLUD = d0000000h, and the next 256MiB are reserved for MM PCI + MM PCIe
(Yonah is Y2006, so PCIe came in Y2004), so somewhere above there will be
PCI configuration space (minimum 64K x 256 = 16MiB, maybe more, since some
ports are PCIe), Then HSEG, after boot FLASH.
_______

Well, Andrey, if Nico is right, you have reduced options... Dracut stays as
one of very seldom options to try, don't you agree?

Zoran

On Thu, Jul 6, 2017 at 5:44 PM, Nico Huber  wrote:
> On 06.07.2017 07:20, Zoran Stojsavljevic wrote:
> > Top of Low Usable RAM 00d0h??? Any explanation for that?
>
> The simplest and most obvious explanation turned out to be true, the
> register is encoded as multiples of 16MiB.
>
> Nico