[SUGGESTION] Add mvebu 6.8 patches, move to rmk tree #6229
Conversation
github-actions
bot
added
size/large
|
Pro: less maintaining, perhaps more features and fixes Cons: development branch that goes with the mainline code when developers finds time. Can be days, but also weeks - months behind upstream. Making release out of this might not be best using this code. I am fine with both ways. EDGE is here to experiment. If it proves to be worse, we still can go back. |
|
sorry just noticed this PR :) will try to test soon |
|
@lanefu you got few days for merging into 24.5 |
|
any luck here? |
sorry I like missed all these notifications some how.. lemme actually take a look now. |
|
Hmmm Had compile error on |
|
is |
|
removed vsc73xx and ran into a different tangle... I'll have to try harder and look more closely |
|
I can have a look at it this afternoon. |
Heisath
changed the title
|
I looked at it and moved the kernel to 6.8 for mvebu edge. Compilation of kernel works I think. Sadly the build framework fails at the end and I have no idea whats wrong. Never got into the new build output format... https://paste.armbian.com/etahupogin I think this is the same problem @lanefu ran into. |
Description
Hi. mvebu has been moved to csc some time ago. Now every once in a while a patch breaks and we have to remove it / fix it.
Russel King keeps a pretty up to date kernel tree for clearfog over at http://git.armlinux.org.uk/cgit/linux-arm.git/log/?h=clearfog
So I tried to move our mvebu-edge to be based on his work. This allows us to include lots of mvebu patches without the need to maintain them.
I would like to discuss the advantages and disadvantages with you!
Also this is some movement to finally get the helios4 pwm patch mainlined over at the linux-pwm/gpio/kernel mailing list.
Jira reference number AR-2015
How Has This Been Tested?
Ran kernel build.