cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Contributor
Contributor
92 Views
Registered: ‎05-30-2018

Petalnux: Difference in behavior with Remote-Linux (2020.1 vs previous release)

In previous Petalinux releases, I was able to specify a custom linux repository by doing  this in the project-spec/configs/config file

CONFIG_SUBSYSTEM_COMPONENT_LINUX__KERNEL_NAME_REMOTE_DOWNLOAD_PATH="git://github.com/<my repo>.git"
CONFIG_SUBSYSTEM_COMPONENT_LINUX__KERNEL_NAME_REMOTE_REFERENCE="<md5 hash>"

 

It seems that this is no longer acceptable in Petalinux 2020.1. I get an error claiming the repository cannot be found and it will try to checkout a default branch name "linux-xlnx-5.4" in this case.

I instead must provide a branch and a md5 hash like so:

CONFIG_SUBSYSTEM_COMPONENT_LINUX__KERNEL_NAME_REMOTE_DOWNLOAD_PATH="git://github.com/<my repo>.git"
CONFIG_SUBSYSTEM_COMPONENT_LINUX__KERNEL_NAME_REMOTE_REFERENCE="<md5 hash>"

CONFIG_SUBSYSTEM_COMPONENT_LINUX__KERNEL_NAME_REMOTE_BRANCH="<branch that contains the above git hash in history>"

 

The branch must now be included despite specifying the exact md5 hash in Petalinux 2020.1. Previous versions did not have this behavior so this seems like a bug. Will this be fixed in future versions?

 

0 Kudos
0 Replies