On 20-02-19 15:22, Luca Ceresoli wrote: > Hi Jean-Francois, > > On 20/02/19 15:01, Jean-Francois Dagenais wrote: >> >> >>> On Feb 20, 2019, at 06:01, Mike Looijmans <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> +1 for that! >>> >>> (and not just on meta-xilinx, but on kernel, u-boot, and other >>> repositories as >>> well) >>> >>> These "big blob" changes are impossible to manage. >> >> Indeed. Here's a concrete example: >> >> I had to integrate the audio on our board. Our design called for the >> xilinx_dma driver to come into play. When I started using the cyclic >> mode with the audio I found it was (and still is I believe) completely >> broken/non-functional. I spent a week and a half working on >> xilinx_dma.c. I meticulously fixed the different issues I saw, cleaned >> up a whole bunch of stuff and carefully created a nice series of commits >> so that it could be discussed and applied. >> >> I was carrying this in our repo awaiting a closely upcoming release. To >> my dismay, xilinx_dma.c had a complete overhaul appear in github's >> linux-xlnx upon the release and to add insult to injury, the commits >> which were finally deposited on the repo pre-dated my work! > > Oh dear. I also have fixes for cyclic DMA on the 2017.x (4.9) series. > Now I guess I will be unable to apply them on the 2018.x (4.14) series, > just as you have. :-(
We too. Which then results in avoiding the Xilinx DMA IP completely... -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
