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
    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/

    \
     
     \ /
      Last update: 2005-03-22 14:03    [W:0.022 / U:60.452 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site