mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: jgarzik@mandrakesoft.com
Cc: linux-kernel@vger.kernel.org
Subject: 2.5.20 tulip bogosities
Date: Thu, 6 Jun 2002 18:24:13 +0200 (MET DST)	[thread overview]
Message-ID: <200206061624.SAA17598@harpo.it.uu.se> (raw)

With 2.5.19 tulip says the following for my 21143:

Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Found IRQ 5 for device 02:0a.0
tulip0:  EEPROM default media type Autosense.
tulip0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
tulip0:  MII transceiver #1 config 3000 status 782d advertising 01e1.
eth0: Digital DS21143 Tulip rev 65 at 0xd800, 00:40:C7:99:3A:5B, IRQ 5.

But 2.5.20 tulip now spews the following and then misidentifies
the NIC as a 21140:

Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Found IRQ 5 for device 02:0a.0
tulip0:  EEPROM default media type Autosense.
tulip0:  Index #0 - Media 100baseTx (#3) described by a 21140 non-MII (0) block.
tulip0:  Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
...
[136 lines deleted]
...
tulip0:  Index #139 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
tulip0:  Index #140 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
eth%d:  Invalid media table selection 255.
tulip0:  MII transceiver #1 config 3000 status 782d advertising 01e1.
eth0: Digital DS21140 Tulip rev 65 at 0xd800, 00:40:C7:99:3A:5B, IRQ 5.

Also note the obviously broken "eth%d" printk format string.

/Mikael

             reply	other threads:[~2002-06-06 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 16:24 Mikael Pettersson [this message]
2002-06-06 18:31 ` Jeff Garzik
2002-06-06 18:41   ` Patrick Mochel
2002-06-07 12:08     ` Alessandro Suardi
2002-06-07 17:04 ` Thunder from the hill
2002-06-07 17:17   ` Jeff Garzik
2002-06-06 20:26 Mikael Pettersson

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=200206061624.SAA17598@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®