From: Gary Thomas <gary@mlbassoc.com>
To: Aaron Case <aaron.case@dynazign.com>
Cc: Ecos-Discuss <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] context for creating interrupts on edb7312
Date: Thu, 20 Nov 2003 15:21:00 -0000 [thread overview]
Message-ID: <1069341693.1961.660.camel@hermes> (raw)
In-Reply-To: <GBEOKKOEOGFDMKDFCHIMKENNCAAA.aaron.case@dynazign.com>
On Thu, 2003-11-20 at 08:01, Aaron Case wrote:
> > It happens automatically in "cyg_start()", so my test runs just as well
> > even if I make this change:
> >
> > Index: hal/powerpc/mpc8xxx/current/tests/mpc8xxx_timer.c
> > ===================================================================
> > RCS file:
> > /home/gthomas/my_cvs/develop/ecos/packages/hal/powerpc/mpc8xxx/cur
> > rent/tests/mpc8xxx_timer.c,v
> > retrieving revision 1.1
> > diff -u -5 -p -r1.1 mpc8xxx_timer.c
> > --- hal/powerpc/mpc8xxx/current/tests/mpc8xxx_timer.c 20 Nov 2003
> > 14:21:54 -0000 1.1
> > +++ hal/powerpc/mpc8xxx/current/tests/mpc8xxx_timer.c 20 Nov 2003
> > 14:29:39 -0000
> > @@ -149,12 +149,12 @@ cyg_user_start( void )
> > IMM->cpm_timers_trr1 = 0x2000; // Reference value
> > IMM->cpm_timers_tcn1 = 0;
> > IMM->cpm_timers_ter[0] = 0xFF;
> > IMM->cpm_timers_tgcr1 = _TC_TGCR_RST1; // Reset & enable timer1
> >
> > - cyg_scheduler_start();
> > - CYG_TEST_PASS("mpc8xxx_timer");
> > +// cyg_scheduler_start();
> > +// CYG_TEST_PASS("mpc8xxx_timer");
> > }
> >
> > //
> > -------------------------------------------------------------------------
> >
> > #else // ! CYGPKG_KERNEL
> >
> > Are you overriding "cyg_start()"? That's the place that the scheduler
> > is normally started (although many of our tests do it explicitly)
> >
> > --
> > Gary Thomas <gary@mlbassoc.com>
> > MLB Associates
> >
> >
>
> Thanks for the clarification. I believe this may be my last question on the
> matter.
>
> Is it possible to enable interrupts with cyg_interrupt_enable(), before the
> task scheduler starts, supposing I were foolish enough to do such a thing?
>
> It appears that cyg_interrupt_enable() acts directly on the CPSR in
> ARM(after viewing the ASM), but my MAJIC debugger tells me that the CPSR
> doesn't change unless the scheduler is started. So what in eCos blocks
> access to the interrupt bits in the CPSR when the scheduler is not running?
Nothing - remember eCos is pretty light weight; you can do most anything
you want at any time. That said, it's not a good idea to be messing
around with the interrupts and you should never blindly just enable them
(unless you want a broken system!)
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-11-20 15:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 16:34 Aaron Case
2003-11-19 19:36 ` Gary Thomas
2003-11-19 20:22 ` Aaron Case
2003-11-19 22:18 ` Gary Thomas
2003-11-20 14:25 ` Aaron Case
2003-11-20 14:35 ` Gary Thomas
2003-11-20 15:01 ` Aaron Case
2003-11-20 15:21 ` Gary Thomas [this message]
2003-11-21 15:06 ` Aaron Case
2003-11-21 15:55 ` Gary Thomas
2003-11-21 16:32 ` Aaron Case
2003-11-21 17:22 ` Gary Thomas
2003-11-21 17:28 ` Gary Thomas
2003-11-21 18:28 ` Aaron Case
2003-11-19 16:50 amassa
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=1069341693.1961.660.camel@hermes \
--to=gary@mlbassoc.com \
--cc=aaron.case@dynazign.com \
--cc=ecos-discuss@sources.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).