Re: regression tests for am3517-evm machine?

[Denys Dmytriyenko <denys@ti.com>]

On Wed, Jan 27, 2016 at 10:52:55PM -0600, Troy Benjegerdes wrote:
> On Wed, Jan 27, 2016 at 05:55:29PM -0500, Denys Dmytriyenko wrote:
> > On Wed, Jan 27, 2016 at 04:12:03PM -0600, Troy Benjegerdes wrote:
> > > > > So the first problem seems to be that the 'u-boot' target produces
> > > > > a build from the 2014.07 version, which does not seem to have any
> > > > > environment or other setup to load a device tree.
> > > > > 
> > > > > Is there some patch floating around somewhere that updates the
> > > > > default u-boot environment to work better with new kernels, or do
> > > > > I need try and merge something in from the beaglebone
> > > > 
> > > > Can you try u-boot-ti-staging instead?
> > > 
> > > This is from 'pokey' ( yocto-2.0-121-g2fb7ee2 ),
> > > with meta-ti: ( v2012.05-yocto1.2-938-gd397744 )
> > 
> > Strange mix of branches - 2012 was almost 4 years ago... :)
> > 
> > I'd recommend using "fido" branch in all layers, as most tested at the moment. 
> > Still no guarantees about am3517, as that platform hasn't been officially 
> > tested for quite some time.
> 
> Ah, I was on master for meta-ti.
> 
> FYI, I needed the following hack to build on yocto-2.0:

It was fixed in master long ago:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/recipes-graphics/drm/libdrm.inc?id=2d2633227f541395276316a4b45bafa41be94003


> ~/src/poky/meta-ti/recipes-graphics/drm
>  % git diff
> diff --git a/recipes-graphics/drm/libdrm_2.4.41.bb b/recipes-graphics/drm/libdrm_2.4.41.bb
> index 86a660e..6e08b98 100644
> --- a/recipes-graphics/drm/libdrm_2.4.41.bb
> +++ b/recipes-graphics/drm/libdrm_2.4.41.bb
> @@ -1,8 +1,9 @@
> -require recipes-graphics/drm/libdrm.inc
> +#require recipes-graphics/drm/libdrm.inc
>  
>  FILESEXTRAPATHS_append := ":${COREBASE}/meta/recipes-graphics/drm/libdrm"
>  
>  COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15"
> +LICENSE = 'GPL'
> 
> 
> 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.