This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/AM5728: Release notes

Hi, all.

Now I am using process sdk 03.02.05 for am572x.

The newest sdk is 04.01.00 and the issue tracker of release note  lists a lot of bug fixed.

But how to get the patch corresponding to the record id of bug issue?

and there is simple way to update from 03.02.05 to 04.01.00?

Because of project requirement, many file of  file system, u-boot, kernel of  03.02.05 are modified.

Thanks.

  • The software team have been notified. They will respond here.
  • There's quite a huge difference between PSDKL 3.02 and 4.01: different compiler, u-boot, kernel version, yocto branch, etc. You need to rebase your code on top of the new SDK, i.e. you need to know what things you changed in the existing version and then reapply in the new version. Some of that work can be managed through Yocto build system if for example you created your own distribution and associated meta-layer. You could track your specific changes in that branch.

    Note that PSDKL 4.02 is expected by the end of the year, so you may want to wait until that's released before you begin any major efforts. Or at a minimum, keep careful logs of what you're changing so that when PSDKL 4.03 is eventually released you can rebase on top of that one (i.e. that will likely be the final and most stable of the 4.9 kernel releases so that would be a good version to utilize for a shipping product).
  • For other things of PSDK except u-boot and kernel, It means if I found a bug fixed in PSDK release note which I interest and want to patch to my exist system,the only way is to rebase on top of new PSDK. Right ?

    And for u-boot and kernel, I can get patch of git to update from old version to new version, but git log seems no corresponding to record id of bug issue in PSDK release note, it also must rebase on top of new PSDK?
  • Is there only one specific bug you're trying to fix?  If so, which one?  That might be reasonable to do a small update (depending on the bug!).  If there are a bunch of bug fixes and new features, then it quickly becomes easier to rebase your code on the new SDK, rather than trying to pull code backwards.