Re: [ECOS] Network code unstable (Solved for real this time).

[Roland Caßebohm <roland dot cassebohm at visionsystems dot de>]

On Wednesday, 6. March 2002 18:32, Pieter Truter wrote:
> The ether chip stopped responding. I did not experience this problem in
> RedBoot, mainly because of the lightweight stack used by RedBoot.
>
> I will still do some tests to see how it affect the GDB stubs in RedBoot. I
> know it is extremely slow to download an image with GDB/RedBoot.
>
> -----Original Message-----
> From: Douglas Bush [mailto:dbush@extremeeng.com]
> Sent: Wednesday, March 06, 2002 9:23 AM
> To: 'Pieter Truter'; 'Gary Thomas'; 'Andrew Lunn'
> Cc: 'eCos Disuss'
> Subject: RE: [ECOS] Network code unstable (Solved for real this time).
>
>
> Would this driver problem affect redboot\GDB?  Were the crashes hard
> resets, or just continuous loops?
>

Douglas sad in an other message that the download speed of redboot is much 
slower sins may 2001. I have looked in the CVS tree to find out what was 
changed at this time:


2001-05-07  Gary Thomas  <gthomas@redhat.com>

        * src/net/net_io.c (net_io_isr): Interrupt acknowledgement
        should rightly be done by the driver 'delivery' routine, not here.

Maybe this change does effect redboot/gdb ?

Roland
-- 
___________________________________________________

VS Vision Systems GmbH, Industrial Image Processing
Roland Caßebohm
Aspelohe 27A, D-22848 Norderstedt, Germany
Mail: roland.cassebohm@visionsystems.de
http://www.visionsystems.de
___________________________________________________

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss