linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: Stephan van Hienen <ultra@a2000.nu>
Cc: sparclinux@vger.kernel.org, "" <linux-kernel@vger.kernel.org>
Subject: Re: Alteon AceNIC Coper Seen as Fibre ? (and incorrect settings)
Date: 12 Dec 2002 17:00:02 -0500	[thread overview]
Message-ID: <m37keej3tp.fsf@trained-monkey.org> (raw)
In-Reply-To: Stephan van Hienen's message of "Tue, 10 Dec 2002 22:03:03 +0100 (CET)"

>>>>> "Stephan" == Stephan van Hienen <ultra@a2000.nu> writes:

Stephan> Sun UltraSparc 10 kernel 2.4.20

Stephan> eth2: Alteon AceNIC Gigabit Ethernet at 0x1ff02900000, irq
Stephan> 6,7d0 Tigon II (Rev. 6), Firmware: 12.4.11, MAC:
Stephan> 00:60:cf:20:92:fc PCI bus width: 32 bits, speed: 33MHz,
Stephan> latency: 64 clks eth2: Firmware up and running

Stephan> unplugging the utp cable, and plugging back in gives :

Stephan> eth2: 10/100BaseT link UP eth2: Optical link DOWN eth2:
Stephan> 10/100BaseT link UP

This is purely cosmetic. Basically the firmware sends a link down
event but not media info with it. At the time I wrote the code copper
cards weren't available and I just never got around to changing
it. It's trivial to fix, but really makes no difference whatsoever.

Jes

      parent reply	other threads:[~2002-12-12 21:57 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 21:03 Alteon AceNIC Coper Seen as Fibre ? (and incorrect settings) Stephan van Hienen
2002-12-10 21:16 ` Is this going to be true ? Serge Kuznetsov
2002-12-10 22:14   ` Herman Oosthuysen
2002-12-10 22:21     ` Serge Kuznetsov
2002-12-11  0:33       ` Michael Melanson
2002-12-11  0:55         ` David Schwartz
2002-12-11  1:04           ` Larry McVoy
2002-12-11 23:47     ` Henning P. Schmiedehausen
2002-12-11  0:05   ` Joseph D. Wagner
2002-12-11  1:08     ` Herman Oosthuysen
2002-12-11 15:55       ` Måns Rullgård
2002-12-11 16:33         ` Richard B. Johnson
2002-12-12  0:01           ` Henning P. Schmiedehausen
2002-12-12  3:16             ` Richard B. Johnson
2002-12-12  3:39               ` Mark Hamblin
2002-12-13  9:18               ` David Schwartz
2002-12-11 23:57         ` Henning P. Schmiedehausen
2002-12-12  9:22           ` Ragnar Hojland Espinosa
2002-12-12 14:15           ` Adam H. Pendleton
2002-12-12 21:24           ` Kjartan Maraas
2002-12-12  9:35         ` Helge Hafting
2002-12-11 13:41     ` Rik van Riel
2002-12-11 14:17       ` Måns Rullgård
2002-12-11 17:06     ` Serge Kuznetsov
2002-12-11 17:26       ` Roy Sigurd Karlsbakk
2002-12-11 22:01         ` john slee
2002-12-12 10:13           ` Måns Rullgård
2002-12-12 10:16         ` Måns Rullgård
2002-12-12 11:12           ` Henning P. Schmiedehausen
2002-12-12 13:19             ` Billy Harvey
2002-12-12 13:30               ` Henning P. Schmiedehausen
2002-12-13 10:56                 ` szonyi calin
2002-12-13 13:19                   ` Billy Harvey
2002-12-11 17:12     ` Serge Kuznetsov
2002-12-11 17:21       ` Alvaro Lopes
2002-12-12  6:50         ` Kai Henningsen
2002-12-11 17:29       ` Dave Jones
2002-12-11 17:18     ` Serge Kuznetsov
2002-12-11 13:38   ` Richard B. Johnson
2002-12-11 16:19     ` Alan Cox
2002-12-10 21:41 ` Alteon AceNIC Coper Seen as Fibre ? (and incorrect settings) Eric Weigle
2002-12-12 22:00 ` Jes Sorensen [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=m37keej3tp.fsf@trained-monkey.org \
    --to=jes@wildopensource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=ultra@a2000.nu \
    /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).