From: Len Brown <len.brown@intel.com>
To: Andy Currid <acurrid@nvidia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.4.26 x86_64] fix ACPI PRT entry handling
Date: 22 May 2004 22:58:22 -0400 [thread overview]
Message-ID: <1085281102.12353.716.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615FBF36@hdsmsx403.hd.intel.com>
Accepted.
Thanks,
-Len
On Fri, 2004-05-21 at 18:23, Andy Currid wrote:
> This patch fixes a PCI interrupt routing bug that shows up when
> running
> on x86_64 with ACPI and IOAPIC functionality enabled. Without this
> patch
> in place, the code attempts to route all configurable PCI interrupts
> to
> IRQ 0.
>
> Regards
>
> Andy
> --
> Andy Currid, NVIDIA Corporation
> acurrid@nvidia.com 408 566 6743
>
> --
> diff -Nupr linux-2.4.26/arch/x86_64/kernel/mpparse.c
> linux-2.4.26-patch/arch/x86_64/kernel/mpparse.c
> --- linux-2.4.26/arch/x86_64/kernel/mpparse.c 2004-05-21
> 06:39:40.000000000 -0700
> +++ linux-2.4.26-patch/arch/x86_64/kernel/mpparse.c 2004-05-21
> 06:39:33.000000000 -0700
> @@ -942,8 +942,6 @@ void __init mp_parse_prt (void)
> irq = entry->link.index;
> }
>
> - irq = entry->link.index;
> -
> /* Don't set up the ACPI SCI because it's already set
> up
> */
> if (acpi_fadt.sci_int == irq) {
> entry->irq = irq; /*we still need to set
> entry's irq*/
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next parent reply other threads:[~2004-05-23 2:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FBF36@hdsmsx403.hd.intel.com>
2004-05-23 2:58 ` Len Brown [this message]
2004-05-21 22:23 [PATCH][2.4.26 x86_64] fix ACPI PRT entry handling Andy Currid
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=1085281102.12353.716.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=acurrid@nvidia.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 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.