The physical address of the frame buffer

[shodruk]

When I run , I always get 0x2d100000 as a physical address of the frame buffer.
The eCore coordinates of this address is (11, 17), this is far east from our Epiphany, so I could access it from Epiphany directly.
Is this a fixed address? Or was it by chance that it worked successfully?

[tnt]

The drivers seems to use CMA to reserve a memory zone. The actual address is not hardcoded, but it's also not randomized so as long as the boot sequence and software (u-boot / kernel / device-tree / ... ) doesn't change, it will stay constant.

[ysapir]

You can always tell the eCore where the FB was allocated at run-time, communicating from the host.

[shodruk]

Thanks, tnt, ysapir,

If the address is 0x2c000000, then the eCore coordinates of its address is (11, 0), and we can't access it from Epiphany. (because the request goes to west eLink and is lost)
Is this right?