This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
RE: Threading on EDB7211
- To: Gary Thomas <gthomas at redhat dot com>
- Subject: RE: [ECOS] Threading on EDB7211
- From: Rene dot Affourtit at pemstar dot nl
- Date: Mon, 19 Jun 2000 09:02:59 +0200
- Cc: aknecht at cimsi dot cim dot ch,ecos-discuss at sourceware dot cygnus dot com,gary at ares dot chez-thomas dot org
I'm using the cirrus logic edb7111-2 rev B board.
I think my network problems are related to the timer interrupt problems,
because what I see is
(rougly)
- system initializes,
- networking interface starts the cyg_netint thread.
- cyg_netint waits for netint_flags
- program starts whatever threads it need's
- one by one all threads yield (waiting for IO or somtheing like that)
- system enters Idle thread mode and stays there
this is a scenario which enters IdleThread mode. Basicly what happens is
that because there are no (or very few) clock interrupts there is only
scheduling when a thread has to wait. Once a thread starts running that
doesn't have to wait (e.g. IdleThread) the system stays in this thread and
keeps on doing what it thinks is useful work.
Hope this is useful background info,
I'm looking into today, I'll let you all know if I find something
Rene
Gary Thomas
<gthomas@redhat To: Rene.Affourtit@pemstar.nl
.com> cc: ecos-discuss@sourceware.cygnus.com, Alfredo Knecht
Sent by: <aknecht@cimsi.cim.ch>
gary@ares.chez- Subject: RE: [ECOS] Threading on EDB7211
thomas.org
06/16/00 04:03
PM
On 16-Jun-00 Rene.Affourtit@pemstar.nl wrote:
> Did anybody solve this?
> I didn't notice this before, but in trying to get the networking code to
> run I noticed it.
>
I didn't hear anything back from him. I'm not sure where to go with it
since
this code works on our boards.
As for your problems with networking; what platform are you trying to use?
Can you provide details as to the problems you are experiencing?
Notice that the Cirrus Logic EDB7209 board requires a hardware modification
for the networking to function. See the README for details.