As I posed on the ML, I'm not terribly convinced this is Allwinner (the company)'s intentional thing. I'm more imagining an engineer, that wrote the cedarX stuff* and is very protective of his work, telling management that this is his (Allwinner's) IP and they need to protect it. So management may follow. Or he is even working out of his own hand (shared github account). The fact that the functions where obfuscated to 'hide' stuff, is really a bad bad thing and does show intent. Even so, I'm betting on the rogue engineer, rather then Allwinner's intent. This information just has to get to the proper people via the proper channels.
*
If you take the JPEG stuff, what it looks like is they took the stock jpeg library, and at a certain point changed some functions to interface with cedarX. I can very much image, that the the other half of the code, was modified so that it could be embedded into the chip. (C -> FPGA isn't the hardest job I imagine). If there is some way to prove this, they can obfuscate and change all they want, but the GPL infringment is then in the SoC too. Granted, I think you can do with libjpeg whatever you want, if you add the readme (they didn't), but there are gpl-ed functions in there aswell.
*
If you take the JPEG stuff, what it looks like is they took the stock jpeg library, and at a certain point changed some functions to interface with cedarX. I can very much image, that the the other half of the code, was modified so that it could be embedded into the chip. (C -> FPGA isn't the hardest job I imagine). If there is some way to prove this, they can obfuscate and change all they want, but the GPL infringment is then in the SoC too. Granted, I think you can do with libjpeg whatever you want, if you add the readme (they didn't), but there are gpl-ed functions in there aswell.
Comment