Hi, On Wed, Jan 14, 2015 at 01:03:49PM +0100, Imre Kaloz wrote: > Hi Maxime, > > On Tue, 13 Jan 2015 16:56:41 +0100, Maxime Ripard > <maxime.rip...@free-electrons.com> wrote: > > >+$(eval $(call MultiProfile,Generic,$(PROFILES_LIST))) > >+$(eval $(call MultiProfile,Evalboards,$(PROFILES_LIST))) > > Profile names should be sourced from the profiles. > > >- $(foreach nandboard,$(NANDBOARDS),$(call > >BuildSysupgrade,$(1),$(nandboard));) > >+ $(call Image/Build/Profile/$(PROFILE)/BuildSysupgrade,$(1)) > > UBI and BuildSysUpgrade is there for NAND only.
Ok. I still think UBI might be a good choice for some !NAND-based boards, but point taken for BuildSysUpgrade. > On boards with nor (unless you come up with a really good reason to hack > UBI) It's not really a hack. UBI is perfectly capable on running on NOR, and it's even mentionned in their documentation on various occasions. > you should stick to squashfs+jffs2. Ok. > Also, each NOR based board should have "firmware" partition and use > the OpenWrt MTDSPLIT framework and should have a single, flashable > firmware image file created instead of separate uImage+rootfs stuff. I'm not really familiar with MTDSPLIT, but I'll look into that. Thanks! Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
signature.asc
Description: Digital signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
