From: Ondrej Zary <linux@rainbow-software.org>
To: Samuel Chessman <chessman@tux.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] tlan: Enable link monitoring
Date: Fri, 16 May 2014 20:59:17 +0200 [thread overview]
Message-ID: <201405162059.17456.linux@rainbow-software.org> (raw)
In-Reply-To: <1400263230-2599-2-git-send-email-linux@rainbow-software.org>
On Friday 16 May 2014 20:00:30 Ondrej Zary wrote:
> Enable old link monitoring code and modify it:
> - control LINK LED
> - use separate timer so it does not interfere with ACT LED
> - reset adapter on link loss to restart autonegotiation
> (required to switch between 10/100 Mbps on OC-2326)
Oops, sorry. This part is broken - the link comes up properly but no packets
can be transferred then.
--
Ondrej Zary
prev parent reply other threads:[~2014-05-16 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 18:00 [PATCH 1/2] tlan: Enable activity LED on Olicom OC-2325 and OC-2326 Ondrej Zary
2014-05-16 18:00 ` [PATCH 2/2] tlan: Enable link monitoring Ondrej Zary
2014-05-16 18:59 ` Ondrej Zary [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=201405162059.17456.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=chessman@tux.org \
--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;
as well as URLs for NNTP newsgroup(s).