[meta-xilinx] Xilinx, why are you breaking the meta-xilinx-bsp layer?

[Martin Lund]

Hi Manju,


Thank you for your answers.

>> It would be nice if Xilinx would maintain a wiki documenting the schedule for
>> Xilinx YP branches. Xilinx wiki is good stuff!
>>
>
>Will try to document the process on wiki

A simple overview detailing past and future Xilinx YP branch releases would be helpful to remove some of the confusion or lack of information regarding the Xilinx YP branch releases.


>> We are perhaps a front runner here but the very reason we tried to bring up the
>> rel-v2018.1 with YP rocko is that we wanted to use the new v2018.1 components
>> to benefit from the various bug fixes and improvements. In particular we wanted
>> to try out the much never kernel (4.9 vs 4.14) because we see some instability
>> issues with the Xilinx qspi-nor driver when running some UBI stress tests. First we
>> tried back porting most of the qspi-nor changes from 4.14 to 4.9 but that didn't fix
>> the instability. There are some deeper infrastructure changes in the qspi-nor driver
>> (e.g. change from mmio to ioctl API calls) that we coulnd't easily backport so that
>> put us on the path of trying to upgrade everything to the new rel-v2081.1 to get
>> to the new kernel.
>>
>
>Can we start a new thread on this issue please?
>We would like to understand the failure and try to provide a fix
>Not sure if this helps:
>https://github.com/Xilinx/linux-xlnx/commit/1859edf811e7960ddc73a08b2e8bac93be463a87

Yes, I'll start a new thread detailing the issue we see when we run the UBI stress tests from mtd-utils.

Br, Martin


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20180525/20ca390e/attachment-0001.html>