From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: white phoenix <white.phoenix@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: nforce2 bugs?
Date: Wed, 29 Sep 2004 23:17:44 +0100 [thread overview]
Message-ID: <1096496263.16768.12.camel@localhost.localdomain> (raw)
In-Reply-To: <e2ae0e3b04092915427fcff604@mail.gmail.com>
On Mer, 2004-09-29 at 23:42, white phoenix wrote:
> [x86] fix lockups with APIC support on nForce2
Looks reasonable (anyone from Nvidia care to ack any of these)
> Add PCI quirk to disable Halt Disconnect and Stop Grant Disconnect
> (based on athcool program by Osamu Kayasono).
Is this always safe - if not why does the BIOS not do it.
APIC one I don't have enough background on
next prev parent reply other threads:[~2004-09-29 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 22:42 nforce2 bugs? white phoenix
2004-09-29 22:17 ` Alan Cox [this message]
2004-09-30 0:32 ` white phoenix
2004-09-30 9:25 ` Prakash K. Cheemplavam
2004-09-30 14:24 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2004-09-30 15:43 Andy Currid
2004-09-30 16:59 ` Maciej W. Rozycki
2004-10-01 3:41 ` Ross Dickson
2004-10-01 11:16 ` Jesse Stockall
2004-10-02 2:13 Jesse Allen
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=1096496263.16768.12.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=white.phoenix@gmail.com \
/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