From: Gary Thomas <gthomas@redhat.com>
To: Alfredo Knecht <aknecht@cimsi.cim.ch>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] Threading on EDB7211
Date: Mon, 19 Jun 2000 13:22:00 -0000 [thread overview]
Message-ID: <XFMail.000619142231.gthomas@redhat.com> (raw)
In-Reply-To: <3.0.5.32.20000619205726.00a61220@mailhost>
I built a EDB7211 install/build tree & put the whole thing at:
ftp://ftp.chez-thomas.org/pub/eCos/edb7211/
Pick and choose. Let me know what happens.
Also, if you had a chance, perhaps you could try an older binutils snapshot.
The one that I know works is from 000321 (I also put this file under /eCos)
Note: ftp.chez-thomas.org is a new address. If this doesn't work, try
hermes.chez-thomas.org.
On 19-Jun-00 Alfredo Knecht wrote:
> Hi All,
> I sure am glad for Rene, though I think he was asking for trouble...
> As for my problems, they are still here even after installing binutils
> 2.10rc3.
> Innocent as a lamb, still investigating on this strange behaviour. :)
> I will let you know as soon as I find something;
> In the meantime, would anybody bother to send me known working objects
> under the /install/lib/ for an EDB-7111-2, no matter which configuration?
> just to narrow the quest a little.
> Thank you,
> Alfredo
>
> At 06:06 19.6.00 -0600, you wrote:
>>
>>On 19-Jun-00 Rene.Affourtit@pemstar.nl wrote:
>>>
>>> Thanks for the hint,
>>>
>>> but as it turned out my problem was caused by a modification I made in
>>> vectors.s which caused that no interupts were handled by ecos at all.
>>> It's strange how two very different problems can have the same symptoms.
>>> Sorry to have bothered you all with something that was entirely my own
>>> fault.
>>>
>>
>>No need to apologize (just don't do it again :-)
>>
>>This mailing list is supposed to be a forum where ideas and questions can
>>be posted and hopefully resolved. Even if the problem was your fault,
>>asking it here let's everyone who uses eCos about it. When a solution
>>is found, we all hear about it as well and can benefit from the experience.
>>
>>Just for grins - what did you change in vectors.S, why did you do it and
>>what did you do wrong? [Just for pedagogic enlightment :-) ]
>>
>>
> ************************************************************************
> Alfredo Knecht Fax ++41 91 610 8970 Tel ++41 91 610 8960
> SUPSI-ICIMSI aknecht@cimsi.cim.ch http://www.cimsi.cim.ch
>
> Istituto CIM della Svizzera italiana CH-6928 Manno (Lugano)
> ************************************************************************
>
next prev parent reply other threads:[~2000-06-19 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-19 5:24 Rene.Affourtit
2000-06-19 0:04 Rene.Affourtit
2000-06-19 4:11 ` 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.000619142231.gthomas@redhat.com \
--to=gthomas@redhat.com \
--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).