All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Tamas K Lengyel <tamas.k.lengyel@gmail.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: Unable to boot Xen 4.7-rc4 on HiKey
Date: Thu, 2 Jun 2016 12:24:00 +0100	[thread overview]
Message-ID: <57501750.1070203@arm.com> (raw)
In-Reply-To: <CABfawhk_vyXtFB3nCjVzfTmVj5q6kmZHY6bUcabnGpYAB4ywUg@mail.gmail.com>

Hi Tamas,

On 02/06/16 02:09, Tamas K Lengyel wrote:
> On Wed, Jun 1, 2016 at 3:49 PM, Julien Grall <julien.grall@arm.com> wrote:
>> On 01/06/2016 18:10, Tamas K Lengyel wrote:
>>>
>>> Hi all,
>>> following the steps from http://wiki.xen.org/wiki/HiKey I'm unable to
>>> get the board to boot Xen. I'm using the Debian reference image from
>>> linaro as base
>>> (https://builds.96boards.org/releases/hikey/linaro/debian/latest/)
>>> and that boots fine both from the SD card directly and through
>>> startup.nsh. However, when I try to boot Xen I see only the following:
>>>
>>> Xen 4.7.0-rc (c/s Mon May 23 12:07:20 2016 +0100 git:8478c94-dirty) EFI
>>> loader
>>> Using configuration file 'xen.cfg'
>>> Image: 0x000000007a121000-0x000000007acb8a70
>>>
>>> After that no output and dom0 never comes online on the network
>>> either. I tried compiling Xen on the device itself in case it was a
>>> problem with my cross-compile setup but no difference. Also with and
>>> without debug=y. Any tips on what might be going wrong here?
>>
>>
>> I gave a quick look at the upstream device-tree of the hikey, the path
>> /smb/uart@f7113000.
>>
>> If you use the upstream device-tree, it should be able to find the correct
>> UART via "stdout-path" and therefore dtuart=... should not be necessary.
>>
>> Let me know if it works for you, and I will update the wiki page.
>
> No, I removed the dtuart=... part from xen.cfg but there is no
> difference in the output and dom0 never comes up on the network
> either.

Which device-tree are you using?

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-06-02 11:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-01 17:10 Unable to boot Xen 4.7-rc4 on HiKey Tamas K Lengyel
2016-06-01 21:49 ` Julien Grall
2016-06-02  1:09   ` Tamas K Lengyel
2016-06-02 11:24     ` Julien Grall [this message]
2016-06-02 22:34     ` Chenxiao Zhao
2016-06-02 16:53       ` Tamas K Lengyel
2016-06-02 17:02         ` Julien Grall
2016-06-02 17:14           ` Tamas K Lengyel
2016-06-02 17:20             ` Tamas K Lengyel
2016-06-02 18:06               ` Julien Grall
2016-06-02 18:14                 ` Tamas K Lengyel
2016-06-02 16:54   ` Tamas K Lengyel

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=57501750.1070203@arm.com \
    --to=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=tamas.k.lengyel@gmail.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.