From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8cad36b2833c37206e385b368fc2e793@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Thu, 22 Aug 2019 08:07:25 +0100
In-Reply-To: <3468103FF6FA1E43500C7F1B15610D60@felloff.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] raspberry pi 4 arm64 test image
Topicbox-Message-UUID: 063adbc4-eada-11e9-9d60-3106f5b1d025

> oh dear. i dont even know the expected physical memory map...
> i guess that ram is continuous block at [0-0xfc000000). but
> some memory might be reserved...

No, the framebuffer is always reserved at the top of the
first 1GB, so on 2GB and 4GB units there are two separate
regions.

> - atags
> - device tree /memory/reg property
> - firmware property request (getramsize() in vcore.c)
> 
> for me getramsize() returns zero for both base and limit so its
> completely useless.

That's strange, getramsize works on my 2GB pi4:
	getramsize 0 1046478848

The same values are in atags (you need 'device_tree=' in config.txt
to make the firmware pass atags instead of devicetree).