From: Alois Fertl <alois_fertl@talknet.de>
To: LinuxppcDev <linuxppc-dev@lists.linuxppc.org>
Cc: Cort Dougan <cort@ppc.kernel.org>
Subject: Solution for IRQ problems on 2nd Controller
Date: Mon, 03 Jan 2000 20:53:34 +0100 [thread overview]
Message-ID: <3870FE3E.4BEEF230@talknet.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
Some time ago there was a message on the list discussing problems
if more than one irq is pending from the second 8259. On the Blackhawk
I suffer this problem very badly, scsi, network and mouse are all via
the second controller. The problem is with 2.3.x kernels. 2.2 versions
had it fixed doing a loop until no more irqs are present on the second
controller.
The attached patch implements a workaround for the problem by disabling
all irqs from the second chip for a very short time
(in i8259_mask_and_ack_irq()) and than re-enabling the usual ones. Doing
so seems to re-issue the required edge on the line going to the first
controller.
It is probably nor the cleanest way of handling the problem but up
to now the one which solves the problem on my Blackhawk.
The patch is relative the the 2.3.35 version from cvs.on.openprojects.net
Alois.
[-- Attachment #2: i8259.patch --]
[-- Type: text/plain, Size: 1056 bytes --]
--- arch/ppc/kernel/i8259.c.dist Sat Jan 1 20:30:53 2000
+++ arch/ppc/kernel/i8259.c Mon Jan 3 20:17:00 2000
@@ -52,9 +52,10 @@
if (irq_nr > 7) {
cached_A1 |= 1 << (irq_nr-8);
inb(0xA1); /* DUMMY */
+ outb(0xff,0xA1);
outb(cached_A1,0xA1);
- outb(0x20,0xA0); /* Non-specific EOI */
- outb(0x20,0x20); /* Non-specific EOI to cascade */
+ outb(0x20,0xA0); /* Non-specific EOI to cascade */
+ outb(0x20,0x20); /* Non-specific EOI */
} else {
cached_21 |= 1 << irq_nr;
inb(0x21); /* DUMMY */
reply other threads:[~2000-01-03 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3870FE3E.4BEEF230@talknet.de \
--to=alois_fertl@talknet.de \
--cc=cort@ppc.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).