From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4484 invoked by alias); 6 May 2004 22:19:45 -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 4476 invoked from network); 6 May 2004 22:19:44 -0000 Received: from unknown (HELO hermes.chez-thomas.org) (63.225.98.241) by sources.redhat.com with SMTP; 6 May 2004 22:19:44 -0000 Received: by hermes.chez-thomas.org (Postfix, from userid 2000) id 2FBAA100B66; Thu, 6 May 2004 16:19:44 -0600 (MDT) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by hermes.chez-thomas.org (Postfix) with ESMTP id 29EBD100B65; Thu, 6 May 2004 16:19:43 -0600 (MDT) From: Gary Thomas To: bob.koninckx@o-3s.com Cc: ecos-discuss@sources.redhat.com In-Reply-To: <1083881602.13449.20.camel@pc-002.vuilenbos.net> References: <1083793278.32010.14.camel@pc-002.vuilenbos.net> <1083794883.5389.376.camel@hermes> <1083820658.1173.2.camel@pc-002.vuilenbos.net> <1083881602.13449.20.camel@pc-002.vuilenbos.net> Content-Type: text/plain Organization: MLB Associates Message-Id: <1083881982.5389.606.camel@hermes> Mime-Version: 1.0 Date: Thu, 06 May 2004 22:19:00 -0000 Content-Transfer-Encoding: 7bit X-Spam-Level: X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on hermes.chez-thomas.org Subject: Re: [ECOS] cs8900a problem X-SW-Source: 2004-05/txt/msg00095.txt.bz2 On Thu, 2004-05-06 at 16:13, Bob Koninckx wrote: > Ignoring the frame seems to do the trick (at first sight). I suppose > that if ethernet frames would be lost, upper layers will take care of > that, right? > > I do believe, however, that the real problem lies with the device > driver, which should not be delivering zero length frames in the first > place. According to the cs8900a datasheet, enabling interrupts in the > RxCFG register but leaving the corresponding acceptance bit unset in the > RxCTL register will result in the device reporting zero length frames. I > tried the following change in the cs8900_start function > > // put_reg(base, PP_RxCFG, PP_RxCFG_RxOK | PP_RxCFG_CRC | > // PP_RxCFG_RUNT | PP_RxCFG_EXTRA); > put_reg(base, PP_RxCFG, PP_RxCFG_RxOK); > cpd->rxmode = PP_RxCTL_RxOK | PP_RxCTL_Broadcast | PP_RxCTL_IA; > put_reg(base, PP_RxCTL, cpd->rxmode); > > Although this could have explained what happened, it didn't solve > anything. My observation that the zero length is always returned when > the main polling loop is entered three times has been confirmed today. > Don't know if it means anything, but it gives me the impression that it > could be a hardware overrun. I've never seen this happen on any system with this chip, so I'm not sure why it happens. Of course this chip, like most others, has it's own vulgarities and this is probably just another one, albeit freshly discovered. If ignoring zero length frames works, then by all means ignore them. The rest (protocols, etc) should handle it just fine. > > Bob > > On Thu, 2004-05-06 at 07:17, Bob Koninckx wrote: > > On Thu, 2004-05-06 at 00:08, Gary Thomas wrote: > > > On Wed, 2004-05-05 at 15:41, Bob Koninckx wrote: > > > > After some (a lot) digging, I've come closer to my ethernet redboot > > > > problem. > > > > > > > > > > > > > > > > I further noticed that this zero length frame is only seen if the while > > > > loop in the main polling function gets entered at least three times. I > > > > have no idea what could be wrong, Hints or tips are welcome here! > > > > > > What happens if you just ignore frames with a zero length? > > > What's the status (stat) value when the length is zero? > > > > > > > stat always equals 0x04 (RxEvent without any flags set). I'll try and > > see what happens if I ignore zero length frames. > > > > Thanks, > > > > Bob > > -- Gary Thomas MLB Associates -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss