From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:6f8:1178:4:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1YQWUG-0004pY-3f for barebox@lists.infradead.org; Wed, 25 Feb 2015 07:34:29 +0000 Date: Wed, 25 Feb 2015 08:34:06 +0100 From: Sascha Hauer Message-ID: <20150225073406.GS12209@pengutronix.de> References: <1424789630-10461-1-git-send-email-m.olbrich@pengutronix.de> <1424789630-10461-3-git-send-email-m.olbrich@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1424789630-10461-3-git-send-email-m.olbrich@pengutronix.de> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH 3/3] ARM Samsung: add simple NAND barebox update handler To: Michael Olbrich Cc: barebox@lists.infradead.org On Tue, Feb 24, 2015 at 03:53:50PM +0100, Michael Olbrich wrote: > Signed-off-by: Michael Olbrich > --- > > I'm not sure if writing to /dev/nand0.barebox.bb is correct. But from what > I can tell, the nand boot code cannot handle bad blocks, so it probably > doesn't matter anyways. So when the boot code can't handle bad blocks I think you should use the non bb device. Then you'll realize during writing that it won't work, not only during booting Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox