This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Redboot network setup
- To: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Subject: Re: [ECOS] Redboot network setup
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Fri, 14 Sep 2001 02:13:41 +0100
- Cc: "Ecos-List (E-mail)" <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat UK Ltd.
- References: <B1F6452C89AFD411AE0800A0CC734C230150A7@EMAIL1>
Fabrice Gautier wrote:
>
> > From: Jonathan Larmour [mailto:jlarmour@redhat.com]
> > Subject: Re: [ECOS] Redboot network setup
> > >
> > > Then explain me where does the polling occurs ?
> >
> > net_io_test() is an "idle" function, which calls __tcp_poll().
> >
> > Yes, that should work. Maybe RedBoot is jammed somewhere
> > else, like some other idle function is blocking.
>
> Now I see. And i think the problem is in cyg_hal_plf_serial_getc_nonblock
> where we can see:
>
> long timeout = 1000000000; // A long time...
>
> Indeed a long time, for a non blocking function...
>
> This is in hal_diag.c of the Integrator port but there is the same thing in
> 7 others ports:
>
> hal\arm\aeb\current\src\hal_diag.c(447): long timeout = 1000000000; // A
> long time...
> hal\arm\cma230\current\src\hal_diag.c(526): long timeout = 1000000000;
> // A long time...
> hal\arm\ebsa285\current\src\hal_diag.c(346): long timeout = 1000000000;
> // A long time...
> hal\arm\edb7xxx\current\src\hal_diag.c(375): long timeout = 1000000000;
> // A long time...
> hal\arm\iq80310\current\src\hal_diag.c(524): long timeout = 1000000000;
> // A long time...
> hal\arm\pid\current\src\hal_diag.c(501): long timeout = 1000000000; // A
> long time...
> hal\mips\rm7000\ocelot\current\src\ns16552.c(487): long timeout =
> 1000000000; // A long time...
>
> Does anybody noticed problem with networking on this ports?
>
> Maybe the timeout is not an issue for some ports but it was for me, if I
> reduce the timeout to 100 it seems to works. But i'm not sure It needs a
> timeout at all....
There shouldn't be anything needing a timeout on a non-blocking read. In
the other ports you're looking at it's only the non-virtual vector blocking
read functions that have these timeouts.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine