On Sun, Aug 1, 2010 at 5:36 AM, Edgar E. Iglesias
edgar.igles...@gmail.com wrote:
On Sat, Jul 31, 2010 at 12:56:42AM +0200, Edgar E. Iglesias wrote:
On Thu, Jul 29, 2010 at 06:48:24PM -0700, Hollis Blanchard wrote:
The kernel's BSS size is lost by mkimage, which only considers file
size. As
On Mon, Aug 2, 2010 at 11:57 AM, Edgar E. Iglesias
edgar.igles...@gmail.com wrote:
On Mon, Aug 02, 2010 at 10:59:11AM -0700, Hollis Blanchard wrote:
On Sun, Aug 1, 2010 at 5:36 AM, Edgar E. Iglesias
edgar.igles...@gmail.com wrote:
On Sat, Jul 31, 2010 at 12:56:42AM +0200, Edgar E. Iglesias
On Mon, Aug 02, 2010 at 12:33:54PM -0700, Hollis Blanchard wrote:
On Mon, Aug 2, 2010 at 11:57 AM, Edgar E. Iglesias
edgar.igles...@gmail.com wrote:
On Mon, Aug 02, 2010 at 10:59:11AM -0700, Hollis Blanchard wrote:
On Sun, Aug 1, 2010 at 5:36 AM, Edgar E. Iglesias
edgar.igles...@gmail.com
On Mon, Aug 2, 2010 at 12:56 PM, Edgar E. Iglesias
edgar.igles...@gmail.com wrote:
On Mon, Aug 02, 2010 at 12:33:54PM -0700, Hollis Blanchard wrote:
You mean the one architecture, which by the way doesn't even use this
API? That doesn't seem like a strong argument to me. Anyways, it's
Are we
On Sat, Jul 31, 2010 at 12:56:42AM +0200, Edgar E. Iglesias wrote:
On Thu, Jul 29, 2010 at 06:48:24PM -0700, Hollis Blanchard wrote:
The kernel's BSS size is lost by mkimage, which only considers file
size. As a result, loading other blobs (e.g. device tree, initrd)
immediately after the
On Thu, 29 Jul 2010, Hollis Blanchard wrote:
The kernel's BSS size is lost by mkimage, which only considers file
size. As a result, loading other blobs (e.g. device tree, initrd)
immediately after the kernel location can result in them being zeroed by
the kernel's BSS initialization code.
On Thu, Jul 29, 2010 at 06:48:24PM -0700, Hollis Blanchard wrote:
The kernel's BSS size is lost by mkimage, which only considers file
size. As a result, loading other blobs (e.g. device tree, initrd)
immediately after the kernel location can result in them being zeroed by
the kernel's BSS
