From: Denys Dmytriyenko <denys@ti.com>
To: Troy Benjegerdes <hozer@hozed.org>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: regression tests for am3517-evm machine?
Date: Thu, 28 Jan 2016 19:09:08 -0500 [thread overview]
Message-ID: <20160129000907.GK11314@edge> (raw)
In-Reply-To: <20160128163317.GA24907@nl.grid.coop>
On Thu, Jan 28, 2016 at 10:33:17AM -0600, Troy Benjegerdes wrote:
> > > After a little more digging around, I find that having:
> > > #define CONFIG_OF_LIBFDT
> > > is required for u-boot to be able to recognize and load a device
> > > tree, but it does not seem to be set in the am3517 build(s).
> > >
> > > If I build a u-boot from source with CONFIG_OF_LIBFDT, I get the
> > > expected output, but now if boot a mainline 3.16 or 3.18 kernel
> > > (which mostly work with no device tree), these kernels fail to
> > > boot with a device tree.
>
> What is the state of linux-ti-staging and how does it compare to
> linux-omap.. it seems like there is some sort of brokenness in
> moving the am3517 (omap3) support from the legacy code to device
> trees.
linux-ti-staging recipe pulls from ti-linux-kernel on git.ti.com, which is
the latest kernel development and upstreaming effort for all the current TI
processors. Maintaining legacy parts like am3517 and omap3 in general is a
best effort.
If by linux-omap you mean the actual kernel tree from Tony Lindgren, then it
is one of the targets for patches staged in ti-linux-kernel to be upstreamed
to, among others.
--
Denys
prev parent reply other threads:[~2016-01-29 0:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 6:36 regression tests for am3517-evm machine? Troy Benjegerdes
2016-01-18 16:46 ` Denys Dmytriyenko
2016-01-18 20:05 ` Troy Benjegerdes
2016-01-19 18:48 ` Troy Benjegerdes
2016-01-19 19:08 ` Denys Dmytriyenko
2016-01-21 1:58 ` Troy Benjegerdes
2016-01-21 20:48 ` Denys Dmytriyenko
2016-01-21 22:03 ` Robert Nelson
2016-01-21 22:07 ` Denys Dmytriyenko
2016-01-27 21:56 ` Troy Benjegerdes
2016-01-27 22:03 ` Denys Dmytriyenko
2016-01-27 22:12 ` Troy Benjegerdes
2016-01-27 22:55 ` Denys Dmytriyenko
2016-01-28 4:52 ` Troy Benjegerdes
2016-01-28 16:13 ` Denys Dmytriyenko
2016-01-28 16:33 ` Troy Benjegerdes
2016-01-29 0:09 ` Denys Dmytriyenko [this message]
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=20160129000907.GK11314@edge \
--to=denys@ti.com \
--cc=hozer@hozed.org \
--cc=meta-ti@yoctoproject.org \
/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.