Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762515AbYBWLhh (ORCPT ); Sat, 23 Feb 2008 06:37:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750838AbYBWLh3 (ORCPT ); Sat, 23 Feb 2008 06:37:29 -0500 Received: from einhorn.in-berlin.de ([192.109.42.8]:54172 "EHLO einhorn.in-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750831AbYBWLh2 (ORCPT ); Sat, 23 Feb 2008 06:37:28 -0500 X-Envelope-From: stefanr@s5r6.in-berlin.de Date: Sat, 23 Feb 2008 12:36:33 +0100 (CET) From: Stefan Richter Subject: Re: [PATCH 1/2] firewire: endianess fix To: linux1394-devel@lists.sourceforge.net cc: Harvey Harrison , Sam Ravnborg , linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org, linuxppc-dev@ozlabs.org, Kristian Hoegsberg , Jarod Wilson In-Reply-To: Message-ID: References: <20080220220326.GA22328@uranus.ravnborg.org> <1203545913.25307.47.camel@brick> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 718 Lines: 20 I wrote: > If possible, also test whether the device remains accessible after > forcing a bus reset, e.g. by "echo br short > firecontrol". "echo br short | firecontrol" of course. This test should actually not really be necessary because simply plugging the SBP-2 device in should already cause enough generation changes for the code to trip over an endianess bug before or after thhe patch, me thinks. -- Stefan Richter -=====-==--- --=- =-=== http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/