From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757869AbYDHUEq (ORCPT ); Tue, 8 Apr 2008 16:04:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755237AbYDHUEf (ORCPT ); Tue, 8 Apr 2008 16:04:35 -0400 Received: from palinux.external.hp.com ([192.25.206.14]:45167 "EHLO mail.parisc-linux.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754594AbYDHUEf (ORCPT ); Tue, 8 Apr 2008 16:04:35 -0400 Date: Tue, 8 Apr 2008 14:04:18 -0600 From: Matthew Wilcox To: Ingo Molnar Cc: "Brandeburg, Jesse" , "Kok, Auke-jan H" , Linux Kernel Mailing List , NetDev , e1000-list , linux-pci maillist , Jeff Garzik , Andrew Morton , "David S. Miller" , Linus Torvalds , "Ronciak, John" , "Allan, Bruce W" , Greg KH , Arjan van de Ven , "Rafael J. Wysocki" Subject: Re: [regression] e1000e broke e1000 (was: Re: [ANNOUNCE] e1000 toe1000e migration of PCI Express devices) Message-ID: <20080408200417.GI11962@parisc-linux.org> References: <47F69965.7030303@intel.com> <20080408083606.GA20863@elte.hu> <47FB9ABB.9080403@intel.com> <20080408183921.GA20803@elte.hu> <36D9DB17C6DE9E40B059440DB8D95F5204E2A55C@orsmsx418.amr.corp.intel.com> <20080408195949.GB28148@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080408195949.GB28148@elte.hu> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 08, 2008 at 09:59:49PM +0200, Ingo Molnar wrote: > Btw., a sidenote: this is another generally annoying property of Linux: > there's no easy and user-visible enumeration of PCI IDs (devices) that > we _could_ support but dont enable for some reason. It is a royal PITA > to track down when some driver decides to (silently) ignore a piece of > hardware. > > Having a seemingly dead piece of hardware component is one of the most > frustrating user experiences possible - the first instinctive reaction > is "did my hw break???". The kernel should proactively know about all > inactive pieces of hardware and should have a one-stop-shop for users > where they can reassure themselves which devices are not active and why. It's almost trivial to add new string attributes to sysfs. We could have a file, say, /sys/bus/pci/devices/0000:07:03.0/broken which lspci could read to see if anything's left a message for us. Is that the kind of thing you had in mind? -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step."