From: Greg KH <greg@kroah.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Jiri Kosina <jkosina@suse.cz>, Jeff Garzik <jgarzik@pobox.com>,
Ayaz Abdulla <aabdulla@nvidia.com>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: nVidia's MCP61 ethernet card needs quirk for wrong class
Date: Mon, 1 Oct 2007 10:15:43 -0700 [thread overview]
Message-ID: <20071001171543.GA6653@kroah.com> (raw)
In-Reply-To: <20071001170337.GJ12049@parisc-linux.org>
On Mon, Oct 01, 2007 at 11:03:38AM -0600, Matthew Wilcox wrote:
> On Mon, Oct 01, 2007 at 09:25:46AM -0700, Greg KH wrote:
> > For config items, we don't want to modify them in any way, we just want
> > to pass-through the data direct from the device. Look at the sysfs and
> > proc files for pci config spaces. They are returning binary data stored
> > in the device directly. We do not want to have to start modifying that
> > data directly just to handle messed up devices like this.
>
> Nobody's talking about changing the raw pci data. What we're talking
> about is changing the value read out of
>
> $ cat /sys/bus/pci/devices/0000\:00\:00.0/class
> 0x060000
I know, but the next request will be to also fix up those raw values as
someone will have a tool that only uses them :)
> We do tweak at least some of the other similar values (vendor, for sure)
> to work around bugs; not sure we have an example for changing the class
> value yet.
>
> pciutils knows that the kernel has potentially fixed up the values in
> the individual files, and to trust those over the raw data.
Ah, cool, I didn't realize that pciutils handled this kind of mismatch.
That's good to know.
thanks,
greg k-h
prev parent reply other threads:[~2007-10-01 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 14:20 [PATCH] PCI: nVidia's MCP61 ethernet card needs quirk for wrong class Jiri Kosina
2007-10-01 14:46 ` Jeff Garzik
2007-10-01 14:50 ` Jiri Kosina
2007-10-01 14:54 ` Jeff Garzik
2007-10-01 15:01 ` Jiri Kosina
2007-10-01 15:10 ` Jeff Garzik
2007-10-01 15:24 ` Jiri Kosina
2007-10-01 16:25 ` Greg KH
2007-10-01 17:03 ` Matthew Wilcox
2007-10-01 17:15 ` Greg KH [this message]
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=20071001171543.GA6653@kroah.com \
--to=greg@kroah.com \
--cc=aabdulla@nvidia.com \
--cc=jgarzik@pobox.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=matthew@wil.cx \
/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.