From: "Deak, Ferenc" <ferenc.deak@stp.hu>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] cirrus ep93xx - ecos works, network problems
Date: Tue, 11 Oct 2005 16:09:00 -0000 [thread overview]
Message-ID: <20051011181048.e27d4cc1.ferenc.deak@stp.hu> (raw)
In-Reply-To: <200510111524.EWB68581@ms7.netsolmail.com>
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?
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
next prev parent reply other threads:[~2005-10-11 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 15:24 bob.koninckx
2005-10-11 16:09 ` Deak, Ferenc [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-12 8:34 bob.koninckx
2005-10-11 12:01 Deak, Ferenc
2005-10-11 12:06 ` Andrew Lunn
2005-10-11 13:15 ` Deak, Ferenc
2005-10-11 14:10 ` Andrew Lunn
2005-10-11 15:54 ` Deak, Ferenc
2005-10-11 16:18 ` Deak, Ferenc
2005-10-13 14:27 ` Deak, Ferenc
2005-10-13 14:32 ` Gary Thomas
2005-10-17 13:10 ` Deak, Ferenc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051011181048.e27d4cc1.ferenc.deak@stp.hu \
--to=ferenc.deak@stp.hu \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).