Hi @joshgoldsmith,
We can talk about in the future if you need help to create (and maintain
) a meta-pynq layer.
Feel free to ask anything if something is not clear, maybe wrong, I will be happy to reply.
Why doesn’t an official meta-pynq layer exist?
For FPGA folks (at lest in my company) , PYNQ is an absolute game-changer. It’s the life-saver that lets us test complex hardware and accelerators directly from Python, without having to write and maintain complex bare-metal C/C++ applications just to send some data.
Now that AMD/Xilinx is pushing everyone from the (soon-to-be-deprecated) PetaLinux BSPs to a pure Yocto workflow, a meta-pynq layer seems like the most logical, most-needed piece of the puzzle. It would be the definitive bridge to make Yocto the default, easy-to-use platform for the entire PYNQ community.
Is there a technical reason one doesn’t exist? Is it on a secret roadmap somewhere?
Or is this a gap the community needs to fill? We’d love to hear your thoughts!
Thanks for everything you do with PYNQ.