From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4815 invoked by alias); 14 Jul 2005 07:45:22 -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 4798 invoked by uid 22791); 14 Jul 2005 07:45:14 -0000 Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.203) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 14 Jul 2005 07:45:14 +0000 Received: by wproxy.gmail.com with SMTP id i32so369924wra for ; Thu, 14 Jul 2005 00:45:13 -0700 (PDT) Received: by 10.54.31.62 with SMTP id e62mr652919wre; Thu, 14 Jul 2005 00:43:49 -0700 (PDT) Received: by 10.54.67.12 with HTTP; Thu, 14 Jul 2005 00:43:49 -0700 (PDT) Message-ID: <7de07eff0507140043380be37e@mail.gmail.com> Date: Thu, 14 Jul 2005 07:45:00 -0000 From: Sriramkumar Raju Reply-To: Sriramkumar Raju To: Sriramkumar Raju , ecos-discuss@sources.redhat.com In-Reply-To: <20050712113751.GH15048@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7de07eff0507120332361df98e@mail.gmail.com> <20050712113751.GH15048@lunn.ch> Subject: Re: [ECOS] Issue with VIA Rhine II ethernet Driver on I386 platform in latest code base. X-SW-Source: 2005-07/txt/msg00154.txt.bz2 Thanks Andrew it worked after adding some delay. On 7/12/05, Andrew Lunn wrote: > On Tue, Jul 12, 2005 at 04:02:39PM +0530, Sriramkumar Raju wrote: > > Hi, > > I had ported RedBoot to i386 platform having VIA Rhine II > > Ethernet controller. It is working well with the code base that I got > > from "http://safariexamples.informit.com/0130354732/". > > > > I took the latest eCOS code base from > > "http://ecos.sourceware.org/anoncvs.html" by executing the command > > "cvs -z3 -d :pserver:anoncvs@ecos.sourceware.org:/cvs/ecos co -P > > ecos". > > I did the porting of the VIA Rhine driver to the i386 platform in > > latest code base. The system failed to boot. So i tried to debug it by > > enabling the DEBUG in Rhine driver and some more diag_printf > > statements. So after adding debug I got the system booting and got > > DHCP ip address from the DHCP server. I am able to telnet to the > > target. > > > > I want to know what might be reason that makes my system to come up > > once I add the debug message. Do I need to change the memory > > configuration of my system while porting the driver to i386 platform? >=20 > The debug messages might have changed the timing such that some > hardware dependant timing works with the debug messages and not > without them. What you can try to do is slowly remove the debug > messages and see which one is critcal. That might give you a clue as > to while bit of code is causing the problem. >=20 > Andrew > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss