All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
	"Jan Petrouš" <jan.petrous@tieto.com>
Subject: Re: [Qemu-devel] [PATCH] integrator/cp: add support for REFCNTregisterr
Date: Tue, 05 Nov 2013 16:18:26 +0000	[thread overview]
Message-ID: <p1k3gm960d.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA_E4H6O=T34Na07a-6hTsqBzTZAq8JsNnYzZAQVasgq8Q@mail.gmail.com>


peter.maydell@linaro.org writes:

> On 5 November 2013 14:44, Jan Petrouš <jan.petrous@tieto.com> wrote:
>> Hehe, duno, but when I started learning QEMU the Integrator devboard
>> looked for me the nice start-up point = very simple to understand
>> and only very basic, but still core, device list.
>
> QEMU's integrator model is really very minimally maintained.
> A lot of its code is still using out of date ways of doing
> things and hasn't been updated in years; my only test case
> for it is an ancient 2.6.17 kernel. vexpress is rather
> more maintained and I do at least occasionally test with
> new kernels.
<snip>

I suspect it would be worth updating the QEMU wiki pages and building a
simple vexpress image (or showing simple steps for the Linaro vexpress
builds). I suspect Jan's choice was also influenced as mine by the fact
it's the test ARM image mentioned on the wiki page.

Of course the first time I ran it I found it had regressed also ;-)

-- 
Alex Bennée

  reply	other threads:[~2013-11-05 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 11:41 [Qemu-devel] [PATCH] integrator/cp: add support for REFCNT register Jan Petrouš
2013-11-05 13:54 ` Peter Maydell
2013-11-05 14:44   ` Jan Petrouš
2013-11-05 14:56     ` Peter Maydell
2013-11-05 16:18       ` Alex Bennée [this message]
2013-11-05 16:19         ` [Qemu-devel] [PATCH] integrator/cp: add support for REFCNTregisterr Peter Maydell
2013-11-06 12:13           ` Jan Petrouš

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=p1k3gm960d.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=jan.petrous@tieto.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.