From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6235 invoked by alias); 8 Jun 2009 10:56:21 -0000 Received: (qmail 6227 invoked by uid 22791); 8 Jun 2009 10:56:21 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from connor.medar.com (HELO connor.medar.com) (206.181.246.34) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 08 Jun 2009 10:56:15 +0000 Received: from [89.194.102.40] (win0040 [89.194.102.40]) by skynet.wtccorp.com (Postfix) with ESMTP id A8C173F; Mon, 8 Jun 2009 06:56:08 -0400 (EDT) Subject: Re: PowerPC Ethernet issue From: Robert Morse To: Edgar Grimberg Cc: ecos-devel@ecos.sourceware.org In-Reply-To: References: <1244215787.30295.28.camel@win0040> Content-Type: text/plain Date: Mon, 08 Jun 2009 10:56:00 -0000 Message-Id: <1244458362.31511.0.camel@win0040> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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/msg00016.txt.bz2 Thanks, That is what I thought I needed to do. Robert On Sat, 2009-06-06 at 17:30 +0200, Edgar Grimberg wrote: > Hi, > > > > > Looking at the situation, it seems like I would need to > > enable/configure the interrupts for the PHYs. and when a change of > > duplex is detected cause a reset of the MAC. Has anyone done anything > > like this before. Looking 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). > > > Does my idea seem sound, or am I off in the woods somewhere. I know > > about this duplex issue from another design. Where 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. So 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/powerpc/quicc2pro/current/src/tsec.c > > search for: > > tsec_eth_start > phy_dsr > phyAutoNegociate > > Best regards, > Edgar