Re: 2.6.7-rc3: nforce2, no C1 disconnect fixup applied

[Craig Bradney <cbradney@zip.com.au>]

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

On Thu, 2004-06-10 at 23:56, Bartlomiej Zolnierkiewicz wrote:
> 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.


Except if people have the trouble when installing Linux.... ok, yes,
they can still be done somehow, but thats just ugly for the "put cd in
and install" users. Surely the kernel should be detecting this stuff and
using various options as required.

Craig

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]