From: Greg KH <greg@kroah.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clarify pci.txt wrt IRQ allocation
Date: Fri, 11 Jun 2004 17:13:03 -0700 [thread overview]
Message-ID: <20040612001302.GA10294@kroah.com> (raw)
In-Reply-To: <200406111529.16419.bjorn.helgaas@hp.com>
On Fri, Jun 11, 2004 at 03:29:16PM -0600, Bjorn Helgaas wrote:
> I think we should make it explicit that PCI IRQs shouldn't be relied
> upon until after pci_enable_device(). This patch:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7-rc3/2.6.7-rc3-mm1/broken-out/bk-acpi.patch
>
> does PCI interrupt routing (based on ACPI _PRT) and IRQ allocation
> at pci_enable_device()-time.
>
> (To avoid breaking things in 2.6, the above patch still allocates
> all PCI IRQs in pci_acpi_init(), before any drivers are initialized.
> But that shouldn't be needed by correct drivers, and I'd like to
> remove it in 2.7.)
I agree.
> Here's a possible update:
Thanks, I've applied this to my trees.
greg k-h
prev parent reply other threads:[~2004-06-12 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 21:29 [PATCH] clarify pci.txt wrt IRQ allocation Bjorn Helgaas
2004-06-12 0:13 ` Greg KH [this message]
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=20040612001302.GA10294@kroah.com \
--to=greg@kroah.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.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