Linaro QEMU 2014.01

Milestone information

Project:
Linaro QEMU
Series:
trunk
Version:
2014.01
Released:
2014-01-16  
Registrant:
Peter Maydell
Release registered:
2014-01-16
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon qemu-linaro-1.7.0-2014.01.tar.gz (md5, sig) qemu-linaro 2014.01 322
last downloaded today
Total downloads: 322

Release notes 

Linaro QEMU 2014.01 is the latest release of qemu-linaro. Based off upstream (trunk) QEMU, it includes a number of ARM-focused bug fixes and enhancements.

This release has been updated to be based on upstream's recent 1.7.0 release. Interesting ARM related upstream changes include the addition of experimental virtio device support in the vexpress-a9 and vexpress-a15 boards, and a new TCG target for emulating other CPUs on AArch64 host systems.

Note that unless you require any qemu-linaro specific features (the only current such feature is OMAP3 board emulation) it is likely you will be better served by upstream's releases than by the Linaro QEMU releases currently.

Changelog 

View the full changelog

version 2014.01:
 - Rebased onto upstream v1.7.0.
 - Interesting ARM related upstream changes include:
   - the addition of experimental virtio device support in the
     vexpress-a9 and vexpress-a15 boards via a virtio-mmio
     transport.
   - a model of the Calxeda ECX-2000 / Midway system
   - a new TCG target for emulating other CPUs on AArch64
     host systems

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.