lkml.org 
[lkml]   [2004]   [Jun]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 2.6.7-rc3: nforce2, no C1 disconnect fixup applied
Date
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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:03    [W:0.052 / U:0.924 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site