From: Julien Grall <julien.grall@arm.com>
To: Dirk Behme <dirk.behme@de.bosch.com>,
Andre Przywara <andre.przywara@arm.com>
Cc: xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>,
Dirk Behme <dirk.behme@gmail.com>
Subject: Re: [PATCH v2] xen: arm64: Add support for Renesas RCar Gen3 H3 Salvator-X platform
Date: Wed, 6 Jul 2016 15:21:28 +0100 [thread overview]
Message-ID: <577D13E8.7040805@arm.com> (raw)
In-Reply-To: <45d9a5fc-1f6a-0fb8-2bee-ae24843b2647@de.bosch.com>
On 06/07/16 15:03, Dirk Behme wrote:
> On 06.07.2016 15:17, Julien Grall wrote:
>> Hi Dirk,
>>
>> On 06/07/16 07:33, Dirk Behme wrote:
>>> Could you share the U-Boot commands how you load and esp. start Xen? For
>>> loading you use TFTP? How do you start Xen with U-Boot, then? I think we
>>> have to pass the device tree address in x0 and the Linux kernel image
>>> address in x2. How do you do this with an U-Boot command?
>>
>> U-boot can load Xen from TFTP or from the SD-card. This is the same as
>> booting a baremetal kernel with U-boot.
>>
>> There is a section on the wiki page to explain how to create the
>> device-tree node for the boot modules [1] and the allwinner page [2]
>> gives a full example how to boot Xen with U-boot via tftp (Note that it
>> could easily be adapted to load from the SD-Card).
>>
>> Regards,
>>
>> [1]
>> http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions#Boot_Modules
>>
>>
>> [2]
>> http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner#Boot_script
>>
>
>
> Hmm, sorry, I still seem to miss anything :(
>
> I've loaded xen/xen with U-Boot to 0x4A000000 and then try to start it
> as described in [2] above:
>
> => bootz 0x4A000000 - 0x48000000
> Bad Linux ARM zImage magic!
>
> I'm not sure why xen/xen is assumed to be a zImage?
Oh, sorry I meant to say that bootz should be replaced by booti but
forgot to write it down.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-06 14:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 6:37 [PATCH v2] xen: arm64: Add support for Renesas RCar Gen3 H3 Salvator-X platform Dirk Behme
2016-07-05 11:39 ` Julien Grall
2016-07-05 12:09 ` Dirk Behme
2016-07-05 12:45 ` Julien Grall
2016-07-05 13:04 ` Dirk Behme
2016-07-05 13:34 ` Julien Grall
2016-07-05 13:45 ` Andre Przywara
2016-07-05 14:22 ` Dirk Behme
2016-07-05 14:29 ` Andre Przywara
2016-07-06 6:33 ` Dirk Behme
2016-07-06 13:17 ` Julien Grall
2016-07-06 14:03 ` Dirk Behme
2016-07-06 14:21 ` Julien Grall [this message]
2016-07-07 10:39 ` Dirk Behme
2016-07-07 10:46 ` Julien Grall
2016-07-08 11:38 ` Dirk Behme
2016-07-11 9:25 ` Andre Przywara
2016-07-11 10:15 ` Dirk Behme
2016-07-05 13:04 ` Stefano Stabellini
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=577D13E8.7040805@arm.com \
--to=julien.grall@arm.com \
--cc=andre.przywara@arm.com \
--cc=dirk.behme@de.bosch.com \
--cc=dirk.behme@gmail.com \
--cc=sstabellini@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).