public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Matt <madmatt@bits.bris.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: My 3c980 is misdetected
Date: Thu, 08 Nov 2001 09:54:44 -0800	[thread overview]
Message-ID: <3BEAC6E4.7722DB17@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.21.0111080916480.20023-100000@bits.bris.ac.uk>

Matt wrote:
> 
> More NIC-related queries,
> 
> Under the 2.4.13 kernel, the 3c59x.o driver misdetects my 3c980 as a 3c982
> (the dual port version of what I assume is the same card):
> 
> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> 00:09.0: 3Com PCI 3c982 Dual Port Server Cyclone at 0xdc00. Vers LK1.1.16
> 
> Here is the output of lspci -v:
> 
> 00:09.0 Ethernet controller: 3Com Corporation: Unknown device 9805 (rev 78)
>         Subsystem: 3Com Corporation: Unknown device 1000
>         Flags: bus master, medium devsel, latency 32, IRQ 10
>         I/O ports at dc00 [size=128]
>         Memory at db000000 (32-bit, non-prefetchable) [size=128]
>         Expansion ROM at <unassigned> [disabled] [size=128K]
>         Capabilities: [dc] Power Management version 2
> 
> It all seems to work fine, but I was wondering if this might cause a
> hiccup anywhere? 2.2.19 identified my card correctly, and I have some
> earlier 3c980 models in another box still running 2.2.19, which get
> detected correctly too:
> 

No, that's OK - it's just the identification string which is
incorrect.  I was "updating" the ID strings from the latest Becker
driver and one of us got it wrong...

      reply	other threads:[~2001-11-08 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08  9:28 My 3c980 is misdetected Matt
2001-11-08 17:54 ` Andrew Morton [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=3BEAC6E4.7722DB17@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madmatt@bits.bris.ac.uk \
    /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