On 2/6/08, Scott Wood <[EMAIL PROTECTED]> wrote: > > -ifneq ($(CONFIG_REDBOOT),"") > > -image-$(CONFIG_PPC_8xx) += zImage.redboot-8xx > > -endif > > +# Board ports in arch/powerpc/platform/8xx/Kconfig > > +image-$(CONFIG_PPC_MPC86XADS) += cuImage.mpc866ads > > +image-$(CONFIG_PPC_MPC885ADS) += zImage-dtb.mpc885ads > > mpc885ads is cuImage.
Fixed > > > +# Board ports in arch/powerpc/platform/83xx/Kconfig > > +image-$(CONFIG_MPC8313_RDB) += cuImage.mpc8313erdb > > I don't think we need cuImage for this board (no pre-device-tree u-boot). removed > > > +image-$(CONFIG_MPC837x_MDS) += cuImage.mpc8377_mds \ > > + cuImage.mpc8378_mds \ > > + cuImage.mpc8379_mds > > I really hope we don't need cuImage for these. :-) removed > > I wish CONFIG_BOARD_FOO could be annotated with properties such as image > name and bootwrapper platform, rather than having to maintain > separate lists... Oh well. Me too. Fortunately this is probably only an issue for images which require an embedded dtb. Images that get their device trees from elsewhere can follow the lead of CONFIG_DEFAULT_UIMAGE. Over time this issue will diminish. Thanks for the feedback Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
