From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiko Schocher Date: Tue, 17 Feb 2009 08:19:05 +0100 Subject: [U-Boot] [PATCH 09/12] 8360, kmeter1: added bootcount feature. In-Reply-To: <20090216194009.4e0be0ee.kim.phillips@freescale.com> References: <49931853.4090301@denx.de> <20090216194009.4e0be0ee.kim.phillips@freescale.com> Message-ID: <499A64E9.7070202@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Kim, Kim Phillips wrote: > On Wed, 11 Feb 2009 19:26:27 +0100 > Heiko Schocher wrote: > >> add CONFIG_BOUTCOUNT_LIMIT feature for 8360 CPU. > > s/BOUT/BOOT/ Ups, I fix it. >> The bootcounter uses 8 bytes from the muram, >> because no other memory was found on this >> CPU for the bootcount feature. So we must >> correct the muram size in DTS before booting >> Linux. >> >> This feature is actual only implemented for >> MPC8360, because not all 83xx CPU have qe, >> and therefor no muram, which this feature > > therefore I fix this, too. >> uses. >> >> This patch also activate this option for >> the kmeter1 board. > > not that I really like enabling this by default, but this patch doesn't > do what you say it does in this last paragraph here (that I can see at Yes, you are right, this is enabled by patch 10/12 in the common config file for all keymile boards. I remove this from the commit message. > least). Can you either rm this paragraph (preferred :) or actually add > BOOTCOUNT_LIMIT to the board's config? Btw, what's the rationale for > enabling this by default, and for this board? The hardware manufacturer wants to use this feature, see: http://www.denx.de/wiki/DULG/UBootBootCountLimit This board (btw, all keymile boards) uses this feature, so it should be enabled. bye Heiko -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany