From: Andrew de Quincey <adq_dvb@lidskialf.net>
To: Roger Luethi <rl@hellgate.ch>
Cc: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Where do I send APIC victims?
Date: Wed, 3 Sep 2003 11:48:03 +0100 [thread overview]
Message-ID: <200309031148.03941.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <20030903093808.GA28594@k3.hellgate.ch>
> > with these chipsets. I'm waiting on some docs from VIA to fix this issue.
>
> Which still leaves the question of why it used to work (or made the
> impression it did) with older kernels.
I think on earlier kernels there was a bug in ACPI which prevented it from
being used for PCI IRQ routing. I know this was fixed somewhere in the 2.5.5X
series.
When this bug was fixed, it unfortunately caused my nforce2 board to stop
working because of other IRQ issues, which is how I got into this. Its likely
the same thing causes older kernels to work with Via motherboards to work
'cos ACPI isn't being used for IRQ routing.
2.4.22 has the ACPI from 2.6 backported into it, (which includes my patch for
nforce2 boards) so it will start having the same issue with the BIOS bug in
KT333/KT400 boards.
next prev parent reply other threads:[~2003-09-03 9:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 8:08 Where do I send APIC victims? Roger Luethi
2003-09-03 10:23 ` [ACPI] " Andrew de Quincey
2003-09-03 10:23 ` Andrew de Quincey
2003-09-03 9:38 ` Roger Luethi
2003-09-03 10:30 ` Danny ter Haar
2003-09-03 10:48 ` Andrew de Quincey [this message]
2003-09-03 11:40 ` Alan Cox
2003-09-03 12:53 ` Stephan von Krawczynski
2003-09-03 13:04 ` Vladimir Lazarenko
2003-09-03 14:14 ` Stefan Smietanowski
2003-09-03 16:10 ` Andrew de Quincey
2003-09-03 16:09 ` Andrew de Quincey
2003-09-04 0:28 ` Mike Fedyk
2003-09-03 18:13 ` Marcelo Tosatti
2003-09-03 18:15 ` Marcelo Tosatti
2003-09-03 22:44 ` Sérgio Monteiro Basto
2003-09-03 11:05 ` Matthias Andree
2003-09-03 11:18 Nicolas Mailhot
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=200309031148.03941.adq_dvb@lidskialf.net \
--to=adq_dvb@lidskialf.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rl@hellgate.ch \
/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;
as well as URLs for NNTP newsgroup(s).