Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263101AbUFJVwN (ORCPT ); Thu, 10 Jun 2004 17:52:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263107AbUFJVwN (ORCPT ); Thu, 10 Jun 2004 17:52:13 -0400 Received: from mion.elka.pw.edu.pl ([194.29.160.35]:4237 "EHLO mion.elka.pw.edu.pl") by vger.kernel.org with ESMTP id S263101AbUFJVwJ (ORCPT ); Thu, 10 Jun 2004 17:52:09 -0400 From: Bartlomiej Zolnierkiewicz To: Lars Subject: Re: 2.6.7-rc3: nforce2, no C1 disconnect fixup applied Date: Thu, 10 Jun 2004 23:56:07 +0200 User-Agent: KMail/1.5.3 References: <200406101558.54240.bzolnier@elka.pw.edu.pl> In-Reply-To: Cc: linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200406102356.07920.bzolnier@elka.pw.edu.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2162 Lines: 66 On Thursday 10 of June 2004 23:36, Lars wrote: > thanks > > after some reading, im using now in rc.local: > > ### C1 Halt Disconnect Fix for Chip rev. C17 > setpci -H1 -s 0:0.0 6F=1F > setpci -H1 -s 0:0.0 6E=01 > echo "Applying C1 Halt Disconnect Fix" > > this is for an older nforce2 board (a7n8x 1.04) with rev. C17 chip > and worked fine so far. > > for the newer chip revision it should read > > ### C1 Halt Disconnect Fix for Chip rev. C18D > setpci -H1 -s 0:0.0 6F=9F > setpci -H1 -s 0:0.0 6E=01 > echo "Applying C1 Halt Disconnect Fix" > > first setpci is for the c1 halt bit and the second one enables the > 80ns stability value. Order should be reversed. > i understand that its not good to enable c1 for all boards, but it would > be nice to have the option to force the fixup on boards which > work ok but have no bios option to enable c1. (like the a7n8x) > an bootoption like "forceC1halt" or something would be nice here. It can be perfectly handled in user-space as you've just showed. :-) There is no need to add complexity to the kernel. > cheers, > lars > > >> ...maybe a switch to force the fixup on boards without c1 disconnect > >> bios-settings would do it ? > > > > We can't do that, some older boards hang if C1 disconnect is used. > > > > However you can enable fixup and then C1 Halt Disconnect yourself. :-) > > > > setpci -v -H1 -s 0:0.0 6C.L=$(printf %x $((0x$(setpci -H1 -s 0:0.0 6C.L) > > & 0x9F01FF01))) > > > > - to enable fixup first > > > > setpci -v -H1 -s 0:0.0 6F=$(printf %x $((0x$(setpci -H1 -s 0:0.0 6F) | > > 0x10))) > > > > - to enable C1 Halt Disconnect > > > > [ this is untested as I don't have nForce2 board ] > > - > 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/ - 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/