netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: grundler@google.com
Cc: brandon@ifup.org, tobias@ringis.se, kyle@mcmartin.ca,
	netdev@vger.kernel.org, grundler@parisc-linux.org
Subject: Re: dmfe/tulip device id overlap
Date: Mon, 30 Nov 2009 12:26:42 -0800 (PST)	[thread overview]
Message-ID: <20091130.122642.113956563.davem@davemloft.net> (raw)
In-Reply-To: <da824cf30911300914p2d08b87cr4625e9bc30ec7e5b@mail.gmail.com>

From: Grant Grundler <grundler@google.com>
Date: Mon, 30 Nov 2009 09:14:01 -0800

> Has anyone posted "lspci -v" output for the "Netra X1 and Sunfire
> V100" motherboards?
> 
> I'm asking because I'm hoping it's possible to disambiguate the add-on
> cards from
> LAN-on-Motherboard cases by looking at subsystem vendor and device IDs as well.

I think more likely OF properties will help here.

Have a look at:

	git://git.kernel.org/pub/scm/linux/kernel/git/davem/prtconfs.git

In particular 'v100' which has a network device OF node with properties:

        Node 0xf007fae8
            .node:  f007fae8
            local-mac-address:  0003ba11.b371
            assigned-addresses:  81006010.00000000.00010000.00000000.00000100.82006014.00000000.00000000.00000000.00002000.82006030.00000000.00040000.00000000.00040000
            version: '1.0'
            compatible:  70636934.3535342c.34333465.00706369.31323868.2c393130.32007063.69313238.322c3931.30320070.6369636c.6173732c.30323030.303000
            device_type: 'network'
            subsystem-id:  0000434e
            subsystem-vendor-id:  00004554
            reg:  00006000.00000000.00000000.00000000.00000000.01006010.00000000.00000000.00000000.00000100.02006014.00000000.00000000.00000000.00000100
            name: 'ethernet'
            devsel-speed:  00000001
            class-code:  00020000
            interrupts:  00000001
            max-latency:  00000028
            min-grant:  00000014
            revision-id:  00000031
            device-id:  00009102
            vendor-id:  00001282

Hmmm, what vendor is '0x4554'? :-)

  reply	other threads:[~2009-11-30 20:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25  4:36 dmfe/tulip device id overlap Brandon Philips
2009-11-25  4:49 ` Brandon Philips
2009-11-25 17:24   ` Grant Grundler
2009-11-29  8:30     ` David Miller
2009-11-30  6:55       ` Brandon Philips
2009-11-30  7:07         ` David Miller
2009-11-30 12:46           ` Ben Hutchings
2009-11-30 20:21             ` David Miller
2009-11-30 17:14         ` Grant Grundler
2009-11-30 20:26           ` David Miller [this message]
2009-11-30 22:22             ` Brandon Philips
2009-11-30 22:29               ` David Miller
2009-12-29 18:22                 ` [PATCH] dmfe/tulip: Let dmfe handle DM910x except for SPARC on-board chips Ben Hutchings
2009-12-29 18:41                   ` Grant Grundler
2010-01-04  5:36                     ` David Miller
2009-11-25 13:08 ` dmfe/tulip device id overlap Ben Hutchings

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=20091130.122642.113956563.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=brandon@ifup.org \
    --cc=grundler@google.com \
    --cc=grundler@parisc-linux.org \
    --cc=kyle@mcmartin.ca \
    --cc=netdev@vger.kernel.org \
    --cc=tobias@ringis.se \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).