[meta-xilinx] should elvis' meta-xilinx layer be synced with poky right now?

Elvis Dowson elvis.dowson at gmail.com
Wed Apr 17 17:27:37 PDT 2013


On Apr 17, 2013, at 8:29 PM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:

>  and while i'm here, a question about the u-boot recipe in that same
> layer.  there are two u-boot recipes:
> 
> u-boot-xilinx_2012.10.bb
> u-boot-xilinx_git.bb
> 
> neither of them being .bbappend files, but both contain the FILESPATH
> setting:
> 
> FILESPATH = "${@base_set_filespath([ '${FILE_DIRNAME}/${PN}/${SOC_FAMILY}' ], d)}"
> 
> i'm not sure what's going on there, what is that supposed to
> accomplish since there are no file subdirectories for either of those
> recipes. thanks.

This was placed there, incase there are any SOC_FAMILY specific (e.g. zynq-7)
patches that need to be applied to the u-boot recipes.

Since Xilinx have consolidated most of the support for zynq-7 (ARM) and micro blaze
in their git repositories, no patches were necessary, which is why there are no
subdirectories at the moment.

You'll find a similar FILESPATH definition for the linux kernel recipes as well.

The idea was to make the SOC definitions modular, so that you can specify all
the System-On-Chip components in one place, and then pull all those definitions
in and then proceed with defining additional machine specific features based
on your expansion board (screen, pci, keyboard, serial, etc).

I've done this for the zynq-7 and virtex-5 (which contains a PowerPC 440 processor),

Elvis Dowson


More information about the meta-xilinx mailing list