From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: strange interrupt chaining problem with keyboard interrupt
Date: 8 Oct 2000 17:54:40 GMT
Organization: Ericsson Erisoft AB, Sweden
Lines: 18
Message-ID: <8rqcd0$gng$3@antares.lu.erisoft.se>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1001005075606 DOT 3958E-100000 AT is> <8rhi12$4up$10$1 AT news DOT t-online DOT com> <9003-Thu05Oct2000231854+0300-eliz AT is DOT elta DOT co DOT il> <8rj5td$l0o$14$1 AT news DOT t-online DOT com> <7458-Fri06Oct2000114142+0300-eliz AT is DOT elta DOT co DOT il> <8rliej$ecd$14$1 AT news DOT t-online DOT com>
NNTP-Posting-Host: lws256.lu.erisoft.se
X-Newsreader: TIN [version 1.2 PL2]
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Peter Remmers (Peter DOT Remmers AT t-online DOT de) wrote:
: int count = 0;
: void irq1handler()
: {
:    // removing this textput doesn't help
:    // (it uses the libc's vsprintf which might have been a problem?)
:    textput(0,0, "  %d  ", ++count);
:    asm volatile ("pushf");
:    asm volatile ("lcall *_oldirq1");
: }

Shouldn't there be an "asm volatile ("popf");" after the lcall? If
not, why not?


Right,

						MartinS