Re: Stuck trying to boot Xen 4.3 on Arm Midway

[Stefan Bader <stefan.bader@canonical.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2771 bytes --]

On 02.12.2013 16:52, Ian Campbell wrote:
> On Mon, 2013-12-02 at 16:43 +0100, Stefan Bader wrote:
>> On 02.12.2013 16:24, Ian Campbell wrote:
>>> On Mon, 2013-12-02 at 15:59 +0100, Stefan Bader wrote:
>>>> I am trying to extract and combine the various pieces of information found in
>>>> [1] and its sub-pages and the Xen in-tree documentation in order to make xen
>>>> boot (potentially non-smp without some later changes). But since I am not
>>>> familiar enough with Arm I think I am stuck doing something wrong.
>>>>
>>>> I compiled the hypervisor with debug and early printk for midway and use the
>>>> xen.bin file (I could get no output at all when trying to create a uboot image
>>>> with mkimage from the uncompressed xen.gz).
>>>
>>> What version are you using? xen.bin went away in July, the right file is
>>> now just "xen".
>>
>> The released version of xen 4.3. At some point I might update to 4.3.1 (or
>> whatever stable is current then). This probably implies picking some additional
>> patches when I want to get it running on Midway.
> 
> Xen 4.3 for ARM was a tech preview. I believe at the time it ran on
> Model and versatile express. Getting it running on anything else is
> going to be a big job I'm afraid. I'd suggest either waiting for 4.4 or
> using current tip in the meantime.
> 
>>  The xen.bin would not be
>> packaged right now but it had the right format to be used by bootz while xen.gz
>> (or xen after unpacking) would not be usable in uboot without converting and
>> that need some more address values which I could and likely do get wrong.
> 
> In 4.3 xen.bin was the correct zImage compatible thing. I'm not sure
> what you mean about the address values, but as I say if you are
> expecting it to work on midway easily you are going to be disappointed.

Not really expecting _anything_ to work easily these days. :) What I meant there
was that you have to specify base address and start offset in the mkimage call
and I used the 0x8000000 (give or take a zero I am typing from memory) that was
used in the xen build to convert from xen-bin into xen for both.

> 
> 
>> Thanks, I will look through that later. One thin I noted is the dtb setup.
>> Examples out there often vary in having a modules sub-leaf or not. I would think
>> that from the early printk I am at least right to use the deeper nesting. At
>> least consistent with the in-source doc at that time/ release.
> 
> I can't remember what 4.3 did, but at least these days the depth is not
> that important, it's the compatabile string and presence beneath /chosen
> which matter.

Ok, sounds like I can abandon all hope for 4.3 anyway. But good to know that.
Just a bit confusing.

-Stefan
> 
> Ian.
> 
> 



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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