On 14/01/2014 7:28 AM, Jason Cooper wrote:
> Ahhh, ok. Thanks for the clarification. You kept that line in the
> version you submitted to Russell's patch tracker?
Negative. I'll supersede the patch with one including that line.
--
Ben Peddell
IT Support Bowen, Collinsville and Proserpine Cath
Ben,
On Tue, Jan 14, 2014 at 07:08:30AM +1000, Ben Peddell wrote:
> Patch submitted with requested changes.
>
> On Mon, 13 Jan 2014 at 10:28:51 AM -0500, Jason Cooper wrote:
> >> + initrd_start = initrd_end = 0;
> >
> > This line shouldn't be necessary. Both are reset in the following hunk
> >
Patch submitted with requested changes.
On Mon, 13 Jan 2014 at 10:28:51 AM -0500, Jason Cooper wrote:
>> +initrd_start = initrd_end = 0;
>
> This line shouldn't be necessary. Both are reset in the following hunk
> below your change:
>
if (phys_initrd_size &&
!memblock_is_region_memory(
Ben,
Thanks for the patch. A few comments below.
On Sat, Jan 11, 2014 at 10:03:58AM +1000, klightsp...@killerwolves.net wrote:
> Commit 65939301acdb (arm: set initrd_start/initrd_end for fdt scan)
Thanks for including this. We have a new tag we are using now to
incorporate this information to
Commit 65939301acdb (arm: set initrd_start/initrd_end for fdt scan)
caused the FDT initrd_start and initrd_end to override the
phys_initrd_start and phys_initrd_size set by the initrd= kernel
parameter. With this patch initrd_start and initrd_end will be
overridden if phys_initrd_start and phys_in
