From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: torvalds@osdl.org, lkml <linux-kernel@vger.kernel.org>,
acpi-devel@lists.sourceforge.net, linux-acpi@intel.com
Subject: Re: [PATCH] Next round of ACPI IRQ fixes (VIA ACPI fixed)
Date: Fri, 05 Sep 2003 17:35:10 -0400 [thread overview]
Message-ID: <3F59018E.5060604@pobox.com> (raw)
In-Reply-To: <200309051958.02818.adq_dvb@lidskialf.net>
Andrew de Quincey wrote:
> Hi, this is my next round of ACPI IRQ fixes. Attached are patches for linux-2.4.23-pre3 and linux-2.6.0-test4.
>
> Please CC me on any replies. I seem to be having issues with vger.kernel.org right now.
>
>
> This patch addresses the following issues:
>
> 1) ACPI now drops back to PIC mode if configuration in APIC mode fails.
>
> 2) Removed 2 lines of erroneous code in mpparse.c which causes IO-APICs to be misconfigured.
>
> 3) ACPI now supports PIC controllers properly.
>
> 4) This patch includes a patch by "Jun Nakajima" <jun.nakajima@intel.com> which fixes ACPI IRQ routing for all
> VIA motherboards I have had tested so far. I've included it in this patch as it changes one of the same files.
>
> 5) Now retries with an extended IRQ descriptor if programming a link device with a "standard" IRQ descriptor fails.
>
> This has already been tested successfully by multiple people.
Patch looks pretty good. It is _very_ difficult to pick through, and
pick apart, though.
Consider that one or more people reading your email (a) would want some
of these fixes but (b) already have some of these fixes.
This is why we _really_ need you to split up your patches. Multiple
split-up patches, one per email, is preferred. Don't worry about
sending us too much email: we like it like that.
As an aside, I know at least part of the VIA irq routing stuff still
needs fixing. For some on-board VIA southbridge devices, irq routing is
accomplished by writing the PCI_INTERRUPT_xxx values to PCI config
registers of the target device; for others, the normal pirq PCI config
registers on the southbridge are used. Alan's new irq stuff in 2.4.x
IMO should be merged into 2.6.x soonish, as Alan's work makes a big step
towards making it possible to fix some of the harder-to-fix irq routing
problems.
Jeff
next prev parent reply other threads:[~2003-09-05 21:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 18:58 [PATCH] Next round of ACPI IRQ fixes (VIA ACPI fixed) Andrew de Quincey
2003-09-05 21:35 ` Jeff Garzik [this message]
2003-09-05 23:16 ` [ACPI] " Andrew de Quincey
2003-09-05 22:28 ` Jeff Garzik
2003-09-05 22:28 ` Andrew Morton
2003-09-05 22:56 ` Randy.Dunlap
2003-09-06 0:15 ` [PATCH] 2.4.23-pre3 ACPI fixes series (1/3) Andrew de Quincey
2003-09-10 11:45 ` Bernhard Rosenkraenzer
2003-09-10 21:27 ` Andrew de Quincey
2003-09-10 15:31 ` Daniel Egger
2003-09-06 0:15 ` [PATCH] 2.4.23-pre3 ACPI fixes series (2/3) Andrew de Quincey
2003-09-06 0:15 ` [PATCH] 2.4.23-pre3 ACPI fixes series (3/3) Andrew de Quincey
2003-09-06 0:57 ` [PATCH] 2.6.0-test4 ACPI fixes series (1/4) Andrew de Quincey
2003-09-06 0:57 ` [PATCH] 2.6.0-test4 ACPI fixes series (2/4) Andrew de Quincey
2003-09-06 0:57 ` [PATCH] 2.6.0-test4 ACPI fixes series (3/4) Andrew de Quincey
2003-09-06 0:57 ` [PATCH] 2.6.0-test4 ACPI fixes series (4/4) Andrew de Quincey
2003-09-06 1:22 ` Jeff Garzik
2003-09-06 12:27 ` [ACPI] " Andrew de Quincey
2003-09-06 13:45 ` Andi Kleen
2003-09-08 19:46 ` Mikael Pettersson
2003-09-06 15:47 ` [ACPI] " Alan Cox
2003-09-07 14:54 ` Andrew de Quincey
2003-09-07 17:59 ` Alan Cox
2003-09-07 20:19 ` Andrew de Quincey
2003-09-06 0:02 ` [ACPI] Re: [PATCH] Next round of ACPI IRQ fixes (VIA ACPI fixed) Chris Wright
2003-09-06 1:21 ` Andrew de Quincey
2003-09-06 0:30 ` Jeff Garzik
2003-09-06 2:03 ` Chris Wright
2003-09-06 12:32 ` Andrew de Quincey
2003-09-11 1:36 ` 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=3F59018E.5060604@pobox.com \
--to=jgarzik@pobox.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=adq_dvb@lidskialf.net \
--cc=linux-acpi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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