Re: [Xen-devel] Question about running Xen 4.4 on Arndale board

[Julien Grall <julien.grall@xxxxxxxxxx>]

On 04/14/2014 06:07 PM, Suriyan Ramasami wrote:

> Also, please note the typo for EARLY_PRINTK_BAUD. I guess Julien
> missed a 0 at the end.

Hrmmm, right. I didn't check my patch.

> 
> For the exynos5410, this is what I did with some expert guidance from
> Julien and Ian Campbell. I shall document it here, as it might help
> you too.
> 
> Changes in XEN (xen 4.4 stable) (first lets get XEN to boot and show
> some output)
> 1. change: xen/arch/arm/platforms/exynos5.c structure:
> exynos5_dt_compat[], and add âsamsung,exynos5410â in that list
>    For you it might be "samsung,exynos5420" -> check your dtsi file.

Do you plan to send a patch for adding odroid Xu support in Xen?


> 2. Linux kernel exynos5410.dtsi (for you possibly exynos5420.dtsi)to
> have the ARCH generic timer information. You might already have it.

Do you plan to send this patch on Linux upstream?

> timer {
>  compatible = "arm,cortexÂa15Âtimer","arm,armv7Âtimer";

I guess you meant arm,armv7-timer?

>  interrupts = <1 13 0xf08>,
>           <1 14 0xf08>,
>           <1 11 0xf08>,
>           <1 10 0xf08>;
>           clockÂfrequency = <24000000>;
> };
> Above works for 5250 and 5410.
> 3. Comment out all CPUs but the first cpu to start with (done in your
> exynos5420.dtsi file)
> 4. As Tod mentioned, you are missing the dtb file that you need to
> pass as 3rd parameter to the bootm command. -> bootm $kernel_addr_t -
> $dtb_addr_t
> 5. The bootargs that you have set for xen, need to have the
> console=dtuart dtuart=/serial@12C20000.
>    For you as Julien pointed out it might be @12C30000
> I am not sure if just settign bootargs will help. I wonder if it has
> to be fdt set to /chosen etc. I have pasted a working env file which
> you can modify and convert to scr to run it if need be.

We should see some messages

> For building XEN (make dist-xen), I am not sure if you have to add
> debug=y as well for the CONFIG_EARLY_PRINTK=exynos5420 to be pulled in
> - but, please do check on that.

Aargh, I though Ian's patch to print an error when CONFIG_EARLY_PRINTK
is used without debug=y was in Xen 4.4.

From HyonYoung's previous mail, debug=y was not set.

Regards,

-- 
Julien Grall

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