Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750905AbWJMPCc (ORCPT ); Fri, 13 Oct 2006 11:02:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751132AbWJMPCc (ORCPT ); Fri, 13 Oct 2006 11:02:32 -0400 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:29348 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1750905AbWJMPCb (ORCPT ); Fri, 13 Oct 2006 11:02:31 -0400 Subject: Re: [linux-pm] Bug in PCI core From: Alan Cox To: Alan Stern Cc: Adam Belay , Benjamin Herrenschmidt , Greg KH , linux-pci@atrey.karlin.mff.cuni.cz, Linux-pm mailing list , Kernel development list In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Fri, 13 Oct 2006 16:26:26 +0100 Message-Id: <1160753187.25218.52.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 849 Lines: 19 Ar Gwe, 2006-10-13 am 10:29 -0400, ysgrifennodd Alan Stern: > > I'd like to propose that we have the pci config sysfs interface return > > -EIO when it's blocked (e.g. active BIST or D3cold). This accurately > > reflects the state of the device to userspace, reduces complexity, and > > could potentially save some memory per PCI device instance. > > Could you resubmit your old patches and include a corresponding fix for > this access problem? And then you can fix the applications it breaks, like the X server which does actually want to know where all the devices are located in PCI space. Alan - 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/