This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: cirrus ep93xx - ecos works, network problems
- From: <bob dot koninckx at o-3s dot com>
- To: "Deak, Ferenc" <ferenc dot deak at stp dot hu>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 12 Oct 2005 04:34:25 -0400
- Subject: Re: [ECOS] cirrus ep93xx - ecos works, network problems
---- Original message ----
>Date: Tue, 11 Oct 2005 18:10:48 +0200
>From: "Deak, Ferenc" <ferenc.deak@stp.hu>
>Subject: Re: [ECOS] cirrus ep93xx - ecos works, network
problems
>To: ecos-discuss@ecos.sourceware.org
>
>On Tue, 11 Oct 2005 11:24:30 -0400
><bob.koninckx@o-3s.com> wrote:
>
>> I am not sure if I understand correctly what you describe.
I
>> remember running into problems in the past because of
calls
>> to HAL_DELAY_US in the network code. You say something
about
>> changing timeouts to the order of magnitude of seconds, so
>> keep in mind that HAL_DELAY_US implements a busy wait,
which
>> could start waiting for a _very_ long period of time if
you
>> do that. The behavior you describe indicates that it could
be
>> something like that.
>>
>> Bob
>
>First, am I understand you correctly that you have a working
network
>stack for ecos (not redboot) with ep93xx?
No
>
>I'm sorry if my english is a little bit confusing, but I did
not intend to talk about
>timeouts, and I'm not changed any timeouts. The only timeout
in the
>driver is in the init function, so I think this is not the
problem...
>
>Thanks for your help,
>Ferenc Deak
>
>
>--
>Before posting, please read the FAQ:
http://ecos.sourceware.org/fom/ecos
>and search the list archive:
http://ecos.sourceware.org/ml/ecos-discuss
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss