From: Len Brown <len.brown@intel.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: "Allen Martin" <AMartin@nvidia.com>,
ross@datscreative.com.au,
"Christian Kröner" <christian.kroener@tu-harburg.de>,
Linux-Nforce-Bugs <Linux-Nforce-Bugs@exchange.nvidia.com>,
linux-kernel@vger.kernel.org,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: IO-APIC on nforce2 [PATCH]
Date: 22 Apr 2004 00:00:39 -0400 [thread overview]
Message-ID: <1082606439.16333.188.camel@dhcppc4> (raw)
In-Reply-To: <20040416082730.GB22226@mail.shareable.org>
On Fri, 2004-04-16 at 04:27, Jamie Lokier wrote:
> Len Brown wrote:
> > As we expected, an automatic workaround based on chip-set would
> > fail because some BIOS's are fixed and some are not.
>
> Does the workaround actually fail with the fixed BIOSes?
A fixed BIOS will not have a bogus IRQ2->pin-2 mapping,
so the acpi_skip_timer_override workaround would not
find an entry to ignore, and would become a NOP.
So if
1. all nforce2 chipsets have timer connected to pin0
2. we can safely discover we're on nforce2 early enough,
like andi did on x86_64
then we could apply the workaround automatically always
w/o any harm.
-Len
next prev parent reply other threads:[~2004-04-22 4:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 18:33 IO-APIC on nforce2 [PATCH] Allen Martin
2004-04-15 19:20 ` Craig Bradney
2004-04-15 19:50 ` Len Brown
2004-04-16 8:27 ` Jamie Lokier
2004-04-22 4:00 ` Len Brown [this message]
2004-04-22 13:22 ` Maciej W. Rozycki
2004-04-22 13:53 ` Christian Kröner
2004-04-22 15:27 ` Len Brown
2004-04-22 15:40 ` Maciej W. Rozycki
2004-04-22 16:15 ` Christian Kröner
-- strict thread matches above, loose matches on Subject: below --
2004-04-23 1:23 Allen Martin
2004-04-23 15:39 ` Maciej W. Rozycki
2004-04-16 16:41 Allen Martin
2004-04-14 21:01 Christian Kröner
2004-04-15 0:35 ` Peter Clifton
2004-04-15 0:29 ` Craig Bradney
2004-04-15 0:41 ` Ross Dickson
2004-04-13 1:17 IO-APIC on nforce2 Ross Dickson
2004-04-13 5:08 ` Len Brown
2004-04-13 7:03 ` Ross Dickson
2004-04-14 1:02 ` IO-APIC on nforce2 [PATCH] Len Brown
2004-04-14 5:02 ` Ross Dickson
2004-04-14 6:30 ` Jamie Lokier
2004-04-14 10:37 ` Maciej W. Rozycki
2004-04-15 19:28 ` Len Brown
2004-04-14 19:57 ` Christian Kröner
2004-04-15 0:17 ` Len Brown
2004-04-15 1:48 ` Ross Dickson
2004-04-15 17:09 ` Christian Kröner
2004-04-15 15:21 ` Zwane Mwaikambo
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=1082606439.16333.188.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=AMartin@nvidia.com \
--cc=Linux-Nforce-Bugs@exchange.nvidia.com \
--cc=christian.kroener@tu-harburg.de \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=ross@datscreative.com.au \
/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.