[meta-xilinx] Introduction and feedback on meta-xilinx

[Manjukumar Harthikote Matha]

On 11/24/2015 03:36 PM, Peter Crosthwaite wrote:
> On Tue, Nov 24, 2015 at 3:12 PM, Manjukumar Harthikote Matha
> <manjukumar.harthikote-matha at xilinx.com> wrote:
>> Hi all,
>>
>> My name is Manju, I have recently joined Xilinx Inc and will be working on
>> meta-xilinx layer to provide continuous support and integration. Nathan has
>> been helping out to a lot to maintain this layer, I will be working along
>> with him to provide the support for this layer.
>>
>> Our near term goals for meta-xilinx are
>>
>> 1. OSL releases based on meta-xilinx
>>
>
> I don't understand how this would work, and it feels like an inversion
> of the upstream-downstream relationship. Shouldn't meta-xilinx pull
> from OSL sources as appropriate and use an appropriate release, in
> much that same way it does with the major mainline sources? OSL is the
> upstream for those components and has it's own release schedule which
> should not need to depend on a downstream. Is that schedule still
> based on Xilinx tool releases?
>

Hi Peter,

Our plan was to use all the tagged releases from linux-xlnx, u-boot-xlnx 
and Xilinx toolchain to build the OSL images.

For example we would use v2015.3 tag from all the sources(linux-xlnx, 
u-boot-xlnx) and use v2015.3 Xilinx toolchain to build OSL images. Once 
the images are built and tested, we will tag meta-xilinx as well.

Anything incorrect with this approach?

Yes OSL release schedule will be based on Xilinx tool releases.

Thanks
Manju

> Regards,
> Peter
>
>> 2. Updates for toolchain, kernel versions, Yocto versions etc.
>>
>> 3. Support for UltraScale+ MPSoC platforms (Machine definitions for ZC1751,
>> ZCU102 etc)
>>