From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: trouble with ext2 filesystem
Date: Tue, 09 Jun 2009 11:42:43 +0200 [thread overview]
Message-ID: <4A2E2E93.1090005@gmail.com> (raw)
In-Reply-To: <4A18F6B7.8060708@gremlin.it>
Alessandro GARDICH ha scritto:
> 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
>
>
>
>
Thank you for the patch.
Acked-by: Marco Cavallini <m.cavallini@koansoftware.com>
next prev parent reply other threads:[~2009-06-09 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 20:23 trouble with ext2 filesystem Alessandro GARDICH
2009-05-23 20:43 ` Phil Blundell
2009-05-24 7:26 ` Alessandro GARDICH
2009-06-09 9:42 ` Marco Cavallini [this message]
2009-05-24 7:29 ` Alessandro GARDICH
2009-05-24 7:29 ` Alessandro GARDICH
2009-06-09 8:49 ` Marco Cavallini
2009-06-09 9:24 ` Alessandro GARDICH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A2E2E93.1090005@gmail.com \
--to=koansoftware@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.