Hi Imre, On Thu, Oct 09, 2014 at 10:54:19PM +0200, Maxime Ripard wrote: > Hi Imre, > > On Thu, Oct 09, 2014 at 10:30:46PM +0200, Imre Kaloz wrote: > > Hi, > > > > On Thu, 09 Oct 2014 17:59:25 +0200, Maxime Ripard > > <[email protected]> wrote: > > > > >This patch adds a new profile for the Mirabox, and fixes a few things > > >along the way, mostly because of the Mirabox NAND page size that > > >differs from the other mvebu boards (and most of the boards supported > > >by OpenWRT apparently). > > > > At first look they look fine, except the UBI* options in the > > profiles. We always want to build images for all boards, so I would > > keep those in the image Makefile and keep the profiles for the bare > > minimum like on other targets. > > Ok, how would you support boards with alternate UBI and UBIFS options > then? By hacking into Image/Build like what's done currently for mamba?
Can we move forward on this? Enforcing UBI options for the whole target is not a reasonable option. You won't be able to use any generated image on a board that doesn't have the same eraseblock, page and sub-page sizes. Mirabox is in this case, the not-yet supported Armada 385 RD too, and presumably a lot of others. I've looked more in the include/image.mk file, and the only way for now to deal with this aside from setting it at the target level is to set it in the profile. If we want to build images that boot on every boards for a given target, regardless of the profile, this is indeed something that will not work. Should I introduce a "board"? Do you have something else in mind? Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
signature.asc
Description: Digital signature
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
