04-07-2021, 02:27 PM
(04-04-2021, 09:37 PM)t4_4t Wrote: As far as I know, '0.9.16: gitlab-ci-linux-build-163' is the last version of 'u-boot' with the correct implementation of 'efuse' support.
The so-called 'main-line' ' u-boot', does not have the 'efuse' support function correctly implemented.
(* It may be more accurate to say that the'efuse'support feature itself has been removed.)
Try the following image,
https://github.com/ayufan-rock64/linux-b...m64.img.xz
If this still gives the same result, your claim (In fact the efuse is empty) is correct.
On the other hand, if you get a reasonable value, it's just a 'u-boot' problem.
This might be true. I do not have the time today to test, but will do it to make sure it is not my card that is messed up.
However this also shows the heart of the problem here:
How many forks of uboot and the kernel should a project like armbian need to package? Really one for every manufacturer with incompatible patches? And knowing the gotchas when users "uses the wrong version"?
If neither Rockchip nor pine64 can make the card properly working in mainline versions of critical parts of the plumbing like uboot and the kernel then why should armbian - a community project - push resources into trying to support this uniq flavor of hardware it?
So I can understand why they still package it, but also why they do not want take time trying to figure out users problems with it.
I also do not understand why the ' around mainline. Mainline is mainline. everything else is a fork until it becomes its own viable project with its own name that succeeds in becoming a contender or even surpassing the original. See for example MySQL and MariaDB, OpenOffice and LibreOffice. Or for that matter the Linux and Android kernel.
The vendors forks of uboot are code drops and not viable projects in its self, and their patches should really be up-streamed into mainline projects if they want community projects like Armbian to actually be able to fully support it, and not having to try to figure out if the user have a software bug, another gotcha with using "the wrong fork" or an actual hardware problem.