search for: exynos5250

...julieng/linux-arm.git last commit: 3f35c6f2b805901fbde2ce7553478a8cd4249a33 The linux-domU repository is the same but branch arndale-domU-3.9: git://xenbits.xen.org/people/julieng/linux-arm.git last commit: 510c35298dfbb6ccb0d883cb34a27eff2f291cea I tried to add ''CONFIG_EARLY_PRINTK = exynos5250'' and ''debug=y'' in .config file and in Config.mk but still no output. This is all I get: U-Boot 2012.10-rc1-g0faa5ad-dirty (May 01 2013 - 23:42:46) for ARNDALE5250 CPU: Exynos5250@1000MHz Board: for ARNDALE5250 I2C: ready DRAM: 2 GiB WARNING: Caches not enabled...

Hello, While I was doing some tests in Arndale board, the network (iperf) throughput suddenly decreases to 5Mbps (from 100Mbps) out of nowhere. This typically happens when I generate traffic using iperf (100Mbps) while installing some packages using apt-get in dom0. Whenever this behavior happens, I can not see any distinguishable logs from any places. After some debugging, I found that

The current early-printk support for ARM is rather hard-coded, making it hard to add machines or tweak settings. This series slightly moves some code to gather UART settings in xen/arch/arm/Rules.mk instead of the actual .c files. Also it allows two different machines with different settings to share the same driver, which the last patch exploits to add support the Calxeda Midway hardware. This

Hello, I am trying to boot Arndale board with Julien''s new XenARM patch series. But I have got "Data Abort" while in booting. My environment is: - Arndale Board - Xen-4.3-unstable from branch "arm" in git://xenbits.xen.org/people/julieng/xen-unstable.git - Dom0 Kernel from branch "dev-arndale-dom0-3.9" in

Hi Xen Developers, I had tested new XenARM for Arndale board that is updated in Anthony''s tree from 2 days ago. I expected that will be working. But, I can not boot Dom0 Kernel. I used kernel and XenARM both are from Xen Wiki(http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale). It (seems) stopped after "(XEN) Freed 212kB init memory" message. When I

The majority of this series went in a while back, what remains is just the basic platform support and the UART blacklisting. The series has also grown a constcorrectness fix for the other existing platforms too. Still no SATA support from upstream sadly. Bamvor has written some generic docs at http://wiki.xenproject.org/wiki/Xen_ARMv7_with_Virtualization_Extensions/Allwinner Thanks, Ian.

...// //setenv script_addr_r 0x40080000// // //setenv bootcmd_load_linux_mmc ''ext2load mmc 0:1 $kernel_addr_r /zImage''// //setenv bootcmd_load_xen_mmc ''ext2load mmc 0:1 $xen_addr_r /xen-uImage''// //setenv bootcmd_load_dtb_mmc ''ext2load mmc 0:1 $dtb_addr_r /exynos5250-arndale.dtb''// //setenv bootcmd_load_script_mmc ''ext2load mmc 0:1 $script_addr_r /load-xen-mmc.img''// // //setenv bootcmd ''run bootcmd_load_script_mmc; source $script_addr_r''// //setenv xen_bootargs ''sync_console console=dtuart dtuart=/serial@...

Since OMAP UART has a few distinct features than common 8250 UART, I re-implemented its driver rather than porting it based on ns16550.c. There are mainly two big differences between the implementations. First, OMAP UART introduces the concept of register access mode, which divides the register map into seperated space. Switching the access mode is then necessary when configuring it. Second, THRE