From: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
To: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
Chris Wright <chrisw-3NddpPZAyC0@public.gmane.org>
Subject: Re: [ACPI] [PATCH] 2.6.0-test4 Don't change BIOS allocated IRQs
Date: Tue, 16 Sep 2003 18:02:55 -0700 [thread overview]
Message-ID: <20030917010254.GA1640@kroah.com> (raw)
In-Reply-To: <200309170011.03630.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
On Wed, Sep 17, 2003 at 12:11:03AM +0100, Andrew de Quincey wrote:
> With the help of Chris Wright testing several failed patches, I've tracked
> down another ACPI IRQ problem. On many systems, the BIOS
> pre-allocates IRQs for certain PCI devices, providing a list of alternate
> possibilities as well.
>
> On some systems, changing the IRQ to one of those alternate possibilities
> works fine. On others however, it really isn't a good idea. As theres no
> way to tell which systems are good and bad in advance, this patch simply
> ensures that ACPI does not change an IRQ if the BIOS has pre-allocated it.
Nice, the patch below, which Chris told me is from you, fixed my
problems too. It is against 2.6.0-test5-bk3 and fixes bug number 1186
in the bugzilla.kernel.org database.
Many thanks for this work, I really appreciate it.
thanks,
greg k-h
test5-bk_current
===== drivers/acpi/pci_link.c 1.13 vs edited =====
--- 1.13/drivers/acpi/pci_link.c Mon Sep 8 05:51:03 2003
+++ edited/drivers/acpi/pci_link.c Tue Sep 16 16:16:31 2003
@@ -456,7 +456,6 @@
irq = link->irq.active;
} else {
irq = link->irq.possible[0];
- }
/*
* Select the best IRQ. This is done in reverse to promote
@@ -466,6 +465,7 @@
if (acpi_irq_penalty[irq] > acpi_irq_penalty[link->irq.possible[i]])
irq = link->irq.possible[i];
}
+ }
/* Attempt to enable the link device at this IRQ. */
if (acpi_pci_link_set(link, irq)) {
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net,
linux-acpi@intel.com, Chris Wright <chrisw@osdl.org>
Subject: Re: [ACPI] [PATCH] 2.6.0-test4 Don't change BIOS allocated IRQs
Date: Tue, 16 Sep 2003 18:02:55 -0700 [thread overview]
Message-ID: <20030917010254.GA1640@kroah.com> (raw)
In-Reply-To: <200309170011.03630.adq_dvb@lidskialf.net>
On Wed, Sep 17, 2003 at 12:11:03AM +0100, Andrew de Quincey wrote:
> With the help of Chris Wright testing several failed patches, I've tracked
> down another ACPI IRQ problem. On many systems, the BIOS
> pre-allocates IRQs for certain PCI devices, providing a list of alternate
> possibilities as well.
>
> On some systems, changing the IRQ to one of those alternate possibilities
> works fine. On others however, it really isn't a good idea. As theres no
> way to tell which systems are good and bad in advance, this patch simply
> ensures that ACPI does not change an IRQ if the BIOS has pre-allocated it.
Nice, the patch below, which Chris told me is from you, fixed my
problems too. It is against 2.6.0-test5-bk3 and fixes bug number 1186
in the bugzilla.kernel.org database.
Many thanks for this work, I really appreciate it.
thanks,
greg k-h
test5-bk_current
===== drivers/acpi/pci_link.c 1.13 vs edited =====
--- 1.13/drivers/acpi/pci_link.c Mon Sep 8 05:51:03 2003
+++ edited/drivers/acpi/pci_link.c Tue Sep 16 16:16:31 2003
@@ -456,7 +456,6 @@
irq = link->irq.active;
} else {
irq = link->irq.possible[0];
- }
/*
* Select the best IRQ. This is done in reverse to promote
@@ -466,6 +465,7 @@
if (acpi_irq_penalty[irq] > acpi_irq_penalty[link->irq.possible[i]])
irq = link->irq.possible[i];
}
+ }
/* Attempt to enable the link device at this IRQ. */
if (acpi_pci_link_set(link, irq)) {
next prev parent reply other threads:[~2003-09-17 1:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 23:11 [PATCH] 2.6.0-test4 Don't change BIOS allocated IRQs Andrew de Quincey
2003-09-16 23:11 ` Andrew de Quincey
[not found] ` <200309170011.03630.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-17 0:29 ` Chris Wright
2003-09-17 0:29 ` Chris Wright
2003-09-17 1:02 ` Greg KH [this message]
2003-09-17 1:02 ` [ACPI] " Greg KH
2003-09-17 8:08 ` Andrew de Quincey
[not found] ` <20030917010254.GA1640-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2003-09-17 8:08 ` Andrew de Quincey
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=20030917010254.GA1640@kroah.com \
--to=greg-u8xffu+wg4eavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org \
--cc=chrisw-3NddpPZAyC0@public.gmane.org \
--cc=linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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 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.