On 16 May 2011 13:20, karim.allah.ahmed@gmail.com

<karim.allah.ahmed@gmail.com> wrote:
> Can somebody please explain how development happens regarding qemu-linaro ?
>
> I've taken a look here [0] and If I'm not mistaken, there's no code in the
> repo.

We don't keep qemu-linaro in a launchpad bzr repo. The code lives in
the Linaro git repository:
http://git.linaro.org/gitweb?p=qemu/qemu-linaro.git;a=summary

https://wiki.linaro.org/WorkingGroups/ToolChain/QEMU
is intended to be a brief summary of the aims of the qemu-linaro tree,
but briefly, the idea is to provide a staging post for ARM releated
QEMU work which we are planning to push upstream but haven't yet.
Currently the major feature in this tree but not yet upstream is
support for OMAP3 (including Beagle board models); the plan for
the next six-month cycle includes working on getting that upstream.

> I can see a lot of blueprints, but I don't understand how work is
> being done regarding those blueprints or when will it be done!

In common with the other Linaro working groups, the toolchain
group's QEMU work is focused on upstream collaboration. So much
of the planned work is delivered as a set of patches submitted and
eventually committed to upstream QEMU. qemu-linaro then picks up
those changes as part of its tracking of upstream.

On blueprints:
If a blueprint is 'approved' then we've committed to doing the
work for the six-month cycle (which Launchpad calls a 'series')
it is targeted against. The 1105 cycle finishes in two weeks which
is why there are currently only a few blueprints left visible on
launchpad as not yet finished. Blueprints for 1111 are currently
being written. (If you want to look at our current set of
proto-blueprints they're on the wiki:
https://wiki.linaro.org/PeterMaydell/Qemu1111
We'll be finalising the list in the next two weeks and turning
them into proper launchpad blueprints.)

For tracking progress on this work, status.linaro.org is good.
Unfortunately there's no easy way to show only QEMU work, but
you can start at the Toolchain Group's page:
 http://status.linaro.org/linaro-toolchain-wg.html
and then click through to the individual Technical Requirements,
for example
http://status.linaro.org/group/tr-toolchain-consolidate-qemu.html
which in turn show progress on individual blueprints.

> Oh, and what exactly is the 'qemu-linaro' tarball in the repo ?

The tarballs are monthly source releases of the qemu-linaro tree.
They get some testing, and are also published as Ubuntu packages
via a PPA. They're a convenient way to try a "latest bleeding
edge" QEMU with extra ARM goodness.

-- Peter Maydell