From: Len Brown <len.brown@intel.com>
To: Allen Martin <AMartin@nvidia.com>
Cc: 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: 15 Apr 2004 15:50:25 -0400 [thread overview]
Message-ID: <1082058625.24423.161.camel@dhcppc4> (raw)
In-Reply-To: <DCB9B7AA2CAB7F418919D7B59EE45BAF49FB9D@mail-sc-6-bk.nvidia.com>
On Thu, 2004-04-15 at 14:33, Allen Martin wrote:
> It was a bug in our original nForce reference BIOS that we gave out to vendors. Since then we fixed the reference BIOS, but since it was after products shipped, most of the motherboard vendors won't pick up the change unless they get complaints from customers.
>
> We've fixed it for our reference BIOS for future products though.
Great!
Knowing this makes the path clear.
As we expected, an automatic workaround based on chip-set would
fail because some BIOS's are fixed and some are not.
So we either leave the workaround as manual bootparam
or try to enumerate all BIOS versions with the bug
in dmi_scan. I'm content to do the former. If distros
have trouble supporting nforce2 systems, they may want to add
to the later.
thanks,
-Len
ps.
I'm also excited to see a linux-nforce-bugs@exchange.nvidia.com alias
on your note. Perhaps you can explain how we should use it. Should
this alias be included on discussions of the more important issue --
the system hang that seems to be related to HALT in idle/C1?
next prev parent reply other threads:[~2004-04-15 19:51 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 [this message]
2004-04-16 8:27 ` Jamie Lokier
2004-04-22 4:00 ` Len Brown
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=1082058625.24423.161.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox