Re: [PATCH] drivers/of: add option to load a default Device Tree

[Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

Hi Franck,

(This could be confusing, with Franck and Frank -- feel free to
address me as rowand in this thread if it is less confusing.)

On 06/22/16 08:05, Franck Jullien wrote:
> Even if a platform doesn't use a device tree during its
> boot process it can be useful to enable CONFIG_OF and get
> an empty device tree.
> 
> Then, devices can use device tree overlays to populate this
> default tree.
> 
> Signed-off-by: Franck Jullien <franck.jullien-EduPiq9onwdphFt5fpzH3laPQRlvutdw@public.gmane.org>
> ---
>  drivers/of/Kconfig     |  9 +++++++++
>  drivers/of/Makefile    |  3 +++
>  drivers/of/base.c      | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  drivers/of/default.dts |  4 ++++
>  drivers/of/unittest.c  | 33 +++++----------------------------
>  include/linux/of.h     |  2 ++
>  6 files changed, 73 insertions(+), 28 deletions(-)
>  create mode 100644 drivers/of/default.dts

< snip >

For context, in a later reply, you mention that this is for x86_64.

My current inclination is to prefer not to solve the problem this way.
I was going to ask why you didn't just add the compiled default.dts
to the kernel as an appended device tree blob, until I found out
this was for x86_64.

Can you add unflatten_devicetree() to x86_64, then just use the
appended device tree blob method?

-Frank
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html