From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: Andrew Morton <akpm@osdl.org>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
LSE <lse-tech@lists.sourceforge.net>
Subject: RE: [PATCH] 2.6.5- es7000 subarch update
Date: Mon, 12 Apr 2004 14:31:38 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0404121430290.18930@montezuma.fsmlabs.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0404121318510.18930@montezuma.fsmlabs.com>
On Mon, 12 Apr 2004, Zwane Mwaikambo wrote:
> On Mon, 12 Apr 2004, Protasevich, Natalie wrote:
>
> > Since it is a valid entry, find_irq_entry() in setup_IO_APIC_irqs() searches the mp_irqs[] by the pin number and runs into this element first. It uses it to program the pin and never gets to the element down below that contains modified entry with a correct overwrite in it.
> > I was able to get rid of this problem on the ES7000 with the following code:
> >
> > for (i = 0; i < mp_irq_entries; i++) {
> > if ((mp_irqs[i].mpc_srcbus == intsrc.mpc_srcbus)
> > && (mp_irqs[i].mpc_srcbusirq == intsrc.mpc_srcbusirq)) {
> > mp_irqs[i] = intsrc;
> > + if (intsrc.mpc_srcbusirq > pin) {
> > + int j;
> > + for (j = 0; j < i; j++)
> > + if (mp_irqs[j].mpc_dstirq == intsrc.mpc_dstirq)
> > + mp_irqs[j].mpc_irqtype = -1;
> > + }
> > found = 1;
> > break;
> > }
> > }
> > I will appreciate any feedback and suggestions.
>
> Out of interest, doesn't this have the same effect?
Forgot the bus check;
Index: linux-2.6.5-mc3/arch/i386/kernel/mpparse.c
===================================================================
RCS file: /home/cvsroot/linux-2.6.5-mc3/arch/i386/kernel/mpparse.c,v
retrieving revision 1.1.1.1
diff -u -p -B -r1.1.1.1 mpparse.c
--- linux-2.6.5-mc3/arch/i386/kernel/mpparse.c 9 Apr 2004 17:53:27 -0000 1.1.1.1
+++ linux-2.6.5-mc3/arch/i386/kernel/mpparse.c 12 Apr 2004 18:31:22 -0000
@@ -968,8 +968,9 @@ void __init mp_override_legacy_irq (
* Otherwise create a new entry (e.g. gsi == 2).
*/
for (i = 0; i < mp_irq_entries; i++) {
- if ((mp_irqs[i].mpc_srcbus == intsrc.mpc_srcbus)
- && (mp_irqs[i].mpc_srcbusirq == intsrc.mpc_srcbusirq)) {
+ if ((mp_irqs[i].srcbus == MP_ISA_BUS) &&
+ mp_irqs[i].mpc_dstirq == pin) {
+
mp_irqs[i] = intsrc;
found = 1;
break;
next prev parent reply other threads:[~2004-04-12 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 17:00 Protasevich, Natalie
2004-04-12 17:58 ` Zwane Mwaikambo
2004-04-12 18:31 ` Zwane Mwaikambo [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-19 17:30 Protasevich, Natalie
2004-04-14 16:45 Protasevich, Natalie
2004-04-13 3:44 Protasevich, Natalie
2004-04-14 4:29 ` Len Brown
[not found] <A6974D8E5F98D511BB910002A50A6647615F888E@hdsmsx403.hd.intel.com>
2004-04-13 3:19 ` Len Brown
2004-04-12 20:25 Protasevich, Natalie
2004-04-12 20:50 ` Zwane Mwaikambo
2004-04-06 15:08 Protasevich, Natalie
2004-04-05 16:12 Protasevich, Natalie
2004-04-06 6:30 ` Andrew Morton
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=Pine.LNX.4.58.0404121430290.18930@montezuma.fsmlabs.com \
--to=zwane@linuxpower.ca \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
/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
all inboxes | Powered by JetHome®