From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Sat, 19 Dec 2009 08:59:51 +0100 Subject: [U-Boot] [PATCH 2/9] smi driver support for SPEAr SoCs In-Reply-To: <83d1d72b0912182356u6b140b24g8ee1e97becc6285b@mail.gmail.com> References: <1260955110-5656-1-git-send-email-vipin.kumar@st.com> <1260955110-5656-2-git-send-email-vipin.kumar@st.com> <1260955110-5656-3-git-send-email-vipin.kumar@st.com> <20091216224441.64E914C026@gemini.denx.de> <83d1d72b0912182244yb303c6ai3b61d7b896020c00@mail.gmail.com> <20091219072038.4FEC9E85072@gemini.denx.de> <83d1d72b0912182356u6b140b24g8ee1e97becc6285b@mail.gmail.com> Message-ID: <4B2C87F7.6050902@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Vipin Kumar a ?crit : >> Why don;t you protect sectors where the U-Bootimage and environment >> are stored? > > Since the code is being developed for a development board, erasing and > flashing the uboot is frequent. This is done only to save unprotect every > time before erasing/flashing uboot You could protect the sectors and then have a script in the default environment that automates unprotecting as well as erasing, loading new u-boot and flashing. This way you get the best of both worlds, protection against accidental erasures and simplicity of reflashing. Amicalement, -- Albert.