linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Harald Küthe" <Harald.Kuethe@controlware.de>
To: <linuxppc-embedded@ozlabs.org>
Subject: [PATCH][PPC32] 2.4.27: fixes for 8xx fec.c
Date: Wed, 06 Oct 2004 08:26:43 +0200	[thread overview]
Message-ID: <s163ac5c.063@post2.controlware.de> (raw)

Hello, I sent this one some time ago.

I found two problems concerning the fast ethernet driver=20
for ppc 8xx processors (fec.c) in linux kernel version 2.4.26/27=20
and I think in the 2.6 series as well (not confirmed).

First problem is only when CONFIG_USE_MDIO is __not__ set.
How to reproduce:
start the system with fec ethernet, everything works,=20
issue a ifconfig ethX down and ifconfig ethX up and ethernet is not =
working anymore.
Fix (or at least a workaround). In fec_enet_open() add a fec_restart() at =
the end=20
if CONFIG_USE_MDIO is not set.

2nd problem is with CONFIG_USE_MDIO set:=20
The promiscuous mode/multicast settings are getting lost if link status =
changes occurs=20
How to reproduce:
build a bridge with the fec device. Then simply unplug and replug the =
ethernet cable.=20
fec_restart() is called which idles all promiscuous mode/multicast =
settings.
The bridge will then only forward broadcast frames because the promiscuous =
setting is lost.
Fix: call set_multicast_list(dev) at the end of fec_restart() before =
ethernet is reenabled.

If there are more questions please write back.

Reagrds
Harald

diff -urN linux-2.4.27.orig/arch/ppc/8xx_io/fec.c linux-2.4.27/arch/ppc/8xx=
_io/fec.c
--- linux-2.4.27.orig/arch/ppc/8xx_io/fec.c	2003-11-28 19:26:18.0000000=
00 +0100
+++ linux-2.4.27/arch/ppc/8xx_io/fec.c	2004-08-10 13:54:06.000000000 =
+0200
@@ -1466,6 +1466,8 @@
 	return -ENODEV;		/* No PHY we understand */
 #else
 	fep->link =3D 1;
+	/* after ifconfig down and up fec will not start -> restart it */
+	fec_restart (dev, 0);
 	netif_start_queue(dev);
 	return 0;	/* Success */
 #endif	/* CONFIG_USE_MDIO */
@@ -2049,6 +2051,9 @@
 	fecp->fec_imask =3D ( FEC_ENET_TXF | FEC_ENET_TXB |
 			    FEC_ENET_RXF | FEC_ENET_RXB | FEC_ENET_MII );
=20
+	/* set old promiscuous/multicast settings which are lost above */
+	set_multicast_list(dev);
+
 	/* And last, enable the transmit and receive processing.
 	*/
 	fecp->fec_ecntrl =3D FEC_ECNTRL_PINMUX | FEC_ECNTRL_ETHER_EN;

                 reply	other threads:[~2004-10-06  6:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=s163ac5c.063@post2.controlware.de \
    --to=harald.kuethe@controlware.de \
    --cc=linuxppc-embedded@ozlabs.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).