Re: [linux-sunxi] Re: GPL Violations round-up.
On Sun, Sep 21, 2014 at 10:02:15PM -0700, AndrewDB 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. FWIW I'm working on mainlining amlogic SoCs and several patches have been already submitted to LKML for Meson6 and Meson8 architectures. I'm in contact with a couple of engineers in Amlogic and they seem willing to help the community. They also promised to provide me with all the documentation I need. We will see. -- Carlo Caione -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: GPL Violations round-up.
On Monday, September 22, 2014 8:24:21 AM UTC+3, Tom Cubie wrote: > > On Mon, Sep 22, 2014 at 1:02 PM, AndrewDB > 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 linux-sunxi...@googlegroups.com . > > 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: GPL Violations round-up.
On Mon, Sep 22, 2014 at 1:02 PM, AndrewDB 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 > > > 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 linux-sunxi+unsubscr...@googlegroups.com. > 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: GPL Violations round-up.
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. 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: GPL Violations round-up.
On Wed, Sep 17, 2014 at 01:50:08AM +0300, Raanan Fattal wrote: > Found it in the famous SDK: > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728_stripped/lichee/linux-3.4/drivers/video/sunxi/hdmi/aw/ Damn. I missed that first time round. Will add it to the wiki in a bit. Thanks! Luc Verhaegen. -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: GPL Violations round-up.
Found it in the famous SDK: http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728_stripped/lichee/linux-3.4/drivers/video/sunxi/hdmi/aw/ On Wed, Sep 17, 2014 at 1:41 AM, Luc Verhaegen wrote: > On Tue, Sep 16, 2014 at 02:45:01PM -0700, RFat wrote: >> Hi Luc, >> >> I am by no means an expert on the GPL topic, but I did found a binary file >> to which some of the source is missing. It is: >> >> linux-3.4/drivers/video/sunxi//hdmi/aw/libhdcp > > Which repo, where? Definitely does look like it is subject to the gpl. > >> Perhaps this helps. > > It definitely does! Thanks! > > Luc Verhaegen. -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: GPL Violations round-up.
On Tue, Sep 16, 2014 at 02:45:01PM -0700, RFat wrote: > Hi Luc, > > I am by no means an expert on the GPL topic, but I did found a binary file > to which some of the source is missing. It is: > > linux-3.4/drivers/video/sunxi//hdmi/aw/libhdcp Which repo, where? Definitely does look like it is subject to the gpl. > Perhaps this helps. It definitely does! Thanks! Luc Verhaegen. -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: GPL Violations round-up.
Hi Luc, I am by no means an expert on the GPL topic, but I did found a binary file to which some of the source is missing. It is: linux-3.4/drivers/video/sunxi//hdmi/aw/libhdcp Perhaps this helps. On Wednesday, August 27, 2014 5:21:35 PM UTC+3, Luc Verhaegen wrote: > > In order to satisfy wikipedia, i have to provide a more reliable source > than our wiki. Plus, i am sure that very few of those who were stating > that GPL violations are not as important as getting an email address, > have actually looked at the wiki. So here is a rather complete list. > > * CedarX: re-uses LGPLed code: > > Amongst others, the cedarX userspace binaries that we have access to, > all have symbols from libavcodec from ffmpeg, which is LGPL. Try an nm > and grep for "ff_" and then google those symbols (there are a few more > though). CedarX is LGPLed, Allwinner has to give it up. > > > https://github.com/linux-sunxi/cedarx-libs/blob/master/libcedarv/android/libvecore/libvecore.a > > > https://github.com/linux-sunxi/cedarx-libs/blob/master/libcedarv/linux-armhf/libvecore/libvecore.so > > > * U-boot: GPL: > > Nand, nand, nand. > > > http://dl.linux-sunxi.org/SDK/A20/A20_SDK_20130319/lichee/u-boot/nand_sunxi/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_hummbingbird_v3.3_v2_kfb_ok/lichee/u-boot/nand_sunxi/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/brandy/u-boot-2011.09/nand_sunxi/sun7iw1/libnand_sun7iw1 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/brandy/u-boot-2011.09/nand_sunxi/sun8iw1/libnand_sun8iw1 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/brandy/u-boot-2011.09/nand_sunxi/sun8iw3/libnand_sun8iw3 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/brandy/u-boot-2011.09/nand_sunxi/sun9iw1/libnand_sun9iw1 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_v4.5_hummingbird_kfb_ok/lichee/brandy/u-boot-2011.09/nand_sunxi/sun7iw1/libnand_sun7iw1 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_v4.5_hummingbird_kfb_ok/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw1/libnand_sun8iw1 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_v4.5_hummingbird_kfb_ok/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw3/libnand_sun8iw3 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_v4.5_hummingbird_kfb_ok/lichee/brandy/u-boot-2011.09/nand_sunxi/sun9iw1/libnand_sun9iw1 > > > http://dl.linux-sunxi.org/SDK/A23-v1.0/unpacked/A23/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw3/libnand-sun8iw3 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun5i/libnand-sun5i > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw7/libnand-sun8iw7 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw8/libnand-sun8iw8 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw6/libnand-sun8iw6 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun7i/libnand-sun7i > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun9iw1/libnand-sun9iw1 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw9/libnand-sun8iw9 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw1/libnand-sun8iw1 > > > * Kernel: GPL: > > * Nand support: > > Loads of slightly different binaries for different SoCs on A20, A31, > A23 and A80 SDK kernels: > > > http://dl.linux-sunxi.org/SDK/A20/A20_SDK_20130319/lichee/linux-3.3/modules/nand/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_hummbingbird_v3.3_v2_kfb_ok/lichee/linux-3.3/modules/nand_v2/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/linux-3.3/modules/nand/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/linux-3.3/modules/nand_v2/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_v4.5_hummingbird_kfb_ok/lichee/linux-3.3/modules/nand_v2/libnand > > > http://dl.linux-sunxi.org/SDK/A23-v1.0/unpacked/A23/lichee/linux-3.4/modules/nand/sun8iw1p1/libnand_sun8iw1p1 > > > http://dl.linux-sunxi.org/SDK/A23-v1.0/unpacked/A23/lichee/linux-3.4/modules/nand/sun8iw3p1/libnand_sun8iw3p1 > > > http://dl.linux-sunxi.org/SDK/A23-v1.0/unpacked/A23/lichee/linux-3.4/modules/nand/sun9iw1p1/libnand_sun9iw1p1 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/linux-3.4/modules/nand/sun8iw5p1/libnand_sun8iw5p1 > >
Re: [linux-sunxi] Re: GPL Violations round-up.
On Fri, 29 Aug 2014 17:26:58 +0100 Simon Kenyon wrote: > the question going through my head is: > are the blobs in question derived from (L)GPL code? > if not, then there is no violation > Did you try to look at our wiki? There was one person that spend considerable amount of time to document all the issues. http://linux-sunxi.org/GPL_Violations Off course i am not a lawyer, but with my limited understanding i can see two types of issues. 1. in kernel tree binary only form blobs that link with the kernel 2. the proprietary video engine libraries are made with some parts that correspond to lgpl source code. This is only what i can see by observation, because i am not involved in finding this dirty details. But if there is still doubt that there are issues, i am sure that someone will help to make those issues more clear. To add. Nobody is saying "give us the source or else". I am sure that this can be resolved pacifically, with the both sides get rewarded at the end. But for that, it is need to exist dialog, and to recognize the issues as issues. -- -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: GPL Violations round-up.
the question going through my head is: are the blobs in question derived from (L)GPL code? if not, then there is no violation -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: GPL Violations round-up.
> > I think the main issue here is how someone can possibly use a chipset where > the software comes with GPL violations in a product and sell this product > worldwide. > > I am not a lawyer, but my understanding is that the copyright holder can > file a law suite against whoever sold the product if source code and friends > are not given out. Usually this leads to dishing out the sources, but if not > the copyright holder can disallow certain companies/people to use the > software. Also (depending on the country the products are being sold) it can > be disallowed to further sell products until the dispute is settled. This > would certainly hurt Allwinner and device vendors. > > Till Jaeger (cc'ed here) is a lawyer and an expert with respect to GPL > violations. He can for sure further enlighten us. I don't know the concrete context. Therefore, I can only provide some general remarks. It is true that the copyright holder of a (L)GPL software can enforce the (L)GPL against any company who is distributing a product without being compliant with the (L)GPL. Enforcing means that the copyright holder may claim that the infringer has to cease and desist from distributing the infringing product as long as the license conditions are not met. Best regards, Till -- Dr. Till Jaeger Certified Copyright and Media Law Attorney JBB Rechtsanwälte Jaschinski Biere Brexl Partnerschaft mbB Christinenstraße 18/19 | 10119 Berlin Tel. +49.30.443 765 0 | Fax +49.30.443 765 22 Sitz der Gesellschaft: Berlin | Registergericht AG Charlottenburg | PR 609 B www.jbb.de -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: GPL Violations round-up.
On Fri, Aug 29, 2014 at 10:29:58AM +0200, Luc Verhaegen wrote: > On Fri, Aug 29, 2014 at 01:00:10AM -0700, Robert Berger wrote: > > HI Luc, > > > > I think the main issue here is how someone can possibly use a chipset where > > the software comes with GPL violations in a product and sell this product > > worldwide. > > > > I am not a lawyer, but my understanding is that the copyright holder can > > file a law suite against whoever sold the product if source code and > > friends are not given out. Usually this leads to dishing out the sources, > > but if not the copyright holder can disallow certain companies/people to > > use the software. Also (depending on the country the products are being > > sold) it can be disallowed to further sell products until the dispute is > > settled. This would certainly hurt Allwinner and device vendors. > > > > Till Jaeger (cc'ed here) is a lawyer and an expert with respect to GPL > > violations. He can for sure further enlighten us. > > > > Regards, > > > > Robert > > Thanks Robert, but i hope it doesn't come to that. I am confident that > Allwinner will voluntarily fulfill its obligations. > > Luc Verhaegen. Especially since they now have this nice list of problems that need solving. Luc Verhaegen. -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: GPL Violations round-up.
On Fri, Aug 29, 2014 at 01:00:10AM -0700, Robert Berger wrote: > HI Luc, > > I think the main issue here is how someone can possibly use a chipset where > the software comes with GPL violations in a product and sell this product > worldwide. > > I am not a lawyer, but my understanding is that the copyright holder can > file a law suite against whoever sold the product if source code and > friends are not given out. Usually this leads to dishing out the sources, > but if not the copyright holder can disallow certain companies/people to > use the software. Also (depending on the country the products are being > sold) it can be disallowed to further sell products until the dispute is > settled. This would certainly hurt Allwinner and device vendors. > > Till Jaeger (cc'ed here) is a lawyer and an expert with respect to GPL > violations. He can for sure further enlighten us. > > Regards, > > Robert Thanks Robert, but i hope it doesn't come to that. I am confident that Allwinner will voluntarily fulfill its obligations. Luc Verhaegen. -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: GPL Violations round-up.
HI Luc, On Wednesday, August 27, 2014 5:21:35 PM UTC+3, Luc Verhaegen wrote: > > In order to satisfy wikipedia, i have to provide a more reliable source > than our wiki. Plus, i am sure that very few of those who were stating > that GPL violations are not as important as getting an email address, > have actually looked at the wiki. So here is a rather complete list. > > * CedarX: re-uses LGPLed code: > > Amongst others, the cedarX userspace binaries that we have access to, > all have symbols from libavcodec from ffmpeg, which is LGPL. Try an nm > and grep for "ff_" and then google those symbols (there are a few more > though). CedarX is LGPLed, Allwinner has to give it up. > > > https://github.com/linux-sunxi/cedarx-libs/blob/master/libcedarv/android/libvecore/libvecore.a > > > https://github.com/linux-sunxi/cedarx-libs/blob/master/libcedarv/linux-armhf/libvecore/libvecore.so > > > * U-boot: GPL: > > Nand, nand, nand. > > > http://dl.linux-sunxi.org/SDK/A20/A20_SDK_20130319/lichee/u-boot/nand_sunxi/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_hummbingbird_v3.3_v2_kfb_ok/lichee/u-boot/nand_sunxi/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/brandy/u-boot-2011.09/nand_sunxi/sun7iw1/libnand_sun7iw1 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/brandy/u-boot-2011.09/nand_sunxi/sun8iw1/libnand_sun8iw1 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/brandy/u-boot-2011.09/nand_sunxi/sun8iw3/libnand_sun8iw3 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/brandy/u-boot-2011.09/nand_sunxi/sun9iw1/libnand_sun9iw1 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_v4.5_hummingbird_kfb_ok/lichee/brandy/u-boot-2011.09/nand_sunxi/sun7iw1/libnand_sun7iw1 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_v4.5_hummingbird_kfb_ok/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw1/libnand_sun8iw1 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_v4.5_hummingbird_kfb_ok/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw3/libnand_sun8iw3 > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_v4.5_hummingbird_kfb_ok/lichee/brandy/u-boot-2011.09/nand_sunxi/sun9iw1/libnand_sun9iw1 > > > http://dl.linux-sunxi.org/SDK/A23-v1.0/unpacked/A23/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw3/libnand-sun8iw3 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun5i/libnand-sun5i > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw7/libnand-sun8iw7 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw8/libnand-sun8iw8 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw6/libnand-sun8iw6 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun7i/libnand-sun7i > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun9iw1/libnand-sun9iw1 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw9/libnand-sun8iw9 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/brandy/u-boot-2011.09/nand_sunxi/sun8iw1/libnand-sun8iw1 > > > * Kernel: GPL: > > * Nand support: > > Loads of slightly different binaries for different SoCs on A20, A31, > A23 and A80 SDK kernels: > > > http://dl.linux-sunxi.org/SDK/A20/A20_SDK_20130319/lichee/linux-3.3/modules/nand/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_hummbingbird_v3.3_v2_kfb_ok/lichee/linux-3.3/modules/nand_v2/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/linux-3.3/modules/nand/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_V4.5_MerriiLinux_Humming/linux-3.3/modules/nand_v2/libnand > > > http://dl.linux-sunxi.org/SDK/A31/unpacked-stripped/a31_v4.5_hummingbird_kfb_ok/lichee/linux-3.3/modules/nand_v2/libnand > > > http://dl.linux-sunxi.org/SDK/A23-v1.0/unpacked/A23/lichee/linux-3.4/modules/nand/sun8iw1p1/libnand_sun8iw1p1 > > > http://dl.linux-sunxi.org/SDK/A23-v1.0/unpacked/A23/lichee/linux-3.4/modules/nand/sun8iw3p1/libnand_sun8iw3p1 > > > http://dl.linux-sunxi.org/SDK/A23-v1.0/unpacked/A23/lichee/linux-3.4/modules/nand/sun9iw1p1/libnand_sun9iw1p1 > > > http://dl.linux-sunxi.org/SDK/A80/A80_SDK_20140728/lichee/linux-3.4/modules/nand/sun8iw5p1/libnand_sun8iw5p1 > > > I don't think that many people here have had to RE one of the > libnands to be able to bring up a nand chip with the existing code. > Also, who here knows that we are killing n
Re: [linux-sunxi] Re: GPL Violations round-up
Speaking something wrong is worse than do nothing. If you are too serious about this problem, Aw will keep their mouth tight. Relax and try to communicate with them. Maybe Aw has made some improvements that we didn't know. Just blame his students is not a good teacher. On Thu, Aug 28, 2014 at 9:35 PM, Stefan Monnier wrote: > > So please stop attacking AW in this way. > > FWIW, I agree with Luc that it's important to bring this up and make > sure that there's some positive movement on that front. > Even if it's limited to splitting the blob into a "Free" glue code > linked to a binary blob. > > And it doesn't have to get all fixed right away before we can do > anything else. But there's a need to establish some understanding > between the two parties about this issue. > > > Stefan > > -- > 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 linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: GPL Violations round-up
> So please stop attacking AW in this way. FWIW, I agree with Luc that it's important to bring this up and make sure that there's some positive movement on that front. Even if it's limited to splitting the blob into a "Free" glue code linked to a binary blob. And it doesn't have to get all fixed right away before we can do anything else. But there's a need to establish some understanding between the two parties about this issue. Stefan -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
