[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47FBD1AD.1080700@isomerica.net>
Date: Tue, 08 Apr 2008 16:12:29 -0400
From: Dan Noe <dpn@...merica.net>
To: Matthew Wilcox <matthew@....cx>
CC: Ingo Molnar <mingo@...e.hu>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
"Kok, Auke-jan H" <auke-jan.h.kok@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
NetDev <netdev@...r.kernel.org>,
e1000-list <e1000-devel@...ts.sourceforge.net>,
linux-pci maillist <linux-pci@...ey.karlin.mff.cuni.cz>,
Jeff Garzik <jeff@...zik.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Ronciak, John" <john.ronciak@...el.com>,
"Allan, Bruce W" <bruce.w.allan@...el.com>,
Greg KH <greg@...ah.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [regression] e1000e broke e1000
Matthew Wilcox wrote:
> 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?
I would consider this a worthwhile addition to the kernel (and lspci).
It would be nice if lspci could display what driver had claimed a
particular device, and which devices were unclaimed by any driver or
otherwise had an error that prevented initialization.
I don't have enough experience to gauge how invasive this would be, but
I'd be happy to contribute towards it if practical.
Cheers,
Dan
--
/--------------- - - - - - -
| Daniel Noe
| http://isomerica.net/~dpn/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists