Couldn't you even manage to try a few wines? On Thu, Aug 22, 2019 at 9:59 AM Steve Simon <st...@quintile.net> wrote:
> hi all > > just to say i am very excited abou the pi4 port but am on holiday in > France at the moment so i cannot even help with testing. > > -Steve > > > On 22 Aug 2019, at 9:07 am, Richard Miller <9f...@hamnavoe.com> wrote: > > >> 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). > > > > >
