All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr <olekstysh@gmail.com>
To: Amit Tomer <amittomer25@gmail.com>
Cc: xen-devel@lists.xenproject.org,
	Julien Grall <julien.grall@arm.com>,
	andrii_chepurnyi@epam.com
Subject: Re: XEN on R-CAR H3
Date: Mon, 25 Feb 2019 15:12:41 +0200	[thread overview]
Message-ID: <78c899ed-2b6a-1057-dde0-05f92c3fb81a@gmail.com> (raw)
In-Reply-To: <CABHD4K9GHmNpHSQH0uR7Rtf6gJzN-xW_MeARQzY9z89pcXY5ZQ@mail.gmail.com>


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

  reply	other threads:[~2019-02-25 13:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 14:41 XEN on R-CAR H3 Amit Tomer
2019-02-06 15:03 ` Oleksandr
2019-02-06 15:18   ` Amit Tomer
2019-02-08 18:21     ` Amit Tomer
2019-02-09 16:48       ` Oleksandr
2019-02-15 14:17         ` Amit Tomer
2019-02-15 19:51           ` Oleksandr
2019-02-18 12:53             ` Amit Tomer
2019-02-18 20:00               ` Oleksandr
2019-02-19 16:46                 ` Amit Tomer
2019-02-20 18:13                   ` Oleksandr
2019-02-20 18:31                     ` Amit Tomer
2019-02-20 20:13                   ` Julien Grall
2019-02-20 21:28                     ` Oleksandr Tyshchenko
2019-02-21 10:11                       ` Julien Grall
2019-02-21 19:28                         ` Oleksandr
2019-02-25 14:43                           ` Oleksandr
2019-02-25 23:23                             ` Julien Grall
2019-02-26 18:09                               ` Oleksandr
2019-02-21 18:20                       ` Amit Tomer
2019-02-21 18:44                         ` Oleksandr
2019-02-22 19:15                           ` Oleksandr
2019-02-22 20:08                             ` Amit Tomer
2019-02-23 13:05                               ` Amit Tomer
2019-02-25 13:12                                 ` Oleksandr [this message]
2019-02-27 20:03                                   ` Oleksandr
2019-03-05 16:50                                     ` Amit Tomer
2019-03-05 18:07                                       ` Oleksandr
2019-03-05 18:10                                         ` Amit Tomer
2019-03-05 19:40                                           ` Oleksandr
2019-03-13 12:41                                             ` Amit Tomer
2019-03-15 18:50                                               ` Oleksandr
2019-02-21 18:15                     ` Amit Tomer
2019-02-27 11:00                       ` Julien Grall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=78c899ed-2b6a-1057-dde0-05f92c3fb81a@gmail.com \
    --to=olekstysh@gmail.com \
    --cc=amittomer25@gmail.com \
    --cc=andrii_chepurnyi@epam.com \
    --cc=julien.grall@arm.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.