linux-3.4-sunxi

Sure, but Allwinner did release their BSP under GPLv2, which the community summarily ported to mainline for the chunks they hadn't rewritten already. Broadcom has yet to do anything like that. https://github.com/allwinner-zh/linux-3.4-sunxi

Some person from linux-sunxi made it his life mission to crucify Allwinner because they (Allwinner) messed up with some Linux kernel tarballs. What you have been reading is the result of this campaign against Allwinner. 1. Allwinner used to distribute Linux kernel tarballs with several device drivers in binary-only (object) files. They were in the correct place and you could recompile the kernel. Those binary .o files would be used so that you could complete the compilation. Such an example is the Mali driver and others that Allwinner did not make an effort to get the rights to redistribute in source. Obviously, this is a GPL violation. So, how do you deal with this issue? Do you get Allwinner to release the source of the Mali GPU driver due to the GPL violation? :-). Some people wanted to play lawyers and would mess up ANY action unless

It is created with 0666 as the mode. https://github.com/allwinner-zh/linux-3.4-sunxi/blob/A83T/ar...

I like how the repository's history was discretely rewritten since then. Commit 7cc9a8fff679fcd31bca7d18c8b3b960796d032f was replaced by bcc3e09783ca31039183d5084d8480bd76d531f5, without the sunxi-debug.c file. Compare https://github.com/allwinner-zh/linux-3.4-sunxi/commit/7cc9a... (original) with https://github.com/allwinner-zh/linux-3.4-sunxi/commit/bcc3e... (modified) https://github.com/allwinner-zh/linux-3.4-sunxi/blob/7cc9a8f... https://github.com/allwinner-zh/linux-3.4-sunxi/blob/bcc3e09... → 404

And everything hidden in this undocumented monster-commit: https://github.com/allwinner-zh/linux-3.4-sunxi/commit/7cc9a... He should have added: 3. add a backdoor;