From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756243Ab3HMJNW (ORCPT ); Tue, 13 Aug 2013 05:13:22 -0400 Received: from mail-lb0-f171.google.com ([209.85.217.171]:56529 "EHLO mail-lb0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753818Ab3HMJNV (ORCPT ); Tue, 13 Aug 2013 05:13:21 -0400 MIME-Version: 1.0 In-Reply-To: <1376383051.2737.20@driftwood> References: <20130812164548.GE23006@n2100.arm.linux.org.uk> <1376383051.2737.20@driftwood> From: Peter Maydell Date: Tue, 13 Aug 2013 10:12:59 +0100 Message-ID: Subject: Re: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+ To: Rob Landley Cc: Russell King - ARM Linux , Guenter Roeck , Paul Gortmaker , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , qemu-devel@nongnu.org, Arnd Bergmann Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13 August 2013 09:37, Rob Landley 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56566) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9AfQ-0004M6-2x for qemu-devel@nongnu.org; Tue, 13 Aug 2013 05:13:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V9AfI-0001Jw-Jg for qemu-devel@nongnu.org; Tue, 13 Aug 2013 05:13:28 -0400 Received: from mail-lb0-f169.google.com ([209.85.217.169]:41383) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9AfI-0001Jp-Dk for qemu-devel@nongnu.org; Tue, 13 Aug 2013 05:13:20 -0400 Received: by mail-lb0-f169.google.com with SMTP id u10so5608142lbi.14 for ; Tue, 13 Aug 2013 02:13:19 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1376383051.2737.20@driftwood> References: <20130812164548.GE23006@n2100.arm.linux.org.uk> <1376383051.2737.20@driftwood> From: Peter Maydell Date: Tue, 13 Aug 2013 10:12:59 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+ List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rob Landley Cc: Russell King - ARM Linux , "linux-kernel@vger.kernel.org" , qemu-devel@nongnu.org, Paul Gortmaker , Guenter Roeck , Arnd Bergmann , "linux-arm-kernel@lists.infradead.org" On 13 August 2013 09:37, Rob Landley 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: peter.maydell@linaro.org (Peter Maydell) Date: Tue, 13 Aug 2013 10:12:59 +0100 Subject: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+ In-Reply-To: <1376383051.2737.20@driftwood> References: <20130812164548.GE23006@n2100.arm.linux.org.uk> <1376383051.2737.20@driftwood> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 13 August 2013 09:37, Rob Landley 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