Linaro QEMU package in Ubuntu?
rsalveti at rsalveti.net
Wed Dec 8 17:50:25 UTC 2010
On Wed, Dec 8, 2010 at 7:23 AM, Peter Maydell <peter.maydell at linaro.org> wrote:
> On 8 December 2010 08:53, Jani Monoses <jani at ubuntu.com> wrote:
>> one of the Ubuntu blueprints for 11.04 is to provide a QEMU better suited to
>> Linaro/ARM work in the official archives, allowing to
>> at least the official Ubuntu ARM images.
>> The Linaro PPA provides a package based on qemu-maemo from gitorious,
>> and it is ahead of what is packaged in that it supports the BeagleBoard.
> Yes. At the moment I think that something based on that tree is
> your best practical choice if you want neon support and certainly
> if you need omap3.
>> I see there's also qemu-arm repo in git.linaro.org - I assume this is a
>> newer and preferable upstream to the maemo one?
> No. This tree is currently tracking qemu upstream master and I am
> using it as a way to provide tested arm patches to upstream in a way
> that they can pull.
Are you also tracking all those additional omap 3 patches available at
the maemo/meego tree?
I'm ok to use the maemo/meego one, as it's currently used by Linaro,
but I don't know if they are actually following or at least rebasing
their patches over the upstream tree. The idea of that blueprint is
basically to identify what is the best maintainable and working tree
for at least one target (omap or versatile) so we can get the best
Qemu experience for ARM at Ubuntu, by the time of the Natty release.
It seems that the current best working target is the omap 3 one, but
at UDS it was said that upstream wasn't that happy to incorporate
those patches so soon, so we get to the point that is inevitable to
keep both trees, or creating a new one incorporating all these patches
and help trying to get them upstream (and that's what I thought the
linaro git tree was all about).
>> Are the ARM patches being pushed and accepted into upstream QEMU regularly?
>> In this case there may be no need to create a new package
>> and just wait for that work to get released and packaged, and maybe focus
>> the effort on helping with upstreaming the ARM changes.
> This depends on how long you are prepared to wait. Some ARM
> fixes are starting to go into upstream. OTOH upstream's proposed
> release cycle is about once every 6 months, with 0.14 due to
> branch very shortly. So 0.15 ought to be much better for ARM
> support but won't be available until middle of next year.
> I'm currently focusing most of my effort on working with upstream
> to get these patches accepted. I also have a blueprint for doing
> at least enough maintenance/bugfixing on the maemo-qemu
> package so it continues to boot the linaro images.
Ok, so you're saying that the maemo-qemu package will be probably the
one used by the Linaro's tools for the next cycle?
Ricardo Salveti de Araujo
More information about the linaro-dev