X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Message-ID: <41012fe1$0$172$cc7c7865@news.luth.se>
From: Martin Str|mberg <ams AT speedy DOT ludd DOT ltu DOT se>
Subject: Re: PM hardware interrupts
Newsgroups: comp.os.msdos.djgpp
References: <ZtDJc.129847$wH4 DOT 7032125 AT twister DOT southeast DOT rr DOT com> <003e01c46b01$84546800$0d01a8c0 AT josepmariaxp> <3pCLc.170124$tH1 DOT 6880991 AT twister DOT southeast DOT rr DOT com>
User-Agent: tin/1.4.6-20020816 ("Aerials") (UNIX) (NetBSD/1.6Q (alpha))
Date: 23 Jul 2004 15:33:53 GMT
Lines: 25
NNTP-Posting-Host: speedy.ludd.ltu.se
X-Trace: 1090596833 news.luth.se 172 130.240.16.13
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Matt Flyer <goaway AT nospam DOT me> wrote:
: So far I have been able to straighten things out a little bit.  I can
: re-direct the interrupts either by chaining or allocating an iret wrapper
: and claiming the interrupt with a "_go32_set_protected" command.  For some
: reason though, the interrupt only executes one time.  From my research, I
: would say this means that the interrupt is not being acknowledged - but I
: believe this I addressed this.  If I am not mistaken, when I chain the
: interrupt using the "_go32_chain_protected ..." command, I acknowledge the
: interrupt with an outportb(0xA0, 0x20); outportb(0x20,0x20); (slave first)
: for a non specific EOI and when I simply capture the interupt the wrapper
: handles this for me.  My above assumptions are partially based on
: experimental results as if I don't structure the code this way I get crash
: errors of some form.

I would expect the chain variant to acknowledge the interrupt (as I
would expect it to be chained to the previous handler), but not
the iret version.

But note that I haven't done any hardware interrupt hooking myself, so
I don't know much about that.


Right,

						MartinS