From: Lars <terraformers@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc3: nforce2, no C1 disconnect fixup applied
Date: Fri, 11 Jun 2004 01:01:59 +0200 [thread overview]
Message-ID: <caap8q$m51$1@sea.gmane.org> (raw)
In-Reply-To: 200406110035.48711.bzolnier@elka.pw.edu.pl
Bartlomiej Zolnierkiewicz wrote:
> On Friday 11 of June 2004 00:19, Lars wrote:
>> just learned that
>> setpci -H1 -s 0:0.0 6C.L=0x9F01FF01
>> enables C1 *and* the 80ns stability fix.
>>
>> looks like i have to stick with my ugly little workaround for a while
>
> "ugly"?
just kiddin' ;)
>
> We can probably change kernel fixup to always do & 0x9F01FF01
> but adding "force C1HD" kernel options sounds insane.
i guess that always applying 0x9F01FF01 will force c1 for all users
to *on* again, because the 9F value triggers this.
its my understanding that
0x9F01FF01 enables c1 and fix
0x0F01FF01 disables c1, enables fix
0x0F0FFF01 disables c1 and fix
am i right ?
best,
lars
next prev parent reply other threads:[~2004-06-10 23:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 12:18 2.6.7-rc3: nforce2, no C1 disconnect fixup applied Lars
2004-06-10 12:59 ` Bartlomiej Zolnierkiewicz
2004-06-10 13:26 ` Lars
2004-06-10 13:58 ` Bartlomiej Zolnierkiewicz
2004-06-10 21:36 ` Lars
2004-06-10 21:56 ` Bartlomiej Zolnierkiewicz
2004-06-10 22:00 ` Craig Bradney
2004-06-10 22:26 ` Bartlomiej Zolnierkiewicz
2004-06-10 22:32 ` Craig Bradney
2004-06-10 22:53 ` Bartlomiej Zolnierkiewicz
2004-06-10 22:19 ` Lars
2004-06-10 22:35 ` Bartlomiej Zolnierkiewicz
2004-06-10 23:01 ` Lars [this message]
2004-06-10 23:23 ` Bartlomiej Zolnierkiewicz
2004-06-10 23:38 ` Lars
2004-06-10 14:51 ` Lenar Lõhmus
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='caap8q$m51$1@sea.gmane.org' \
--to=terraformers@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/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