From: Peter Maydell <peter.maydell@linaro.org>
To: Rob Landley <rob@landley.net>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
qemu-devel@nongnu.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Guenter Roeck <linux@roeck-us.net>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+
Date: Tue, 13 Aug 2013 10:12:59 +0100 [thread overview]
Message-ID: <CAFEAcA_KJwzefBH0St2vbGd9gaWsVL9jdrGRBJU9wx2-kuo1vA@mail.gmail.com> (raw)
In-Reply-To: <1376383051.2737.20@driftwood>
On 13 August 2013 09:37, Rob Landley <rob@landley.net> wrote:
> Peter says he knows somebody who knows somebody who dug some instance of
> this hardware out of some landfill or something.
No, I personally myself had the hardware. Really.
> Me, I want to get something that works on new qemu _and_ last year's
> qemu, and that's what I got.
Note that in general hoping that current mainline kernel will
always work with ancient QEMU is a losing proposition -- it is
always possible that a kernel improvement will trigger a latent
model bug in QEMU. (To pick a random example, some while ago fixes
to how the kernel dealt with BGR and RGB pixel formats on the
versatile board broke QEMU because we weren't modelling it right;
that was just a QEMU bug for which the fix is "get a newer QEMU".)
The back-compat in the PCI code is so that the older kernels (2.6.x)
will continue to work, which is not quite the same thing.
-- PMM
next prev parent reply other threads:[~2013-08-13 9:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5207B3C3.9080508@roeck-us.net>
[not found] ` <20130811220450.GY23006@n2100.arm.linux.org.uk>
2013-08-12 0:40 ` [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+ Guenter Roeck
2013-08-12 16:24 ` Peter Maydell
2013-08-12 16:45 ` Russell King - ARM Linux
2013-08-12 17:33 ` Peter Maydell
2013-08-12 20:06 ` Russell King - ARM Linux
2013-08-12 20:49 ` Peter Maydell
2013-08-12 21:21 ` Russell King - ARM Linux
2013-08-12 21:36 ` Peter Maydell
2013-08-12 22:12 ` Russell King - ARM Linux
2013-08-12 22:48 ` Guenter Roeck
2013-08-12 23:04 ` Guenter Roeck
2013-08-14 10:33 ` Russell King - ARM Linux
2013-08-14 12:44 ` Peter Maydell
2013-08-14 12:49 ` Russell King - ARM Linux
2013-08-14 12:56 ` Peter Maydell
2013-08-14 14:41 ` Guenter Roeck
2013-08-14 15:26 ` [Qemu-devel] memory reads and writes Herbei Dacian
2013-08-12 17:48 ` [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+ Peter Maydell
2013-08-13 8:37 ` Rob Landley
2013-08-13 9:12 ` Peter Maydell [this message]
2013-08-13 11:30 ` Russell King - ARM Linux
2013-08-13 3:40 ` Guenter Roeck
2013-08-15 16:45 ` Peter Maydell
2013-08-15 17:54 ` Guenter Roeck
2013-08-15 18:05 ` Peter Maydell
2013-08-15 18:39 ` Guenter Roeck
2013-08-15 20:50 ` Guenter Roeck
2013-08-15 21:49 ` Peter Maydell
2013-08-15 22:18 ` Guenter Roeck
2013-08-15 22:23 ` Peter Maydell
2013-08-15 23:25 ` Guenter Roeck
2013-08-19 15:26 ` Guenter Roeck
2013-08-12 19:02 ` Paul Gortmaker
2013-08-12 20:58 ` Peter Maydell
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=CAFEAcA_KJwzefBH0St2vbGd9gaWsVL9jdrGRBJU9wx2-kuo1vA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@roeck-us.net \
--cc=paul.gortmaker@windriver.com \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).