All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Greg KH <greg@kroah.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, 01 Oct 2007 11:10:57 -0400	[thread overview]
Message-ID: <47010E01.2010001@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710011656090.7567@jikos.suse.cz>

Jiri Kosina wrote:
> On Mon, 1 Oct 2007, Jeff Garzik wrote:
> 
>> There are other network devices that do not claim 
>> PCI_CLASS_NETWORK_ETHERNET either.  
> 
> Nor any other PCI_CLASS_NETWORK subclass?

Correct.


>> Since this is a purely cosmetic issue -- said userland tools would need 
>> to support weird cases _anyway_ -- I am not inclined to apply the patch.
> 
> What would you recommend as a method for userspace to detect whether given 
> hardware is a network card, supposing that there is no driver bound to it 
> yet?

Note the mention of "weird cases"

You come up with a general method, then you have to deal with exceptions 
to that general method.

Another example:  8139too and 8139cp both claim to support 
(0x10EC,0x8139) PCI IDs.  The distro installer needs additional 
information to know to read the PCI revision, which is what determines 
whether or not to use 8139cp driver.

Sometimes life is just not as simple as you would like it to be :)

	Jeff


  reply	other threads:[~2007-10-01 15:11 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 [this message]
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

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=47010E01.2010001@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=aabdulla@nvidia.com \
    --cc=greg@kroah.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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.