On Monday, September 22, 2014 8:24:21 AM UTC+3, Tom Cubie wrote: > > On Mon, Sep 22, 2014 at 1:02 PM, AndrewDB <[email protected] > <javascript:>> wrote: > > For what it's worth, I fully support Luc's actions to document > Allwinner's > > GPL violations. > > > > I also believe it is in Allwinner's interest to fully comply with the > GPL > > and that it's a pity that they don't understand this. How many > (extremely > > expensive) engineer-hours has this community generously contributed to > > firmware/software development on Allwinner SOCs? I am positive that > > Allwinner's present market share is in good part the result of this > > community's work (although this assertion is impossible to prove), so > why > > not help this community by not having to reverse-engineer so many > things? > > > > And finally, last but not least, I firmly believe that it is in the > interest > > of this community to have Allwinner fully comply with the GPL and freely > > provide as much documentation as possible. So we should all stand behind > Luc > > and not be indifferent or worse, critical of his actions. > > > > Let me explain briefly where I am coming from: > > - First developer to have Linux booting on a dual-core Cortex-A9 > AML8726MX > > tablet. Tried in vain to get any response from Amlogic about > cooperation > > with the Linux development community. Dropped development on this > platform > > because of total lack of support from Amlogic. Apparently in the last > few > > months they have been trying to reverse this situation, but I would say > it's > > too little, too late. > > - First developer to have Linux booting on a dual-core RK3066 stick. > Tried > > in vain to get any response from Rockchip and from RK3066 stick > > manufacturers about cooperation with the Linux development community. > Again, > > dropped development on this platform and all subsequent Rockchip SOCs > > because of total lack of support from Rockchip (one of the Android stick > > manufacturers explained to me that he was himself being charged by > Rockchip > > for kernel customization services and did not have access to the kernel > > source). And if I may add, to this day the various kernels that they > have > > discreetly leaked are so unstable that I personally consider Rockchip > SOCs > > to be among the worst possible platforms for Linux and Android. > > The situation has changed for rockchip. Rockchip is now actively doing > the mainline work. They have sent development boards to some kernel > maintainers too[1]. Their latest soc rk3288 goes to mainline three > months ago[2]. Patches are sent to kernel ML everyday from Rockchip > engineers. > > [1] https://plus.google.com/111049168280159033135/posts/eZncP6ym3nZ > [2] http://www.spinics.net/lists/arm-kernel/msg338779.html > > Indeed I saw that Rockchip changed their attitude towards mainline and the community in a big way. Rockchip is now working on having mainline support and I even saw Chrome OS devs contributing to Rockchip mainline code. It seems Google had a big role in convincing companies such as Rockchip and Mediatek to change their ways. Given all of this it would be wise for Allwinner to accelerate their efforts of collaborating with the community. I've seen some shy attempts at this but more could certainly be done about this.
> > > > > > On Wednesday, August 27, 2014 4:21:35 PM UTC+2, Luc Verhaegen wrote: > >> > >> In order to satisfy wikipedia, i have to provide a more reliable source > >> than our wiki. > >> > >> ... > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "linux-sunxi" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > radxa rock - quad core arm computer that rocks > > radxa.com > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
