From: "Colin Bayer" <colin_bayer@compnerd.net>
To: linux-kernel@vger.kernel.org
Cc: rddunlap@osdlab.org
Subject: RE: Sticky IO-APIC problem
Date: Mon, 9 Jul 2001 05:38:55 -0700 [thread overview]
Message-ID: <200107091238.FAA11225@mail9.bigmailbox.com> (raw)
'K, after hours (which seemed like years) of surfing the datasheets of the 82810AA ICH (I/O Controller Hub) from Intel, I've come up with step-by-step hardware-level instructions for enabling the IO-APIC with pre-defined PIRQs (I'm not an assembly guru, so I can't help with the coding of this):
1) Set bit 7 of register PIRQ[n]_ROUT (offset 60h) to 0.
2) Set bits 3:0 of the same register to the (8259) interrupt to be mapped on this PIRQ (big-endian).
3) Set the corresponding bit on the correct 8259s (master is at 21h, slave at A1h) OCW1 register to mask the interrupt; the way I read it, bit 7 of the A1h register is IRQ 15, bit 0 of 21h is IRQ 0.
4) Set bit 8 of GEN_CNTL (starting offset D0h, hehe...) to 1 to enable the I/O APIC.
Anyway, that's as far as I could read into the process. Hope somebody out there in maintainer-land can create a cogent snippet of code out of it. If such code exists, plz don't flame me...
-- Colin
On the first day, man created the computer. On the second day, God proclaimed from the heavens, "F0 0F C7 C8".
------------------------------------------------------------
The CompNerd Network: http://www.compnerd.com/
Where a nerd can be a nerd. Get your free webmail@compnerd.net!
next reply other threads:[~2001-07-09 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 12:38 Colin Bayer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-05 4:12 Sticky IO-APIC problem Colin Bayer
2001-07-04 0:19 Colin Bayer
2001-07-03 23:03 Manfred Spraul
2001-07-03 21:58 Randy.Dunlap
2001-07-02 9:25 Colin Bayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200107091238.FAA11225@mail9.bigmailbox.com \
--to=colin_bayer@compnerd.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdlab.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.