Date: Thu, 18 Jan 2001 11:53:48 -0800 From: Mike Smith <msmith@freebsd.org> To: Dennis <dennis@etinc.com> Cc: hackers@freebsd.org Subject: Re: stray irq 7 Message-ID: <200101181953.f0IJrmQ00749@mass.osd.bsdi.com> In-Reply-To: Your message of "Thu, 18 Jan 2001 13:04:10 EST." <5.0.0.25.0.20010118122059.01fb0b00@mail.etinc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>
> I know we've discussed this before. But I cant believe its a "hardware
> problem".
Then you're not going to believe the answer.
> Enabling any ISA interrupt causes the problem. Rather than the standard "
> your hardware is defective", perhaps someone can explain how a masked
> interrupt can be generated without being enabled.
You should read the i8259 datasheet, or the datasheet for any device
embedding a macrocell which emulates it.
> It seems as if the masks are being written wrong. By enabling irq 5 I can
> cause the problem on demand.
This may well be the case, but until you read the i8259 datasheet, or the
datasheet for any device embedding a macrocell which emulates it, and
compare the code against what is claimed should be done, you aren't
helping anyone.
> What exactly is the hardware problem..and if you've identified it why is
> there no simple workaround after all this time (or is there)?
You should read the i8259 datasheet, or the datasheet for any device
embedding a macrocell which emulates it, and once you read the section on
spurious interrupts all should become clear.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101181953.f0IJrmQ00749>