From: Gary Thomas <gthomas@redhat.com>
To: Rene.Affourtit@pemstar.nl
Cc: ecos-discuss@sourceware.cygnus.com, aknecht@cimsi.cim.ch
Subject: RE: [ECOS] Threading on EDB7211
Date: Mon, 19 Jun 2000 04:11:00 -0000 [thread overview]
Message-ID: <XFMail.000619051125.gthomas@redhat.com> (raw)
In-Reply-To: <OF32BDA76A.33B1D1FF-ONC1256903.002493B5@pemstar.nl>
The very first thing to look at is the tools you are using to build eCos.
The sourceware 'binutils' package _was_ broken. Any snapshots from late
May through early June will not build a running eCos on ARM platforms.
On 19-Jun-00 Rene.Affourtit@pemstar.nl wrote:
>
> 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.
>
>
next prev parent reply other threads:[~2000-06-19 4:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 0:04 Rene.Affourtit
2000-06-19 4:11 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-19 5:24 Rene.Affourtit
2000-06-19 4:42 Rene.Affourtit
2000-06-19 5:06 ` Gary Thomas
2000-06-19 11:55 ` Alfredo Knecht
2000-06-19 13:22 ` Gary Thomas
2000-06-16 8:29 Alfredo Knecht
[not found] ` <XFMail.000616095000.gthomas@redhat.com>
2000-06-16 12:29 ` Alfredo Knecht
2000-06-16 13:34 ` Gary Thomas
2000-06-16 6:39 Rene.Affourtit
2000-06-16 7:03 ` Gary Thomas
2000-06-12 12:51 Alfredo Knecht
2000-06-10 19:55 Alfredo Knecht
2000-06-11 4:38 ` Gary Thomas
2000-06-12 1:19 ` Alfredo Knecht
2000-06-12 6:10 ` Gary Thomas
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=XFMail.000619051125.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=Rene.Affourtit@pemstar.nl \
--cc=aknecht@cimsi.cim.ch \
--cc=ecos-discuss@sourceware.cygnus.com \
/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).