From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from tango.tkos.co.il ([62.219.50.35]) by canuck.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1R3RPB-0007BS-JN for barebox@lists.infradead.org; Tue, 13 Sep 2011 11:44:02 +0000 Date: Tue, 13 Sep 2011 14:43:53 +0300 From: Baruch Siach Message-ID: <20110913114353.GA25206@sapphire.tkos.co.il> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: 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-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: tftp to flash from linux To: Vanhauwaert Wouter Cc: "barebox@lists.infradead.org" Hi Wouter, On Tue, Sep 13, 2011 at 01:36:31PM +0200, Vanhauwaert Wouter wrote: > To update our platform from within a booted linux, we need tftp to write to > the nand-flash (another partition) directly. > Which one do I use? /dev/mtdx or /dev/mtdblockx? And what happens with bad > blocks here? Are these bad-block aware? Use the nandwrite utility from the mtd-utils package (there's also a Busybox version), and /dev/mtdx. baruch -- ~. .~ Tk Open Systems =}------------------------------------------------ooO--U--Ooo------------{= - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il - _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox