Linaro QEMU package in Ubuntu?
peter.maydell at linaro.org
Wed Dec 8 17:59:51 UTC 2010
On 8 December 2010 17:50, Ricardo Salveti <rsalveti at rsalveti.net> wrote:
> 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?
Well, there's http://gitorious.org/ubuntu-qemu-omap which is really
just the maemo tree with packaging patches on it. I've done the
odd bugfix to the omap code but I've been able to get those taken
into the maemo/meego tree so there's been no need to carry them
as a separate linaro/ubuntu tree.
OMAP3 support patches are on the todo list to help in getting
them upstream, but they're behind the ARM correctness fixes
> 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).
Well, the linaro git tree is assisting in that process, but it's doing
it by being where I put small reviewed sets of patches in a rebased
branch that Anthony can pull, rather than by being a complete
tree of upstream + all known ARM fixes. (I think if we tried to
maintain the latter it would be a lot of work and would look pretty
similar to the meego tree anyhow, but if people think it's worthwhile
effort we can talk about it.)
>> 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?
More information about the linaro-dev