From: Jack Mitchell <ml@communistcode.co.uk>
To: yocto@yoctoproject.org
Subject: Re: RFC: User configurable recipe features
Date: Thu, 13 Oct 2011 09:30:16 +0100 [thread overview]
Message-ID: <4E96A198.9030109@communistcode.co.uk> (raw)
In-Reply-To: <4E95C787.3020000@linux.intel.com>
On 12/10/2011 17:59, Darren Hart wrote:
>
> On 10/11/2011 04:49 PM, Tim Bird wrote:
>> On 10/10/2011 11:41 AM, Darren Hart wrote:
>>> As part of working on meta-tiny, I've come across a need (want?) to
>>> present users with the ability to select some set of features in a
>>> local
>>> configuration file that will impact the build of the image and a set of
>>> recipes.
>> Can you tell me more about meta-tiny? this is the first I've heard
>> about this (sorry if discussion went by on the mailing list and I
>> missed it), and I'm very interested.
>>
>> I'm currently doing some size-related work for Sony (including
>> some work to support 4K stacks).
>>
> Perhaps while I have the attention of a few interested parties, it would
> be a good time for a poll. I'm interested in your motivation for smaller
> images.
>
> Are you building SoC's with memory on die and needing to keep the memory
> footprint down to save precious die real-estate?
no
>
> Are you looking at creating mass-market products and saving a few
> pennies on the flash storage translates to real money, so you want to
> minimize the physical size?
no
>
> Are you concerned with boot time, and have connected larger image sizes
> with longer boot times?
I am concerned with boot time, but don't believe it is image size that
ramps it up.
>
> Is there another motivating factor for your interest in small images?
Yes, a smaller system which is easier to check, build and maintain. In
my office I am the leading driver for using linux in a team of 3 (two
software, one fpga developer) so the less time I spend building,
rebuilding and checking features I don't need, to ensure they don't
comprimise the stability of the system, the more faith they have in the
system I'm putting forward.
>
> Thanks,
>
next prev parent reply other threads:[~2011-10-13 8:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 18:41 RFC: User configurable recipe features Darren Hart
2011-10-11 15:53 ` McClintock Matthew-B29882
2011-10-11 16:06 ` Darren Hart
2011-10-11 22:15 ` Richard Purdie
2011-10-11 23:51 ` Khem Raj
2011-10-12 0:18 ` Philip Balister
2011-10-12 15:41 ` Darren Hart
2011-10-12 15:47 ` Koen Kooi
2011-10-12 15:52 ` Paul Eggleton
2011-10-12 16:49 ` Darren Hart
2011-10-12 15:40 ` Darren Hart
2011-10-11 23:49 ` Tim Bird
2011-10-12 15:55 ` Darren Hart
2011-10-12 18:44 ` Khem Raj
2011-10-12 19:30 ` Koen Kooi
2011-10-12 19:32 ` Khem Raj
2011-10-12 20:15 ` Darren Hart
2011-10-12 19:13 ` Tim Bird
2011-10-12 16:59 ` Darren Hart
2011-10-12 17:19 ` Tim Bird
2011-10-12 19:22 ` William Mills
2011-10-13 8:30 ` Jack Mitchell [this message]
2011-10-13 18:33 ` William Mills
2011-10-13 20:50 ` Khem Raj
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=4E96A198.9030109@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=yocto@yoctoproject.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.