From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] x86: zImage: pass device tree setup data to the kernel
Date: Mon, 19 Mar 2018 11:19:27 +0200 [thread overview]
Message-ID: <1521451167.23017.48.camel@linux.intel.com> (raw)
In-Reply-To: <1521245773.1851.18.camel@intel.com>
On Fri, 2018-03-16 at 17:16 -0700, Ivan Gorinov wrote:
> On Fri, 2018-03-16 at 19:52 +0200, Andy Shevchenko 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?
>
> It will work because CONFIG_OF is disabled in most x86 kernel
> configurations.
No one prevents to put CONFIG_OF=y into kernel configuration.
> > 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.
>
> I am going to try that on a Minnowboard.
Yes, please.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-03-19 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 17:38 [U-Boot] [PATCH v2] x86: zImage: pass device tree setup data to the kernel Ivan Gorinov
2018-03-16 17:52 ` Andy Shevchenko
2018-03-16 17:55 ` Andy Shevchenko
2018-03-17 0:16 ` Ivan Gorinov
2018-03-19 9:19 ` Andy Shevchenko [this message]
2018-03-16 19:40 ` Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1521451167.23017.48.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.