To me it does not make any sense to merge them. One would use the OSS flow and
thus only meta-xilinx, or the Xilinx SDK toolflow which is meta-petalinux and
meta-xilinx-tools (I think). I don't see the added value in merging them, it
will only add to the confusion, and pollute one's environment by dragging in
"meta" layers that aren't actually active.
On 13-11-17 21:13, Manjukumar Harthikote Matha wrote:
Hi All,
We want to restructure meta-xilinx layer to encompass all the layers coming
from Xilinx.
The proposal is the following for Rocko/master:
meta-xilinx
->meta-xilinx-bsps (current meta-xilinx)
->meta-xilinx-contrib
In the next release we will add some more layers such as meta-petalinux,
meta-xilinx-tools, etc. It will look like
meta-xilinx
->meta-xilinx-bsps (current meta-xilinx)
->meta-petalinux
->meta-xilinx-tools
->meta-xilinx-contrib
There will be some movement of recipes from meta-xilinx-bsps to
meta-xilinx-contrib. Patches will be sent to mailing list on any recipes
movement.
This will provide one clone to get all the required meta layers from Xilinx for
a complete solution, and the users can blacklist any layer which they don't
want to use.
This will enables us to help our vendors/partners to add their reference
designs, board definitions etc.
Please let us know your feedback. We plan to get this done no later than 11/20.
Thanks,
Manju
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
--
_______________________________________________
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
