For our environment we needed a working Ethernet driver for the u-boot. We wanted to use the official u-boot from the cva6-sdk but realized that it lacks this driver-type. Therefore, we searched for a solution. The yocto for cva-6 has a working u-boot Ethernet driver. It is a specific commit of another branch of the same u-boot Repository the cva6-sdk takes its u-boot from. Therefore, to fix the problem, we took the changes made inside the Ethernet driver commit by @eyssartk [not the whole branch] and added it to the u-boot of the official cva6-sdk. It works. With this fix the u-boot of the cva6-sdk also has a working Ethernet driver. We created an issue for this because in previous versions of the cva6-sdk it had a working Ethernet driver. Further, we would recommend to apply these changes to the u-boot version, which is connected to the cva6-sdk.
Finally, we would take this chance to highlight, that the source of this issue lies in the complexity of repository inter-connections and, that we would highly recommend to compress them to the smallest amount needed. For example, just having one u-boot and one OpenSBI for CVA-6 would be helpful. This compressing-approach would also solve some naming issues such as the cva6 branch of the u-boot repository, which does not work with the official cva6-sdk directly.
Hello everyone,
For our environment we needed a working Ethernet driver for the u-boot. We wanted to use the official u-boot from the cva6-sdk but realized that it lacks this driver-type. Therefore, we searched for a solution. The yocto for cva-6 has a working u-boot Ethernet driver. It is a specific commit of another branch of the same u-boot Repository the cva6-sdk takes its u-boot from. Therefore, to fix the problem, we took the changes made inside the Ethernet driver commit by @eyssartk [not the whole branch] and added it to the u-boot of the official cva6-sdk. It works. With this fix the u-boot of the cva6-sdk also has a working Ethernet driver. We created an issue for this because in previous versions of the cva6-sdk it had a working Ethernet driver. Further, we would recommend to apply these changes to the u-boot version, which is connected to the cva6-sdk.
The described fix would also solve the issue mentioned by us in the u-boot repository.
Finally, we would take this chance to highlight, that the source of this issue lies in the complexity of repository inter-connections and, that we would highly recommend to compress them to the smallest amount needed. For example, just having one u-boot and one OpenSBI for CVA-6 would be helpful. This compressing-approach would also solve some naming issues such as the cva6 branch of the u-boot repository, which does not work with the official cva6-sdk directly.
Kind Regards,
Jan Reinhard SYSGO