From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Martin Mares <mj@ucw.cz>
Cc: Adam Belay <abelay@MIT.EDU>,
Alan Stern <stern@rowland.harvard.edu>, Greg KH <greg@kroah.com>,
linux-pci@atrey.karlin.mff.cuni.cz,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Bug in PCI core
Date: Fri, 13 Oct 2006 22:25:50 +1000 [thread overview]
Message-ID: <1160742350.4792.257.camel@localhost.localdomain> (raw)
In-Reply-To: <mj+md-20061013.093014.26714.atrey@ucw.cz>
On Fri, 2006-10-13 at 11:31 +0200, Martin Mares wrote:
> Hi!
>
> > For example, currently, if I power off the ethernet of my mac, or the
> > firewire chip (which are powered off if the module isn't loaded), lspci
> > will get the device id and vendor id right ... but won't get the class
> > code.
>
> Ehm, you aren't using any recent pciutils, are you? ;-)
Whatever came with the distro that complained about the problem back
then :) I agree that the problem is fixed on the kernel level (sysfs)
and I'm happy to hear that pciutils is fixed too :) So we can probably
do what Adam suggest and just return errors or ff's
Ben.
next prev parent reply other threads:[~2006-10-13 12:25 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 20:41 Bug in PCI core Alan Stern
2006-10-13 1:01 ` [linux-pm] " Benjamin Herrenschmidt
2006-10-13 8:50 ` Adam Belay
2006-10-13 8:50 ` [linux-pm] " Adam Belay
2006-10-13 9:16 ` Benjamin Herrenschmidt
2006-10-13 9:16 ` [linux-pm] " Benjamin Herrenschmidt
2006-10-13 9:31 ` Martin Mares
2006-10-13 9:31 ` [linux-pm] " Martin Mares
2006-10-13 12:25 ` Benjamin Herrenschmidt [this message]
2006-10-13 14:29 ` Alan Stern
2006-10-13 14:29 ` [linux-pm] " Alan Stern
2006-10-13 15:26 ` Alan Cox
2006-10-13 15:29 ` Arjan van de Ven
2006-10-13 16:06 ` Alan Cox
2006-10-13 16:34 ` Adam Belay
2006-10-13 16:34 ` [linux-pm] " Adam Belay
2006-10-13 16:36 ` Matthew Wilcox
2006-10-13 17:09 ` Alan Cox
2006-10-13 17:09 ` [linux-pm] " Alan Cox
2006-10-13 16:49 ` Matthew Wilcox
2006-10-13 16:49 ` [linux-pm] " Matthew Wilcox
2006-10-13 17:34 ` Alan Cox
2006-10-13 17:34 ` [linux-pm] " Alan Cox
2006-10-13 17:13 ` Arjan van de Ven
2006-10-13 17:13 ` [linux-pm] " Arjan van de Ven
2006-10-13 17:57 ` Alan Stern
2006-10-13 17:57 ` [linux-pm] " Alan Stern
2006-10-13 19:18 ` Matthew Wilcox
2006-10-13 20:59 ` Alan Stern
2006-10-13 20:59 ` [linux-pm] " Alan Stern
2006-10-13 19:30 ` Adam Belay
2006-10-13 19:30 ` [linux-pm] " Adam Belay
2006-10-13 23:00 ` Benjamin Herrenschmidt
2006-10-13 23:00 ` [linux-pm] " Benjamin Herrenschmidt
2006-10-14 2:33 ` Alan Stern
2006-10-14 2:33 ` [linux-pm] " Alan Stern
2006-10-14 3:04 ` Roland Dreier
2006-10-14 3:04 ` Roland Dreier
2006-10-14 3:07 ` Matthew Wilcox
2006-10-14 3:19 ` Bill Randle
2006-10-14 3:19 ` [linux-pm] " Bill Randle
2006-10-14 5:47 ` Greg KH
2006-10-14 5:47 ` [linux-pm] " Greg KH
2006-10-13 17:01 ` Adam Belay
2006-10-13 17:01 ` [linux-pm] " Adam Belay
2006-10-13 16:40 ` Adam Belay
2006-10-13 16:40 ` [linux-pm] " Adam Belay
2006-10-13 20:48 ` Pavel Machek
2006-10-14 5:34 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1160742350.4792.257.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=abelay@MIT.EDU \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux-pm@lists.osdl.org \
--cc=mj@ucw.cz \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.