public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Samuel Sieb <samuel@sieb.net>,
	linux-kernel@vger.kernel.org,
	"Rafael C. de Almeida" <almeidaraf@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Magnus Damm <magnus@valinux.co.jp>, takada <takada@mbf.nifty.com>
Subject: Re: kernel won't boot on a Cyrix MediaGXm (Geode )
Date: Wed, 20 Aug 2008 13:03:59 +0200	[thread overview]
Message-ID: <200808201304.00956.jbe@pengutronix.de> (raw)
In-Reply-To: <20080820104538.GF2816@elte.hu>

On Mittwoch, 20. August 2008, Ingo Molnar wrote:
> * Juergen Beisert <jbe@pengutronix.de> wrote:
> > On Mittwoch, 20. August 2008, Ingo Molnar wrote:
> > > * Samuel Sieb <samuel@sieb.net> wrote:
> > > > Ingo Molnar wrote:
> > > >> any patch we should pick up to make your box boot?
> > > >
> > > > I've looked through various datasheets and found that the GXm and
> > > > GXLV Geode processors don't have an incrementor.  I attached two
> > > > patches. One only calls the incrementor setup for GX1 or better.  The
> > > > other one removes the incrementor setup entirely.  As the incrementor
> > > > value differs according to clock speed and we would hope that the
> > > > BIOS configures it correctly, it is probably the better one to
> > > > choose.  But I will leave that choice up to you.  Either one works
> > > > for me. :-)
> > >
> > > i went for the commit below and queued it up in tip/x86/urgent - thanks
> > > Samuel.
> > >
> > > what happens if the incrementor is not set up correctly by the BIOS
> >
> > The system can freeze. The clock the incrementor modifies is used for
> > the external SDRAM (something like a delay line or jitter reduction).
> > Thats why its setting depends on the core clock speed.
>
> so, what's the recommendation - is the patch fine? (which removes
> incrementor setting, leaving it to the BIOS)

In my environment I need the incrementor setting in accordance to the CPU core 
frequency, as my BIOS sets a wrong value. Removing it is no solution for me.

But: There where a few bug reports in the last weeks, and all had problems 
when the incrementor setting is changed inside the kernel. Seems only my BIOS 
is broken.

So I vote for removing the incrementor setting. I can life with a local patch 
for my kernels.

Juergen

-- 
Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
    Handelsregister: Amtsgericht Hildesheim, HRA 2686
         Vertretung Sued/Muenchen, Germany
   Phone: +49-8766-939 228 |  Fax: +49-5121-206917-9

  reply	other threads:[~2008-08-20 11:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21  5:11 kernel won't boot on a Cyrix MediaGXm (Geode ) Samuel Sieb
2008-07-21  6:28 ` Juergen Beisert
2008-07-22  5:16   ` Samuel Sieb
2008-07-22  8:08     ` Juergen Beisert
2008-07-23  7:13       ` Samuel Sieb
2008-07-21  6:36 ` Rafael C. de Almeida
2008-07-21 11:47   ` Ingo Molnar
2008-07-22  5:10     ` Samuel Sieb
2008-07-22 10:24       ` Ingo Molnar
2008-07-22 10:51         ` Juergen Beisert
2008-07-23  7:18           ` Samuel Sieb
2008-07-28 15:32             ` Ingo Molnar
2008-07-28 17:58               ` Samuel Sieb
2008-07-29  9:18                 ` Ingo Molnar
2008-07-29  8:15               ` Juergen Beisert
2008-08-07  5:06               ` Samuel Sieb
2008-08-20  9:32                 ` Ingo Molnar
2008-08-20  9:44                   ` Juergen Beisert
2008-08-20 10:45                     ` Ingo Molnar
2008-08-20 11:03                       ` Juergen Beisert [this message]
2008-08-20 11:20                         ` Ingo Molnar

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=200808201304.00956.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=almeidaraf@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus@valinux.co.jp \
    --cc=mingo@elte.hu \
    --cc=samuel@sieb.net \
    --cc=takada@mbf.nifty.com \
    --cc=tglx@linutronix.de \
    /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