From: Chris Wright <chrisw@osdl.org>
To: Tomasz Lemiech <szpajder@staszic.waw.pl>
Cc: Chris Wright <chrisw@osdl.org>,
torvalds@osdl.org, len.brown@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.12.2 acpi_register_gsi() patch causes problems on Asus A7V333 motherboard
Date: Tue, 12 Jul 2005 13:15:19 -0700 [thread overview]
Message-ID: <20050712201519.GB19052@shell0.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0507122153110.24219@boss.staszic.waw.pl>
* Tomasz Lemiech (szpajder@staszic.waw.pl) wrote:
> On Tue, 12 Jul 2005, Chris Wright wrote:
>
> >>- 2.6.12.2 with acpi_register_gsi() one-line fix works without problems
>
> My apologies - I meant: "_without_ acpi_register_gsi() one-line fix". That
> is, _reverting_
> http://www.kernel.org/git/?p=linux/kernel/git/gregkh/linux-2.6.12.y.git;a=commit;h=1ef0867a529b222b8ff659d68140df8d5d6a45f2
> from 2.6.12.2 fixes the problem.
Can you verify that the patch below (w/out reverting that patch, apply
on top of) fixes it for you?
thanks,
-chris
--
---
drivers/acpi/pci_irq.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/pci_irq.c b/drivers/acpi/pci_irq.c
--- a/drivers/acpi/pci_irq.c
+++ b/drivers/acpi/pci_irq.c
@@ -433,7 +433,7 @@ acpi_pci_irq_enable (
printk(KERN_WARNING PREFIX "PCI Interrupt %s[%c]: no GSI",
pci_name(dev), ('A' + pin));
/* Interrupt Line values above 0xF are forbidden */
- if (dev->irq >= 0 && (dev->irq <= 0xF)) {
+ if (dev->irq > 0 && (dev->irq <= 0xF)) {
printk(" - using IRQ %d\n", dev->irq);
acpi_register_gsi(dev->irq, ACPI_LEVEL_SENSITIVE, ACPI_ACTIVE_LOW);
return_VALUE(0);
next prev parent reply other threads:[~2005-07-12 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 18:08 2.6.12.2 acpi_register_gsi() patch causes problems on Asus A7V333 motherboard Tomasz Lemiech
2005-07-12 18:20 ` Chris Wright
2005-07-12 20:00 ` Tomasz Lemiech
2005-07-12 20:15 ` Chris Wright [this message]
2005-07-13 8:00 ` Tomasz Lemiech
2005-07-13 8:02 ` Chris Wright
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=20050712201519.GB19052@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szpajder@staszic.waw.pl \
--cc=torvalds@osdl.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