Phil Blundell wrote:
> On Sat, 2009-05-23 at 22:23 +0200, Alessandro GARDICH wrote:
>> At now I modify qemux86.conf cause usually EXTRA_IMAGECMD is in the
>> machine config file, but to add hardware specific parameters (flash size
>> and erase size). I'm not sure if is the right place. Probably in the
>> distro configuration could be better.
>
> The distro config probably is the right place for this. After all, the
> number of inodes you need depends primarily on the number of files that
> you're going to ship in the rootfs, and that in turn is primarily
> influenced by the DISTRO's policies rather than by any inherent aspect
> of the MACHINE.
>
> The other uses of EXTRA_IMAGECMD that I guess you're thinking of are
> mostly to do with jffs2 parameters, which are rather different in that
> they're determined by the specifics of the hardware in use and hence do
> go with the MACHINE rather than the DISTRO.
>
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
true, reform the patch for kaeilos.conf
Acked-by: Marco Cavallini <m.cavallini@koansoftware.com>
# Also, it appears that no locales fit in 16Mb for now. "C" locale rules!
IMAGE_LINGUAS = '${@base_less_or_equal("ROOT_FLASH_SIZE", "16", "", "en-us", d)}'
+# increase inode/block ratio for ext2 filesystem
+EXTRA_IMAGECMD_ext2 = "-i 4096"
# set feed path variables
FEED_BASEPATH = "feeds/2008/${ANGSTROM_PKG_FORMAT}/${LIBC}/"