[ECOS] Redboot network setup
Fabrice Gautier
Fabrice_Gautier@sdesigns.com
Thu Sep 13 17:10:00 GMT 2001
> 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....
Thanks
--
Fabrice Gautier,
Fabrice_Gautier@sdesigns.com
More information about the Ecos-discuss
mailing list