From: matthieu castet <castet.matthieu@free.fr>
To: Linux Kernel list <linux-kernel@vger.kernel.org>,
acpi-devel@lists.sourceforge.net
Cc: Adam Belay <ambx1@neo.rr.com>,
"Li, Shaohua" <shaohua.li@intel.com>,
Len Brown <len.brown@intel.com>
Subject: [ACPI] Re: Fw: ACPI bug causes cd-rom lock-ups (2.6.10-rc2)
Date: Wed, 01 Dec 2004 21:26:19 +0100 [thread overview]
Message-ID: <41AE28EB.9090302@free.fr> (raw)
>+/*
>+ * We'd like PNP to call this routine for the
>+ * single ISA_USED value for each legacy device.
>+ * But instead it calls us with each POSSIBLE setting.
>+ * There is no ISA_POSSIBLE weight, so we simply use
>+ * the (small) PCI_USING penalty.
>+ */
Couldn't be better to change the pnp core behaviour ?
In drivers/pnp/resource.c, pnp_register_irq_resource, instead of calling
pcibios_penalize_isa_irq couldn't we call something like
pcibios_penalize_possible_isa_irq ?
The pnp implemations already use pcibios_penalize_isa_irq [1] for the
irq that are used.
So it seem it is call 2 times for the allocated resources...
Also don't we need to depenalize the irq, if we change the irq or
disable the device ?
Matthieu CASTET
[1]
$grep -r penalize */*
pnpacpi/rsparser.c:
pcibios_penalize_isa_irq(res->data.irq.interrupts[0]);
pnpacpi/rsparser.c:
pcibios_penalize_isa_irq(res->data.extended_irq.interrupts[0]);
pnpbios/rsparser.c: pcibios_penalize_isa_irq(irq);
next reply other threads:[~2004-12-01 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 20:26 matthieu castet [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-26 0:53 [ACPI] Re: Fw: ACPI bug causes cd-rom lock-ups (2.6.10-rc2) Li, Shaohua
2004-11-15 19:19 2.6.10-rc1-mm5 (and ide-cd) Stas Sergeev
2004-11-23 6:09 ` Fw: ACPI bug causes cd-rom lock-ups (2.6.10-rc2) Len Brown
2004-11-24 18:12 ` Stas Sergeev
2004-11-24 22:44 ` Len Brown
2004-11-25 18:18 ` Stas Sergeev
2004-12-01 5:41 ` [ACPI] " Len Brown
2004-12-01 5:44 ` Len Brown
2004-12-02 16:52 ` Stas Sergeev
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=41AE28EB.9090302@free.fr \
--to=castet.matthieu@free.fr \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ambx1@neo.rr.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.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;
as well as URLs for NNTP newsgroup(s).