From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: [PATCH 2/2] [TULIP] Check the return value from pci_set_mwi() Date: Fri, 6 Oct 2006 13:28:42 -0600 Message-ID: <20061006192842.GO2563@parisc-linux.org> References: <1160161519800-git-send-email-matthew@wil.cx> <11601615192857-git-send-email-matthew@wil.cx> <4526AB43.7030809@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Val Henson , Greg Kroah-Hartman , netdev@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org, David Miller Return-path: Received: from palinux.external.hp.com ([192.25.206.14]:21670 "EHLO mail.parisc-linux.org") by vger.kernel.org with ESMTP id S1422650AbWJFT2n (ORCPT ); Fri, 6 Oct 2006 15:28:43 -0400 To: Jeff Garzik Content-Disposition: inline In-Reply-To: <4526AB43.7030809@garzik.org> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Fri, Oct 06, 2006 at 03:15:15PM -0400, Jeff Garzik wrote: > Matthew Wilcox wrote: > >Also, pci_set_mwi() will fail if the cache line > >size is 0, so we don't need to check that ourselves any more. > > NAK, not true on all arches. sparc64 at least presumes that the > firmware DTRT with cacheline size, which hurts us now given this tulip patch How does it hurt us? int pcibios_prep_mwi(struct pci_dev *dev) { /* We set correct PCI_CACHE_LINE_SIZE register values for every * device probed on this platform. So there is nothing to check * and this always succeeds. */ return 0; } If Dave's wrong about that, it hurts him, not us ;-) It's still not necessary for the Tulip driver to check.