On 23.02.19 15:05, Amit Tomer wrote:
Hello,
Hi
Did removing reserved-memory regions together with users work out well
for you?
Removing "reserved-memory" node along with "mmngr" worked well. Tested it
with v3.15 BSP release.
ok
Also, just tried loading XEN from one of your branch[1] but it stuck with this:
[ 13.793305] host 10.105.2.27 is alive
[ 13.797050] => tftp 0x48000000 xen
[ 20.944681] ravb:0 is connected to ravb. Reconnecting to ravb
[ 20.952032] ravb Waiting for PHY auto negotiation to complete... done
[ 23.964201] ravb: 1000Base/Full
[ 23.972794] Using ravb device
[ 23.975792] TFTP from server 10.105.2.27; our IP address is 10.105.2.28
[ 23.982685] Filename 'xen'.
[ 23.985588] Load address: 0x48000000
[ 23.989307] Loading:
#################################################################
[ 29.073520]
#################################################################
[ 29.155589] ##################
[ 29.178818] 141.6 KiB/s
[ 29.181540] done
[ 29.183447] Bytes transferred = 754000 (b8150 hex)
[ 29.188789] => booti 0x48000000
[ 34.990295] Image lacks image_size field, assuming 16MiB
[ 34.995837]
[ 34.997362] Starting kernel ...
[ 35.000628]
Do we need to chose some other address where it should be loaded ?
We usually load Xen to 0x48080000...
I think, it is up to you to what address to load images in U-Boot.
Just to be sure that you won't overwrite something else in memory
(stack, other images, etc)...
I would suggest you to build with early printk support enabled and see
what is wrong.
CONFIG_EARLY_PRINTK=scif,0xe6e88000
BTW, we use mkimage tool to create Xen image to be loaded:
mkimage -A arm64 -C none -T kernel -a 0x78080000 -e 0x78080000 -n "XEN"
xen/xen xen-uImage
Thanks
-Amit
--
Regards,
Oleksandr Tyshchenko
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
