From: Jesper Skov <jskov@redhat.com>
To: ecos-discuss@sourceware.cygnus.com
Cc: Sandeep Rikhi <sr@cdotb.ernet.in>
Subject: [ECOS] forwarded message from Sandeep Rikhi
Date: Thu, 07 Sep 2000 04:21:00 -0000 [thread overview]
Message-ID: <14775.31270.533016.728986@thinktwice.zoftcorp.dk> (raw)
To : Jesper Skov <jskov at redhat dot com>
Subject : Re: [ECOS] DSRs
From : Sandeep Rikhi <sr at cdotb dot ernet dot in>
Date : Thu, 7 Sep 2000 15:35:48 +0500 (GMT+0500)
Respected Sir
Thanks for your kind help. Could you please guide me for the source code.
Also, ecos is already supporting
MPC850 which is being used in the project,
It would be a matter of great help if you could put some light on the
names of the files to be studied for interrupt handling.
Thanks & regards !
*********************************************************
Sandeep Rikhi
GET-GCPE Group.
Switching Division B1,
Centre for Development of Telematics,
Millers Road, Bangalore.
India.
Ph: (080) 2263399 ext:205/217,2250009,2282119
*********************************************************
On 7 Sep 2000, Jesper Skov wrote:
> >>>>> "Sandeep" == Sandeep Rikhi <sr@cdotb.ernet.in> writes:
>
> Sandeep> Suppose we configure eCos to allow DSRs and handle
> Sandeep> them in a list. Also, Suppose some thread is executing and
> Sandeep> there is an interrupt occurance.
>
> [snip]
>
> This is all handled by the "standard" eCos interrupt code. You must
> write your HAL to match the interrupt handling semantics of one of the
> existing HALs.
>
> Here's a little detail about the interrupt processing:
>
> http://sources.redhat.com/ecos/docs-latest/porting/hal-interrupts.html
>
> To get all the details you'd have to read the code.
>
> Suffice to say that your concerns are all addressed by the "standard"
> eCos interrupt handling semantics.
>
> Jesper
>
reply other threads:[~2000-09-07 4:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14775.31270.533016.728986@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=sr@cdotb.ernet.in \
/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).