[meta-xilinx] ZC702 support in Xilinx meta-xilinx

[Elvis Dowson]

Hi Robert,

On Apr 23, 2013, at 3:11 PM, "Robert P. J. Day" <rpjday at crashcourse.ca> wrote:

> On Tue, 23 Apr 2013, Elvis Dowson wrote:
> 
>> Additionally while on this topic, any thoughts on how one would
>> maintain different configurations for a board, using different
>> kernel sources, e.g Xilinx and Analog Devices, and manage this in an
>> easy way in a custom board layer and switch between them?
> 
>  not sure if this is the question you're asking but you can have
> board-specific settings the way the meta-yocto-bsp layer does. that
> layer defines four machines, and the kernel bbappend files look like:
> 
> KBRANCH_atom-pc  = "standard/common-pc/atom-pc"
> KBRANCH_routerstationpro = "standard/routerstationpro"
> KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
> KBRANCH_beagleboard = "standard/beagleboard"
> 
> COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
> COMPATIBLE_MACHINE_routerstationpro = "routerstationpro"
> COMPATIBLE_MACHINE_beagleboard = "beagleboard"
> COMPATIBLE_MACHINE_atom-pc = "atom-pc"
> 
> ... etc etc ...  but i suspect this isn't what you were asking about.

Right, this is what I do now. In my mind, a meta-board layer should
be sufficiently different to be put into a separate layer, else a standard
machine conf, with a of machine specific configurations for the kernel
and bootloader, in the manner you describe might be sufficient, along
with machine specific patches located in a specific folder in the kernel
or bootloader recipe.

I see value in creating a meta-soc-family layer, and then appending 
board specific patches or configurations, from a separate board layer
as required, e.g. if you create a design using the xilinx ip blocks
or create your own ip blocks, along with a bunch of linux drivers, then
you could append those drivers as patches to the standard linux kernel
from your custom meta-board layer, on top of a generic meta-zynq-7 or 
meta-microblaze layer.

Elvis Dowson