From: Lars <terraformers@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc3: nforce2, no C1 disconnect fixup applied
Date: Thu, 10 Jun 2004 23:36:17 +0200 [thread overview]
Message-ID: <caak85$9vg$1@sea.gmane.org> (raw)
In-Reply-To: 200406101558.54240.bzolnier@elka.pw.edu.pl
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.
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.
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 ]
next prev parent reply other threads:[~2004-06-10 21:36 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 [this message]
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
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='caak85$9vg$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