From: Daniel Drake <dsd@gentoo.org>
To: Jon Mason <jdmason@us.ibm.com>
Cc: mulix@mulix.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: pcnet32 devices with incorrect trident vendor ID
Date: Thu, 12 Jan 2006 20:49:42 +0000 [thread overview]
Message-ID: <43C6C0E6.7030705@gentoo.org> (raw)
In-Reply-To: <20060112175051.GA17539@us.ibm.com>
Jon Mason wrote:
> Some pcnet32 hardware erroneously has the Vendor ID for Trident. The
> pcnet32 driver looks for the PCI ethernet class before grabbing the
> hardware, but the current trident driver does not check against the
> PCI audio class. This allows the trident driver to claim the pcnet32
> hardware. This patch prevents that.
On the subject of pcnet32 and the invalid vendor ID, you may find this
interesting:
http://forums.gentoo.org/viewtopic-t-420013-highlight-trident.html
The user saw the correct vendor ID (AMD) in 2.4, but when upgrading to
2.6, it changed to Trident.
I guess this is still likely to be a hardware bug, but it demonstrates
that the Linux PCI layer has something to do with it (even if it is just
triggering it somehow).
Daniel
next parent reply other threads:[~2006-01-12 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060112175051.GA17539@us.ibm.com>
2006-01-12 20:49 ` Daniel Drake [this message]
2006-01-12 20:57 ` pcnet32 devices with incorrect trident vendor ID Matthew Wilcox
2006-01-12 21:03 ` Daniel Drake
2006-01-12 21:05 ` Matthew Wilcox
2006-01-12 21:22 ` Bill Nottingham
2006-01-12 21:24 ` Bill Nottingham
2006-01-12 22:23 ` Don Fry
2006-01-12 22:33 ` Jon Mason
2006-01-12 21:05 ` Lennart Sorensen
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=43C6C0E6.7030705@gentoo.org \
--to=dsd@gentoo.org \
--cc=jdmason@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mulix@mulix.org \
--cc=netdev@vger.kernel.org \
/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).