From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755694AbYHTLE1 (ORCPT ); Wed, 20 Aug 2008 07:04:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751952AbYHTLES (ORCPT ); Wed, 20 Aug 2008 07:04:18 -0400 Received: from metis.extern.pengutronix.de ([83.236.181.26]:50440 "EHLO metis.extern.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751813AbYHTLES convert rfc822-to-8bit (ORCPT ); Wed, 20 Aug 2008 07:04:18 -0400 From: Juergen Beisert Organization: Pengutronix - Linux Solutions for Science and Industry To: Ingo Molnar Date: Wed, 20 Aug 2008 13:03:59 +0200 User-Agent: KMail/1.9.9 Cc: Samuel Sieb , linux-kernel@vger.kernel.org, "Rafael C. de Almeida" , Thomas Gleixner , "H. Peter Anvin" , Magnus Damm , takada References: <48841A92.4020301@sieb.net> <200808201144.02919.jbe@pengutronix.de> <20080820104538.GF2816@elte.hu> In-Reply-To: <20080820104538.GF2816@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <200808201304.00956.jbe@pengutronix.de> X-SA-Exim-Connect-IP: 83.236.181.29 X-SA-Exim-Mail-From: jbe@pengutronix.de Subject: Re: kernel won't boot on a Cyrix MediaGXm (Geode ) X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on metis.extern.pengutronix.de) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mittwoch, 20. August 2008, Ingo Molnar wrote: > * Juergen Beisert wrote: > > On Mittwoch, 20. August 2008, Ingo Molnar wrote: > > > * Samuel Sieb 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