From: Tony Lindgren <tony@atomide.com>
To: Len Brown <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org,
acpi-devel-request@lists.sourceforge.net, patches@x86-64.org,
Andi Kleen <ak@suse.de>,
pavel@ucw.cz, ccheney@debian.org
Subject: Re: [PATCH] x86_64 VIA chipset IOAPIC fix
Date: Thu, 25 Mar 2004 16:47:16 -0800 [thread overview]
Message-ID: <20040326004715.GL7967@atomide.com> (raw)
In-Reply-To: <1080260113.757.67.camel@dhcppc4>
* Len Brown <len.brown@intel.com> [040325 16:15]:
>
> I think we need to tread carefully in this area.
> Ignoring the result of _CRS means that we really don't
> know if the IRQ is programmed or not. We could attach
> a device to the wrong IRQ and not know it.
> Unclear if that risk is a better policy than pretending
> we confirmed that the IRQ was successfully programmed
> when it may not have been.
Yeah, that's what I thought too.
> perhaps you can attach this patch to 1581 and we can work there
> to come up with a "disabled links patch" that makes sense
> for all systems. We might find that we need only a small
> VIA-specific tweak to an otherwise robust policy.
OK, I've attached it there. While waiting for the generic fix, I've also
posted the patch to my amd64 page for m6805 and m6807 owners who might
the patch handy:
http://www.muru.com/linux/amd64/
> If your dmesg and acpidmp are different from 2090, it would
> be good to attach them also.
No, looks the same.
Regards,
Tony
next prev parent reply other threads:[~2004-03-26 0:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 3:34 [PATCH] x86_64 VIA chipset IOAPIC fix Tony Lindgren
2004-03-26 0:15 ` Len Brown
2004-03-26 0:47 ` Tony Lindgren [this message]
2004-03-26 3:04 ` Chris Cheney
2004-03-26 3:11 ` Tony Lindgren
2004-03-26 3:13 ` Len Brown
2004-03-26 3:20 ` Chris Cheney
2004-03-26 3:35 ` Tony Lindgren
2004-03-26 4:21 ` Len Brown
2004-03-26 4:34 ` Chris Cheney
2004-03-26 5:10 ` Tony Lindgren
2004-03-30 3:17 ` Randy.Dunlap
2004-03-26 5:02 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2004-04-16 10:53 HurryLin
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=20040326004715.GL7967@atomide.com \
--to=tony@atomide.com \
--cc=acpi-devel-request@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=ccheney@debian.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.org \
--cc=pavel@ucw.cz \
/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