From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7016 invoked by alias); 6 Jun 2009 15:30:56 -0000 Received: (qmail 7004 invoked by uid 22791); 6 Jun 2009 15:30:54 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-fx0-f227.google.com (HELO mail-fx0-f227.google.com) (209.85.220.227) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 06 Jun 2009 15:30:48 +0000 Received: by fxm27 with SMTP id 27so2329035fxm.30 for ; Sat, 06 Jun 2009 08:30:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.53.143 with SMTP id m15mr4441976bkg.112.1244302244253; Sat, 06 Jun 2009 08:30:44 -0700 (PDT) In-Reply-To: <1244215787.30295.28.camel@win0040> References: <1244215787.30295.28.camel@win0040> Date: Sat, 06 Jun 2009 15:30:00 -0000 Message-ID: Subject: Re: PowerPC Ethernet issue From: Edgar Grimberg To: Robert Morse Cc: ecos-devel@ecos.sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2009-06/txt/msg00014.txt.bz2 Hi, > > =A0 =A0 =A0 =A0Looking at the situation, it seems like I would need to > enable/configure the interrupts for the PHYs. =A0and when a change of > duplex is detected cause a reset of the MAC. =A0Has anyone done anything > like this before. =A0Looking through the ethernet drivers and phy drivers > I do not see anyone doing this (I admit not all). > This looks like the only place to detect if the connection parameters have changed (link, duplex, speed). > =A0 =A0 =A0 =A0Does my idea seem sound, or am I off in the woods somewher= e. =A0I know > about this duplex issue from another design. =A0Where we had a commercial > rtos, that I found out they did not do this and caused a lot of issues, > I thought the device driver should of handled it, but they said it was > up to the application to control the bit. =A0So I do want to repeat the > same issue. I have some code so show that, but it might not fit your device. The idea is to stop and start the ethernet device in the PHY's DSR. In the start function, if the ethernet is not already started, you can renegotiate the connection parameters. The code is at: http://www.ecosforge.net/ecosforge/trunk/ecos_mpc8313/packages/devs/eth/pow= erpc/quicc2pro/current/src/tsec.c search for: tsec_eth_start phy_dsr phyAutoNegociate Best regards, Edgar