From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Higdon Subject: Re: SCSI QLA not working on latest *-mm SN2 Date: Tue, 21 Sep 2004 15:54:05 -0700 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <20040921225405.GC147518@sgi.com> References: <200409211836.36367.jbarnes@engr.sgi.com> <20040921223954.GA147518@sgi.com> <200409211843.49312.jbarnes@engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from omx3-ext.sgi.com ([192.48.171.20]:64166 "EHLO omx3.sgi.com") by vger.kernel.org with ESMTP id S267324AbUIUWyS (ORCPT ); Tue, 21 Sep 2004 18:54:18 -0400 Content-Disposition: inline In-Reply-To: <200409211843.49312.jbarnes@engr.sgi.com> List-Id: linux-scsi@vger.kernel.org To: Jesse Barnes Cc: Andrew Vasquez , Matthew Wilcox , James Bottomley , Grant Grundler , pj@sgi.com, SCSI Mailing List , mdr@cthulhu.engr.sgi.com, jeremy@cthulhu.engr.sgi.com, djh@cthulhu.engr.sgi.com, Andrew Morton On Tue, Sep 21, 2004 at 06:43:49PM -0400, Jesse Barnes wrote: > On Tuesday, September 21, 2004 6:39 pm, Jeremy Higdon wrote: > > On Tue, Sep 21, 2004 at 06:36:36PM -0400, Jesse Barnes wrote: > > > > > > Shouldn't we do a config space read and *then* start the delay, which > > > will only delay for as long as it takes to reset the card on a 33 MHz > > > bus? > > > > The config space read has the same problem that the mmio space read does. > > The chip does not respond. > > Right, but config space reads are supposed to soft fail no matter what. So > we'll get back all ones, but we'll also know that the write has been received > by the device. We can start the delay regardless of the value the read > returns. I thought you said that config space read failures generate an MCA. Or are you going to fix that? jeremy