From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Andrew Grover
<andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: acpi_pci_irq_enable called for all PCI devices
Date: 03 Aug 2004 23:42:55 -0400 [thread overview]
Message-ID: <1091590975.2297.67.camel@dhcppc4> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A847070ED5D8-sBd4vmA9Se6krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Tue, 2004-08-03 at 20:39, Grover, Andrew wrote:
> Hi Bjorn, Len, & all,
>
> I'm looking at the code in pci_acpi_init that unconditionally calls
> acpi_pci_irq_enable for all PCI devices. The comment says this is to
> work around drivers that do not call pci_enable_device.
>
> Do we know if there are any drivers broken in this manner? I think it
> would be good to take advantage of the work done here and not do all IRQ
> allocation at init.
>
I think this was just to be conservative (retain old behaviour) during
2.6.8. Perhaps we should delete that upon the start of 2.6.9...
-Len
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next prev parent reply other threads:[~2004-08-04 3:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 0:39 acpi_pci_irq_enable called for all PCI devices Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A847070ED5D8-sBd4vmA9Se6krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-04 3:42 ` Len Brown [this message]
2004-08-04 14:21 ` Bjorn Helgaas
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=1091590975.2297.67.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=bjorn.helgaas-VXdhtT5mjnY@public.gmane.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