[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqL7Of9_NofFd2ym47PNPtYWSMmshe+sJSGTwKmOa5C50Q@mail.gmail.com>
Date: Tue, 15 Apr 2014 20:02:29 -0500
From: Rob Herring <robherring2@...il.com>
To: Andreas Herrmann <herrmann.der.user@...glemail.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Grant Likely <grant.likely@...aro.org>,
Ralf Baechle <ralf@...ux-mips.org>, linux-mips@...ux-mips.org,
David Daney <ddaney.cavm@...il.com>
Subject: Re: [PATCH 01/20] mips: octeon: convert to use unflatten_and_copy_device_tree
On Mon, Apr 7, 2014 at 12:46 PM, Andreas Herrmann
<herrmann.der.user@...glemail.com> wrote:
> On Thu, Apr 03, 2014 at 05:16:44PM -0500, Rob Herring wrote:
>> From: Rob Herring <robh@...nel.org>
>>
>> The octeon FDT code can be simplified by using
>> unflatten_and_copy_device_tree function. This removes all accesses to
>> FDT header data by the arch code.
>
> Hi Rob,
>
> I think (in general) this modification is ok. But I suggest to use
> following (slightly modified) version.
Having to compile each platform on MIPS sure is annoying. Reminds me
of ARM a few years ago. We need a good rant from Linus about MIPS. ;)
>
> - /* Copy the default tree from init memory. */
> - initial_boot_params = early_init_dt_alloc_memory_arch(dt_size, 8);
> - if (initial_boot_params == NULL)
> - panic("Could not allocate initial_boot_params");
> - memcpy(initial_boot_params, fdt, dt_size);
> + initial_boot_params = (void *)fdt;
Does calling early_init_devtree here work instead. This will add
parsing memory, initrd and command line. If you don't have those then
it should be a nop other than setting initial_boot_params. It should
only matter if your DT has these things and you want/need to ignore
them. Do this would get things more inline with other arches.
Rob
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists