From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from 2.mo2.mail-out.ovh.net ([188.165.53.149] helo=mo2.mail-out.ovh.net) by merlin.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux)) id 1T8UJK-0002qh-CH for barebox@lists.infradead.org; Mon, 03 Sep 2012 10:55:19 +0000 Received: from mail21.ha.ovh.net (b6.ovh.net [213.186.33.56]) by mo2.mail-out.ovh.net (Postfix) with SMTP id 496E3DC423B for ; Mon, 3 Sep 2012 13:00:34 +0200 (CEST) Date: Mon, 3 Sep 2012 12:55:34 +0200 From: Jean-Christophe PLAGNIOL-VILLARD Message-ID: <20120903105534.GA19931@game.jcrosoft.org> References: <201209031232.56813.jbe@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <201209031232.56813.jbe@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-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [RFC] Dedicated command to make a target bootable with Barebox To: Juergen Beisert Cc: barebox@lists.infradead.org On 12:32 Mon 03 Sep , Juergen Beisert wrote: > Hi all, > > currently I'm working on the difficult process to make an i.MX35 SoC boot from > an externally connected NAND device. > > Nothing special with it, only the NAND flash controller in the i.MX35 (also in > i.MX25, i.MX27 and i.MX31) is braindamaged broken. This controller loses the > factory bad block markers when used without a workaround and losing these > markers is a _really_ bad idea. > > But to use the workaround on these SoCs it needs a complicated preparation of > the NAND. Doing it manually is very error prone. And this kind of preparation > has to be kept when the system should be updated and so on. Not easy to > explain and so much more chances for the user to brick the system while the > update process. > > This makes me think about a dedicated command which is responsible to make the > target bootable and does all the (more or less complicated) steps to ensure > the next time it gets powered it's able to boot again. > > There are more architectures which needs a complicated setup to be able to > boot it from some kind of externally connected devices like NAND or eMMCs for > example. Some needs special NAND checksums only for the bootloader, others > needs to keep the partition table even if the bootloader gets updated and so > on. > > Would it be possible to share one command (or one group of commands) by all > architectures? And each architecture adds its special code to the command? > > What kind of setup procedures we must cover with such a command? > > My examples: > > - for the Freescale i.MX SoCs with the broken NFC we must write the bootloader > in a different way than all the remaining data into the NAND device > - for the Samsung S36410 we must save the factory bad block markers first to > support booting from NAND as its internal ROM expects the checksums at a > strange offset in the OOB area On some ST SoC it's the same I think we do not need any command we just need to specify it as mtd level for a specific mtd part Best Regards, J. _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox