On Tuesday 31 March 2015 10:16:52 Chris Hallinan wrote:
On Tue, Mar 31, 2015 at 9:17 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
On Monday 30 March 2015 19:17:46 Chris Hallinan wrote:
Great catching up with you last week, and thanks for looking at my
patch. I supposed it's a
On Tue, Mar 31, 2015 at 9:17 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
Hi Chris,
Great to see you at ELC!
On Monday 30 March 2015 19:17:46 Chris Hallinan wrote:
Great catching up with you last week, and thanks for looking at my
patch. I supposed it's a double edged sword. If
Hi Chris,
Great to see you at ELC!
On Monday 30 March 2015 19:17:46 Chris Hallinan wrote:
Great catching up with you last week, and thanks for looking at my
patch. I supposed it's a double edged sword. If we make it a
variable, it can be set wrong and the build hang again. OTOH, 128MB
is
Hi Armin,
Great catching up with you last week, and thanks for looking at my
patch. I supposed it's a double edged sword. If we make it a
variable, it can be set wrong and the build hang again. OTOH, 128MB
is probably way more space than we really need to reserve, and I
supposed if someone
See https://bugzilla.yoctoproject.org/show_bug.cgi?id=7541
Current implementation of live image type cannot support image size
greater than 4GB. If the image gets too large, the build simply
hangs silently, without any clues or debug output to indicate why.
This patch prevents the build hanging
Chris,
Should the hardcoded value '416080' be a variable so it can be
overridden?
- armin
On 03/30/2015 01:50 PM, Chris Hallinan wrote:
See https://bugzilla.yoctoproject.org/show_bug.cgi?id=7541
Current implementation of live image type cannot support image size
greater than 4GB. If
