From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: Fri, 16 Mar 2018 19:55:41 +0200
Subject: [U-Boot] [PATCH v2] x86: zImage: pass device tree setup data to
 the kernel
In-Reply-To: <1521222757.23017.34.camel@linux.intel.com>
References: <20180316173836.GA1813@intel.com>
 <1521222757.23017.34.camel@linux.intel.com>
Message-ID: <1521222941.23017.35.camel@linux.intel.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Fri, 2018-03-16 at 19:52 +0200, Andy Shevchenko wrote:
> On Fri, 2018-03-16 at 10:38 -0700, Ivan Gorinov wrote:
> > On x86 platforms, U-Boot does not provide Device Tree data to the
> > kernel.
> > This prevents the kernel from using the same hardware description.
> > 
> > Make a copy of DTB data with setup_data header and insert new item
> > into the the setup data linked list.
> 
> So, now is the question, what to do with x86 hardware that has DTS in
> U-
> Boot, but uses ACPI tables, generated by U-Boot.
> 
> Would it work properly?
> 
> I would try to test it on Intel Edison (I hope you may do this
> yourself
> as well), though I don't know when, have not much time to work with
> Edison right now.

Perhaps for now you may use CONFIG_ACPI_GENERATE (or how it's called?).

> >  #include <common.h>
> > +#include <malloc.h>

> > +#include <asm/global_data.h>
> >  #include <asm/acpi_table.h>

Not in order.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy