From: Len Brown <len.brown@intel.com>
To: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: Andrew Morton <akpm@osdl.org>,
"Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: RE: [PATCH] 2.6.5- es7000 subarch update
Date: 12 Apr 2004 23:19:34 -0400 [thread overview]
Message-ID: <1081826374.2258.597.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F888E@hdsmsx403.hd.intel.com>
Natalie,
> ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 13 high edge)
I agree with your description of why the 15->13 override fails.
> ACPI: INT_SRC_OVR (bus 0 bus_irq 4 global_irq 14 high edge)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 15 high edge)
These two also create an actual and potential duplicate mp_irqs[] entry.
> ACPI: INT_SRC_OVR (bus 0 bus_irq 6 global_irq 16 high edge)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 7 global_irq 17 high edge)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 8 global_irq 18 low edge)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 12 global_irq 19 high edge)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 20 high edge)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 23 high level)
The ES7000 sure is a great tester of the over-ride code!
But I don't like the proposal to selectively invalidate
existing mp_irqs[] entries.
I think the proper fix is to parse the over-ride entries before
filling in the (remaining) identity mappings. This also gets
rid of the special case for IRQ2, which would be handled exactly
like the mappings to < 16 on the ES7000 above.
Perhaps I should send you a patch you can test on the ES7000,
since I don't have one of those?
In any case, I'd prefer that proposed patches to this code come
through me, since it is ACPI specific.
thanks,
-Len
next parent reply other threads:[~2004-04-13 3:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F888E@hdsmsx403.hd.intel.com>
2004-04-13 3:19 ` Len Brown [this message]
2004-04-19 17:30 [PATCH] 2.6.5- es7000 subarch update Protasevich, Natalie
-- strict thread matches above, loose matches on Subject: below --
2004-04-14 16:45 Protasevich, Natalie
2004-04-13 3:44 Protasevich, Natalie
2004-04-14 4:29 ` Len Brown
2004-04-12 20:25 Protasevich, Natalie
2004-04-12 20:50 ` Zwane Mwaikambo
2004-04-12 17:00 Protasevich, Natalie
2004-04-12 17:58 ` Zwane Mwaikambo
2004-04-12 18:31 ` 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=1081826374.2258.597.camel@dhcppc4 \
--to=len.brown@intel.com \
--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 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.