From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28199 invoked by alias); 15 Jun 2004 18:01:48 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 28185 invoked from network); 15 Jun 2004 18:01:46 -0000 Received: from unknown (HELO web41304.mail.yahoo.com) (66.218.93.53) by sourceware.org with SMTP; 15 Jun 2004 18:01:46 -0000 Message-ID: <20040615180137.6404.qmail@web41304.mail.yahoo.com> Received: from [67.96.253.254] by web41304.mail.yahoo.com via HTTP; Tue, 15 Jun 2004 11:01:37 PDT Date: Tue, 15 Jun 2004 18:01:00 -0000 From: agyhoo To: ecos-discuss@ecos.sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [ECOS] possible bug in if_fcc ethernet driver? X-SW-Source: 2004-06/txt/msg00139.txt.bz2 Thanks for your response Peter. I dont think that the PHY timeout is an issue in my case. The phy initialization and indeed the MAC initialization completes successfully. The hardware independent ethernet driver sets the state as ACTIVE so the FreeBSD stack thinks the device is ready to send/receive. I still haven't figured out where the problem is. All I know is that something goes wrong in the initialization code before my main routine kicks in. I suspect the alarm timeout network thread because it calls the ethdrv "tickle" API call that seems to do a send operation. - Anunoy __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss