From: Brandon Philips <brandon@ifup.org>
To: David Miller <davem@davemloft.net>
Cc: grundler@google.com, 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 14:22:20 -0800 [thread overview]
Message-ID: <20091130222219.GA8073@jenkins.domain_not_set.invalid> (raw)
In-Reply-To: <20091130.122642.113956563.davem@davemloft.net>
On 12:26 Mon 30 Nov 2009, David Miller wrote:
> 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.
>
> subsystem-id: 0000434e
> subsystem-vendor-id: 00004554
>
> Hmmm, what vendor is '0x4554'? :-)
Whoever it is it is the same as the expansion card on non-sparc
boards: SubVendor: pci 0x4554 [1]
Hrm, dead end I guess.
Cheers,
Brandon
[1] https://bugzilla.novell.com/show_bug.cgi?id=537016#c5
next prev parent reply other threads:[~2009-11-30 22:22 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
2009-11-30 22:22 ` Brandon Philips [this message]
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=20091130222219.GA8073@jenkins.domain_not_set.invalid \
--to=brandon@ifup.org \
--cc=davem@davemloft.net \
--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).