Path: csiph.com!feeder.erje.net!1.eu.feeder.erje.net!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Borislav Petkov Newsgroups: linux.kernel Subject: Re: [PATCHv7] EDAC, altera: Add Altera L2 Cache and OCRAM EDAC Support Date: Mon, 04 Jan 2016 23:10:02 +0100 Message-ID: References: X-Original-To: Thor Thayer Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alien8.de; s=alien8; t=1451944880; bh=BbiEGmNhwO6RB8zrVsTL/zC/kyXGrt/6DOwHql5R9K4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=HDqT7SowgQnFNHHkuDuXmINF1daNjbthaEt8xf fo8QhQWKt7NaKslCe0wbhRP5jPx4S2AQA6zLn7g2eOBIcbaeWZX5pKinfo9T2C0yDDo h3ftuZH7wJs+qo+rCAursbM+D8CwYA89OCrloiHc4cENEraKeGLdt2enEjlfqgyWsU= Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alien8.de; s=alien8; t=1451944879; bh=BbiEGmNhwO6RB8zrVsTL/zC/kyXGrt/6DOwHql5R9K4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=Dv+M/GmM8Au5IMm1r+sz18RfRkD/Rm98+WTX7m H/vepZU84/xDPDL3GtPvP+LE1lkCg3OmZQmPPbzIQOuBzA9ubmfSrEq/DtaTe7FaEcU DdbEuSAteAHkKnaikvl7knPWHCUGVrlZysek67ng5PahLbru3gXDIMO7PzVOAOS+bo= MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) Sender: robomod@news.nic.it List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Approved: robomod@news.nic.it Lines: 37 Organization: linux.* mail to news gateway X-Original-Cc: Dinh Nguyen , dinh.linux@gmail.com, dougthompson@xmission.com, mchehab@osg.samsung.com, linux@arm.linux.org.uk, linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org X-Original-Date: Mon, 4 Jan 2016 23:01:00 +0100 X-Original-Message-ID: <20160104220100.GT22941@pd.tnic> X-Original-References: <20151119183421.GG6065@pd.tnic> <568AA929.1020801@opensource.altera.com> <20160104194629.GN22941@pd.tnic> <568AD038.7070200@opensource.altera.com> <20160104203045.GO22941@pd.tnic> <568ADA22.70109@opensource.altera.com> <20160104205912.GQ22941@pd.tnic> <568ADC4F.6030007@opensource.altera.com> <20160104210726.GS22941@pd.tnic> <568AE523.7010905@opensource.altera.com> X-Original-Sender: linux-kernel-owner@vger.kernel.org Xref: csiph.com linux.kernel:1301138 On Mon, Jan 04, 2016 at 03:33:23PM -0600, Thor Thayer wrote: > The decision about ECC or non-ECC SDRAM is made before building the Linux > image and must be matched to the appropriate bootloader (ECC or non-ECC). > > If ECC is desired for SDRAM, the bootloader enables SDRAM ECC and then > initializes the memory contents (scrub) before the Linux image is loaded > into SDRAM. > > The ECC syndromes are calculated and stored in SDRAM only when SDRAM ECC is > enabled and the SDRAM data is written (in the bootloader case, this is the > Linux image). If we suddenly switched ECC on during Linux initialization, > we'd be flooded with ECC errors since the ECC syndromes won't match the data > for the Linux image. > > The scrubbing process takes more time to boot which some of our customers > don't want. This is what Dinh was referring to. So that still doesn't have any effect on what's compiled in the EDAC module, AFAICT. You simply build everything in and depending on whether ECC is enabled or not in the bootloader, altera_edac behaves accordingly. On a system with ECC *not* enabled, it would simply have the SDRAM ECC functionality inactive. This is no different than an x86 system where you enter the BIOS and enable or disable ECC. The EDAC module queries whether ECC has been enabled or not and behaves accordingly. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- 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/