home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!uwm.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!csc.ti.com!tilde.csc.ti.com!mksol!mccall
- From: mccall@mksol.dseg.ti.com (fred j mccall 575-3539)
- Newsgroups: comp.os.os2.misc
- Subject: Re: OS/2's Interrupt Mapping
- Keywords: IRQ, Interrupt
- Message-ID: <1992Nov7.161053.24080@mksol.dseg.ti.com>
- Date: 7 Nov 92 16:10:53 GMT
- References: <1992Nov6.180326.10300@u.washington.edu>
- Organization: Texas Instruments Inc
- Lines: 21
-
- In <1992Nov6.180326.10300@u.washington.edu> mts@hardy.u.washington.edu (Sean Milligan) writes:
-
- > I read somewhere that OS/2 calls the interrupt addresses by different
- >numbers. (Ex. 9 is IRQ2, I think). I'm trying to get all my boards to work
- >and was wondering if anyone knows if this is true and if so would they please
- >post the various addresses for OS/2 corresponding to the "Real world"
- >settings.
-
- All AT class and better machines map IRQ2 to IRQ9. This is because
- the original PC only had 1 interrupt controller. When the ISA bus
- came out, they cascaded a second interrupt controller off of the first
- one, hanging it off the IRQ2 line. Then in order for IRQ2 to function
- for those cards that expected it, they made IRQ9 map to IRQ2.
-
- In other words, this is a hardware thing and not an OS/2 thing.
-
- --
- "Insisting on perfect safety is for people who don't have the balls to live
- in the real world." -- Mary Shafer, NASA Ames Dryden
- ------------------------------------------------------------------------------
- Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.
-