public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Marco Tralli" <marco.tralli@snapon.com>
To: "Juergen Beisert" <juergen127@kreuzholzen.de>,
	<linux-kernel@vger.kernel.org>
Cc: "Jordan Crouse" <jordan.crouse@amd.com>
Subject: Re: kernel 2.6.23-rc6 hangs on Geode GX1
Date: Thu, 27 Sep 2007 18:33:45 +0200	[thread overview]
Message-ID: <00e101c80124$32ef67a0$7502a8c0@snaponglobal.com> (raw)
In-Reply-To: 200709271813.26103.juergen127@kreuzholzen.de

Thanks Juergen,

> It runs stable on 5 different GX1 systems.
>
> But I do not use a standard BIOS. I'm using LinuxBIOS instead. But I'm
also using
> these patches.
>

set_cx86_inc was one of performance trick called by geode_configure
I didn't find any documentation about "incrementor margin" before.

But since I'm running on 300MHz GX1 the default kernel is now broken for me!


> --- linux-2.6.22.orig/arch/i386/kernel/cpu/cyrix.c
> +++ linux-2.6.22/arch/i386/kernel/cpu/cyrix.c
> @@ -169,7 +169,7 @@ static void __cpuinit set_cx86_inc(void)
>   setCx86(CX86_PCR1, getCx86(CX86_PCR1) | 0x02);
>   /* PCR0 -- Performance Control */
>   /* Incrementor Margin 10 */
> - setCx86(CX86_PCR0, getCx86(CX86_PCR0) | 0x04);
> + setCx86(CX86_PCR0, getCx86(CX86_PCR0) | 0x05); /* 300MHz CPU */
>   setCx86(CX86_CCR3, ccr3); /* disable MAPEN */
>  }
>

I will try your patch

But again, if those tricks are so system dependent  I suggest to kernel
people to let disable it in default configuration.


Marco


  reply	other threads:[~2007-09-27 16:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 14:44 kernel 2.6.23-rc6 hangs on Geode GX1 Marco Tralli
2007-09-27 15:30 ` R. J. Wysocki
2007-09-27 15:22   ` Jordan Crouse
2007-09-27 16:05     ` Rafael J. Wysocki
2007-09-27 16:21       ` Marco Tralli
2007-09-27 16:05     ` Marco Tralli
2007-09-27 16:13 ` Juergen Beisert
2007-09-27 16:33   ` Marco Tralli [this message]
2007-09-28  8:33   ` *SPAM* " Juergen Beisert
2007-09-28  8:35   ` Marco Tralli

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='00e101c80124$32ef67a0$7502a8c0@snaponglobal.com' \
    --to=marco.tralli@snapon.com \
    --cc=jordan.crouse@amd.com \
    --cc=juergen127@kreuzholzen.de \
    --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