On Mon, Jul 15, 2013 at 12:11:19PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 22:17 Wed 10 Jul , Sascha Hauer wrote: > > On Wed, Jul 10, 2013 at 05:50:28PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote: > > > > > > It's the same binding, yes. > > > > > > > > > > I do not like to duplicate the information can de avoid this > > > > > > > > Which information? The Documentation? > > > > > > no the fact we need to describe the nor-partitions twice, for barebox and for > > > linux in the DTB > > > > No, barebox should copy (or move) the partition nodes to where Linux > > finds them before starting the kernel. This is not yet implemented > > though. > > > > Another option of course is to do the obvious and put the partitions > > under the mtd device in the first place. I decided against this since > > I have the strong feeling that the hardware description should be > > separated from clearly board (or project or usecase) specific partition > > descriptions. > > here we need to be more generic as it's booloader specific not really barebox As mentioned I moved from /chosen/barebox to /chosen. I'd like to keep the "barebox," prefixes in the compatible strings as long as barebox is the only bootloader doing such stuff. It's more convenient to drop the prefix later than it is to realize that we introduced a too generic binding. 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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
