public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Luethi <rl@hellgate.ch>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Denis Vlasenko <vda@ilport.com.ua>,
	Patrick Draper <pdraper@gmail.com>,
	Udo van den Heuvel <udovdh@xs4all.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: VIA Rhine ethernet driver bug (reprise...)
Date: Fri, 26 Aug 2005 11:04:12 +0200	[thread overview]
Message-ID: <20050826090412.GA20288@k3.hellgate.ch> (raw)
In-Reply-To: <430EC985.6040307@pobox.com>

On Fri, 26 Aug 2005 03:49:25 -0400, Jeff Garzik wrote:
> Denis Vlasenko wrote:
> >May be a known problem. A buglet in MII common code.
> >Via-rhine maintainer knows about it, as does Jeff.
> 
> You don't speak for me, sir.
> 
> I know of no such problem.  Please submit a report and/or patch.

I believe vda may have been referring to this. I can send you the
original thread if it's not in your mail archive.

Roger

------------------------------ cut here ------------------------------
From: Roger Luethi <rl@hellgate.ch>
Subject: Re: via-rhine + link loss + autoneg off == trouble
To: Denis Vlasenko <vda@ilport.com.ua>, Jeff Garzik <jgarzik@pobox.com>
Cc: "David S. Miller" <davem@davemloft.net>, linux-net@vger.kernel.org,
        linux-kernel@vger.kernel.org
Date: Sat, 13 Aug 2005 20:34:21 +0200
User-Agent: Mutt/1.5.8i

Jeff, can you tune in for a moment?

First of all, many thanks to vda for tracking this down, and to everyone
else who helped with it.

I had a look at my code and at 8139cp (which is one of only a handful
of drivers that have been converted to use the generic MII stuff).

Turns out 8139cp doesn't seem to do anything to address the problem
vda described, either, so it is equally affected. Is this something we
should fix in mii.c, or is mii_check_media working as designed? Btw,
I'd be thrilled if someone wrote a few lines per function in mii.c:
purpose, preconditions, side effects, something along these lines.

Roger
------------------------------ cut here ------------------------------


  reply	other threads:[~2005-08-26  9:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 17:29 VIA Rhine ethernet driver bug (reprise...) Udo van den Heuvel
2005-08-23  9:21 ` Denis Vlasenko
2005-08-24 15:50   ` Lee Revell
2005-08-24 16:03     ` Lee Revell
     [not found]   ` <6981e08b0508252043139cfa2d@mail.gmail.com>
2005-08-26  6:33     ` Denis Vlasenko
2005-08-26  7:49       ` Jeff Garzik
2005-08-26  9:04         ` Roger Luethi [this message]
2005-10-04 15:19           ` Jeff Garzik
2005-08-26 10:04         ` Denis Vlasenko

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=20050826090412.GA20288@k3.hellgate.ch \
    --to=rl@hellgate.ch \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pdraper@gmail.com \
    --cc=udovdh@xs4all.nl \
    --cc=vda@ilport.com.ua \
    /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