From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Problem using timer and irq routines from Allegro
Date:	15 Jan 2001 17:09:25 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	21
Message-ID:	<93vas5$5j6$1@nets3.rz.RWTH-Aachen.DE>
References:	<200101151041 DOT LAA31499 AT alcatel DOT no>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 979578565 5734 137.226.32.75 (15 Jan 2001 17:09:25 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	15 Jan 2001 17:09:25 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

paul DOT crone AT thomson-csf DOT no wrote:
> I have a problem that I've been trying to resolve for some time.  This is a 
> test harness program to test a timer routine using the Allegro timer.c,
> irq.c and irqwrap.S files.  I want to use them in my program.

> The program runs and apparently installs the timer and irq's.  My
> problem is that I don't get any interrupt 'timerRCU' callbacks and
> so the printf statement never prints.

Please be aware that you shouldn't be calling any other functions from
an interrupt handler. Certainly not a complicated one like printf().

I didn't really look at all the code, but there's another possible
problem that comes to mind. You seem to be talking about *two* timer
packages (yours, and the one from allegro) being active at the same
time. Such a setup generally won't work, unless you make sure you use
two independent timer tick IRQ sources, and properly chain interrupt
handlers, where appropriate.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -