Closed AsuraZeng closed 1 year ago
Already asked this in firmware context, but it equally applied to the driver changes: Why not moving to latest 08.05.00.004 release? Already the icssg-prueth driver has several changes there, some of them fixes.
Hi jan
As described above, TI has published the SDK 08.02.00.002 officially, so I catch up on this version. 08.05.00.004 is on the git repo. this is not officially published
While continuing the review, my first suggestion for the kernel patch queue would to preserve our original ordering, add the new cherry-picked patches on top. Would allow some bisecting (with some extra setup effort) over the update.
Another suggestion (should be a separate commit) is to use git format-patch --no-signature
from now on so that this source of change is consistently avoided. I think you tweaked your format-patch to keep the signature identical, right?
You dropped these patches from the queue:
recipes-kernel/linux/files/patches-5.10/0062-remoteproc-pru-Configure-firmware-based-on-client-se.patch
recipes-kernel/linux/files/patches-5.10/0069-remoteproc-pru-add-support-for-configuring-GPMUX-bas.patch
This causes a delta of drivers/remoteproc/pru_rproc.c
even with your old BSP release baseline.
While continuing the review, my first suggestion for the kernel patch queue would to preserve our original ordering, add the new cherry-picked patches on top. Would allow some bisecting (with some extra setup effort) over the update.
Another suggestion (should be a separate commit) is to use
git format-patch --no-signature
from now on so that this source of change is consistently avoided. I think you tweaked your format-patch to keep the signature identical, right?
I have refactored the patches based on your suggestion.
Please check out https://github.com/siemens/meta-iot2050/commits/jan/kernel-update - there was more to-do than I originally thought.
Closing as #411 was merged.
this helps the issue #368 referred. after several times reboots, the ethernet port can not work.