From: Tommy Christensen <tommy.christensen@tpack.net>
To: Bogdan Costescu <Bogdan.Costescu@iwr.uni-heidelberg.de>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH] 3c59x: read current link status from phy
Date: Thu, 08 Sep 2005 15:05:00 +0200 [thread overview]
Message-ID: <1126184700.4805.32.camel@tsc-6.cph.tpack.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0509081351160.21354@dingo.iwr.uni-heidelberg.de>
On Thu, 2005-09-08 at 13:58, Bogdan Costescu wrote:
> Can the original poster give an explanation ? I've enjoyed a rather
> well functioning 3c59x driver for the past ~6 years without such
> double reading. Plus:
> - this operation is I/O expensive
> - it is performed inside a region protected by a spinlock
> - it is performed often, every 60 seconds
>
> Is there some specific hardware that exhibits a problem that is solved
> by this double reading ?
Nothing critical. The idea is to avoid an extra delay of 60 seconds
before detecting link-up.
Please see http://bugzilla.kernel.org/show_bug.cgi?id=5025
-Tommy
next prev parent reply other threads:[~2005-09-08 13:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200509080125.j881PcL9015847@hera.kernel.org>
2005-09-08 1:49 ` Jeff Garzik
2005-09-08 11:58 ` Bogdan Costescu
2005-09-08 13:05 ` Tommy Christensen [this message]
2005-09-08 13:35 ` Bogdan Costescu
2005-09-08 14:42 ` Tommy Christensen
2005-09-08 15:42 ` Bogdan Costescu
2005-09-08 18:56 ` Andy Fleming
2005-09-09 10:10 ` Bogdan Costescu
2005-09-09 18:08 ` Andy Fleming
2005-09-08 22:39 ` Tommy Christensen
2005-09-08 22:41 ` Andrew Morton
2005-09-08 23:12 ` Tommy Christensen
2005-09-09 0:01 ` Jeff Garzik
2005-09-09 1:08 ` John W. Linville
2005-09-09 7:34 ` Tommy Christensen
2005-09-09 7:44 ` Andrew Morton
2005-09-09 11:35 ` Neil Horman
2005-09-08 14:13 ` [PATCH] 3c59x: cleanup of mdio_read routines to use MII_* macros in include/linux/mii.h Neil Horman
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=1126184700.4805.32.camel@tsc-6.cph.tpack.net \
--to=tommy.christensen@tpack.net \
--cc=Bogdan.Costescu@iwr.uni-heidelberg.de \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®