search for: vexpress

Given that the xenvm machine is based on vexpress but with an extremely limited selection of peripherals (the guest is supposed to use virtual devices instead), add "xen,xenvm" to the list of compatible machines in mach-vexpress. Changes in v2: - remove include skeleton; - use #address-cells = <2> and #size-cells = <2>; -...

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.

Hi, I''ve tried several different approaches to debootstrap a working rootfs for with a Cortex A15 model ( FastModels ) and Xen but still face some issues. Some information on my setup. For a Dom0 kernel I''m using the latest version from git://github.com/torvalds/linux.git, I attached my config as it might be of some use for others. I''m using the latest Xen unstable

...now how to remove the parameter in the xml file, or in virsh. Regards Thank you Xu Here's the qemu-system-arm command, generated by libvirt: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/local/bin/qemu-system-arm -name test -S -machine vexpress-a15,accel=kvm,usb=off -cpu host -m 500 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid cab134ea-eed8-42e7-88cb-403ee2801e22 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/test.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mo...

...02138e0>] (pci_device_probe+0x90/0x120) from [<c025fe98>] (driver_probe_device+0x148/0x2c4) (Note that you cannot work around this by choosing a different block driver, because eventually virtio-serial is required which will fail in the same way). (5) To fix (4), it is planned to move to vexpress emulation. This also lifts the memory limit to <= 2GB. vexpress doesn't have PCI at all, but it has a non-upstream virtio-mmio transport which allegedly works (I've not tried it). This also requires a new kernel for Fedora/ARM build with vexpress support. The configure options mentio...

...atches for the kernel were merged in 3.8 it states. This results in Xen freezing when loading dom0: ... [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 32512 pages, LIFO batch:7 [ 0.000000] ------------[ cut here ]------------ [ 0.000000] WARNING: at arch/arm/mach-vexpress/v2m.c:431 v2m_dt_init_early+0x4c/0x70() [ 0.000000] [<c000d51c>] (unwind_backtrace+0x0/0xe0) from [<c0014e20>] (warn_slowpath_common+0x48/0x60) [ 0.000000] [<c0014e20>] (warn_slowpath_common+0x48/0x60) from [<c0014ef0>] (warn_slowpath_null+0x18/0x1c) [ 0.000000] [&l...

...tch; - stop iterating over the DT nodes in device_tree_for_each_node if func returns a value != 0; - return 1 from _find_compatible_node when a node is found; - move the wait loop and the syscfg cfgctrl write into a separate function; - fix comments; - define all registers in write; - move platform_vexpress.c to platforms/vexpress.c; - move platform_vexpress.h to arm-arm/platforms/vexpress.h; - use a lookup table to set the color masks; - fix indentation; - make sure mode_string is not NULL and is not bigger than 16 chars before continuing; - introduce 2 separate error messages for !hdlcd_start and !f...

...ELinux label on the kernel or device tree. @@ -124,7 +124,7 @@ the permissions or SELinux label on the kernel or device tree. If specified, search for a device tree which is compatible with the selected kernel and the name of which matches the given wildcard. You can use a wildcard such as C<vexpress-*a9*.dtb> which would match -C<vexpress-v2p-ca9.dtb>. +F<vexpress-v2p-ca9.dtb>. Notes: @@ -170,7 +170,7 @@ Possible formats are: A directory tree in the host filesystem. -The filesystem tree is written to C<OUTPUTDIR> (ie. the I<-o> option). +The filesystem tree...

...the cubietruck > to allow kvm to be utilized due to the lack of emulation support. > > In the meantime, I was waiting to get my hands on a cortex-a15 for the > purpose of sussing out an effort involved for a debian 8 host and a openwrt > guest. Because the qemu-system-arm supports vexpress-a15 there is better > emulation support, but compiling the guest kernel to match the target host > cpu offers a better chance that kvm acceleration is utilize? In other word > -cpu host is always better? I haven't tested this in a while to generalize like that. But last time tested...

...drivers/clk/st/clkgen-fsyn.c | 2 +- drivers/clk/st/clkgen-mux.c | 8 ++++---- drivers/clk/st/clkgen-pll.c | 4 ++-- drivers/clk/ti/clk-dra7-atl.c | 2 +- drivers/clk/ti/clockdomain.c | 2 +- drivers/clk/versatile/clk-vexpress-osc.c | 2 +- drivers/coresight/coresight-replicator.c | 2 +- drivers/devfreq/event/exynos-ppmu.c | 2 +- drivers/devfreq/tegra-devfreq.c | 2 +- drivers/dma/bestcomm/bestcomm.c | 4 ++-- drivers/dma/k3dma.c | 2 +- drivers/dma/mm...

...drivers/clk/st/clkgen-fsyn.c | 2 +- drivers/clk/st/clkgen-mux.c | 8 ++++---- drivers/clk/st/clkgen-pll.c | 4 ++-- drivers/clk/ti/clk-dra7-atl.c | 2 +- drivers/clk/ti/clockdomain.c | 2 +- drivers/clk/versatile/clk-vexpress-osc.c | 2 +- drivers/coresight/coresight-replicator.c | 2 +- drivers/devfreq/event/exynos-ppmu.c | 2 +- drivers/devfreq/tegra-devfreq.c | 2 +- drivers/dma/bestcomm/bestcomm.c | 4 ++-- drivers/dma/k3dma.c | 2 +- drivers/dma/mm...

These series patch enable Allwinner A31(code name sun6i) support in assemble. with these patches, the cpu 0 of sun6i SOC could successful boot into the c environment. Bamvor Jian Zhang (4): xen/arm: introduce Cortex-A7 support xen/arm: introduce Allwinner sun6i SOC basic support xen/arm: enable early printk for sun6i xen/arm: enable switch to hyper mode for sun6i xen/arch/arm/Rules.mk

...ations of virtio-mmio", you mean "non-QEMU implementations of the ACPI tables". The hardware implementation of virtio-mmio doesn't care at all about the ACPI ID. (In fact the most plausible other-implementation would be UEFI using its own (hard-coded) ACPI tables on top of a QEMU vexpress-a15 model or something similar.) -- PMM

...ations of virtio-mmio", you mean "non-QEMU implementations of the ACPI tables". The hardware implementation of virtio-mmio doesn't care at all about the ACPI ID. (In fact the most plausible other-implementation would be UEFI using its own (hard-coded) ACPI tables on top of a QEMU vexpress-a15 model or something similar.) -- PMM

Hi all, a few weeks ago I (and a few others) started hacking on a proof-of-concept hypervisor port to Cortex-A15 which uses and requires ARMv7 virtualization extensions. The intention of this work was to find out how to best support ARM v7+ on Xen. See http://old-list-archives.xen.org/archives/html/xen-arm/2011-09/msg00013.html for more details. I am pleased to announce that significant progress

Hi, I am trying to run libvchan on ARM Fast Model for VExpress platform for using inter domain communication. But there are some errors. I am attaching the strace outputs for vchan-node1 run in dom0 and domU. Has anybody faced these issues before. Xl console 1The command is Usage: vchan-node1 [client|server] [write|read] domid nodepath my nodepath is - /loc...

Hi all, a few weeks ago I (and a few others) started hacking on a proof-of-concept hypervisor port to Cortex-A15 which uses and requires ARMv7 virtualization extensions. The intention of this work was to find out how to best support ARM v7+ on Xen. See http://old-list-archives.xen.org/archives/html/xen-arm/2011-09/msg00013.html for more details. I am pleased to announce that significant progress

Hi all, a few weeks ago I (and a few others) started hacking on a proof-of-concept hypervisor port to Cortex-A15 which uses and requires ARMv7 virtualization extensions. The intention of this work was to find out how to best support ARM v7+ on Xen. See http://old-list-archives.xen.org/archives/html/xen-arm/2011-09/msg00013.html for more details. I am pleased to announce that significant progress

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

Hi, things are progressing slowly, but I feel that eventually I'll be getting there: supermin can be built on all Linux-based architectures that are part of Debian/unstable[1] -- (except for sparc, but I'll ignore that for now.) libguestfs on the other hand currently fails launching the appliance (necessary for running tests) on everything but x86 and mips. Apparently, qemu-system-arm