All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 09/12] 8360, kmeter1: added bootcount feature.
Date: Tue, 17 Feb 2009 08:19:05 +0100	[thread overview]
Message-ID: <499A64E9.7070202@denx.de> (raw)
In-Reply-To: <20090216194009.4e0be0ee.kim.phillips@freescale.com>

Hello Kim,

Kim Phillips wrote:
> On Wed, 11 Feb 2009 19:26:27 +0100
> Heiko Schocher <hs@denx.de> 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

      reply	other threads:[~2009-02-17  7:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 18:26 [U-Boot] [PATCH 09/12] 8360, kmeter1: added bootcount feature Heiko Schocher
2009-02-17  1:40 ` Kim Phillips
2009-02-17  7:19   ` Heiko Schocher [this message]

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=499A64E9.7070202@denx.de \
    --to=hs@denx.de \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.