Re: [PATCH v2] xen: arm64: Add support for Renesas RCar Gen3 H3 Salvator-X platform

[Dirk Behme <dirk.behme@de.bosch.com>]

Hi Julien,

On 06.07.2016 16:21, Julien Grall wrote:
>
>
> 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.


Ok, thanks, booti does work [1].


Most probably just cosmetics, but again our friend image_size:

Image lacks image_size field, assuming 16MiB

Is there any special reason why we don't write the image size to the xen 
header?

Or should we try to fix it? E.g. like the Linux kernel is doing it?

Best regards

Dirk

[1]

=> booti 0x48000000 - 0x4A000000
Image lacks image_size field, assuming 16MiB
## Flattened Device Tree blob at 4a000000
    Booting using the fdt blob at 0x4a000000
    Using Device Tree in place at 000000004a000000, end 000000004a00c767

Starting kernel ...

- UART enabled -
- CPU 00000000 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Checking for initrd in /chosen
....

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