From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Re: Question on PCI Interrupt translation
Date: Mon, 18 Sep 2000 20:09:00 -0000 [thread overview]
Message-ID: <002201c021e7$06a2abe0$0201a8c0@raccoon> (raw)
In-Reply-To: <39C39E43.D84D85FE@redhat.com>
>
> As you are guessing, it may just be a simple mistake in constructing the
> ISR. Normally the steps are:
>
> cyg_interrupt_create()
> cyg_interrupt_attach()
> cyg_interrupt_unmask()
>
> and be sure to call cyg_interrupt_acknowledge() in the ISR.
>
> > I read the test cases for intr, I didn't find an realistic sample to
test
> > the interrupt mechanism, since the test case just cover the function
call
> > part, not real interrupt is generated. Is there any working interrupt
> > sample?
>
Thanks Jifl,
I guess I follow the correct step of using interrupt. I am not sure if it is
the bug for eCos, I changed one thing in platform.S for vrc4373. In the
initialization of vrc4372, the INTPOL and INTRIG are set to 0x03fff, I use
0x001f instead. Since PCI standard use interrupt for level trigger, low
active, I initialize the #INTA-#INTB to this configuration, I can enter the
ISR now...
But the question is, supposely the DSR will be executed automatically,
right? But I wait for a long time, nothing happens? Is that a problem?
Will you attend the ESC at San Jose?
Thanks.
Rgds,
-Ling
prev parent reply other threads:[~2000-09-18 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-15 19:49 [ECOS] " Ling Su
2000-09-16 9:22 ` [ECOS] " Jonathan Larmour
2000-09-18 20:09 ` Ling Su [this message]
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='002201c021e7$06a2abe0$0201a8c0@raccoon' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.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).