Re: [linux-sunxi] Allwinner GPL violations: definitive proof.
Hello, On 5 March 2015 at 18:35, Henrik Nordström hen...@henriknordstrom.net wrote: ons 2015-03-04 klockan 17:41 + skrev Manuel Braga: What we get? Just indifference that the reverse engineering effort even exists. Sorry you get this impression. I know I have been silent, but that's mostly because video is not something I am interested in, and especially not Allwinners binary take on it. But it does not mean that I am indifferent to your effort, not at all, to me the documentation of the CedarX hardware and proof of concept software was and is very important, even if far from feature complete. It WorksForMe(tm). I can play video with mplayer which is how I use video most of the time even on systems with multiple choices of a media player. And with opensource drivers which I can expect to continue working as long as sunxi hardware has any use. Thanks for that. Yes, it is a gross hack. But for more progress the other parts to which the VE engine is to be hooked have to be ready - like the KMS driver. Technically one can be writing a VE driver without a KMS driver which is then just plugged in ... and you can see all the bugs then. On 4 March 2015 at 14:10, Luc Verhaegen l...@skynet.be wrote: On Wed, Mar 04, 2015 at 02:31:41PM +0200, Simos Xenitellis wrote: On Wed, Mar 4, 2015 at 1:57 PM, Luc Verhaegen l...@skynet.be wrote: On Wed, Feb 25, 2015 at 04:55:15AM +0100, Luc Verhaegen wrote: ... So now there is a LICENSE file stating that the code in https://github.com/allwinner-zh/media-codec is LGPL? So Allwinner believes that by sticking the LGPL on a _binary_ solves all the problems? Just like it seems to believe that removing all binaries from a kernel tree solves all problems with the GPL? Really? This is simply ridiculous. This guy is so toxic. Apparently it's an attitude style to be permanently negative. You give him caviar and he complains that it's black. Or a VIN ROMANEE CONTI 1955 and he complains that it's too old. I do not know whether there will be more commits to that repo. Just in case there are, a typical person would refrain from making such comments. Simos Simos, I am corrosive and bitter, but perhaps i am not the toxic one here. Corrosive and bitter is enough to drive off new users which can potentially become new contributors. Maybe you don't need new community members and are fine with writing a KMS driver in a year or two that nobody but you ever uses. But linux-sunxi needs new members to continue as a community and you have been repeatedly seen driving people off. While your arguments might be technically correct you fail to deliver them politely, or even acceptably in many cases. All we ever see you do is trash me. You have written no code, you have not contributed to the wiki, you only now spend some time on irc to try to clean up your image. You started calling for banishing me, while trying to instigate a fork, almost as soon as you got here. And you try to post about every little positive thing that allwinner does (while allwinner ignores its hard legal responsibilities), to try to take credit for them and to try artificially gain any form of standing here. Perhaps you and Allwinner do not realize this. But linux-sunxi does not need Allwinner, Allwinner needs linux-sunxi. What linux-sunxi requires Yeah, sure. It's true that allwinner has used the work done by sunxi community in the past for their business. And it has provided some code and documentetion. And it has not provided some other code and other documentation which the sunxi community needs to continue the same work. But there is no hard requirement for allwinner to cooperate with linux-sunxi. They can hire a developer to do the work, they can just live with their Chinese SDKs or they can go out of business, whatever. from Allwinner is a legal matter, and a pretty open and shut case at that. Allwinner trying to make their mole a part of this community this crudely or artificially, while so badly messing up the basics, that is not only counterproductive, it is quite preposterous. Stop trying to hollow out Allwinners hard legal requirements. Sure, allwinner is required, legally, to release some sources. And it might have signed some NDAs to not release them so it may as much legally be obliged to not release the same sources. It might in fact have put itself into a situation when it is not allowed to ship a product with this software, legally. However, the copyright of the ffmpeg authors or Linux authors is somewhat theoretical in China while the NDA they signed with the business next door is much less. And as has been pointed out the situation can be 'corrected' by releasing modularized sources with the blobs as properly separated modules without providing anything useful to linux-sunxi at all. So dwelling on this point is in all ways quite useless. Even though they have shipped the SDKs with intermixed binaries and are technically
[linux-sunxi] Re: [PATCH v2 1/4] i2c: sunxi: Add Reduced Serial Bus (RSB) support
On Thu, Mar 05, 2015 at 07:40:44PM +0100, Wolfram Sang wrote: I don't have the bandwidth for a full review right now. However, I already wanted to tell you guys that my gut feeling is that this protocol is quite far away from I2C. P2WI was already at the edge. Maybe there is a better place for such custom stuff? I dunno yet. That's unfortunate, especially since it looks closer to SPI than what P2WI even was. SPI? I assume you mean I2C. Can you elaborate your reasoning? Yeah, I obviously meant I2C, sorry. P2WI had no address. It was a single-device bus. However, the way it communicated with the device was very close to I2C, apart from a parity bit instead of the ACK. From that regard, RSB is a multiple device bus, using addresses, just like I2C. The way it communicates is basically the one used by P2WI. So really, it just is more I2C-alike than P2WI has ever been. What would be your suggestion? Let me quote: I don't have the bandwidth for a full review right now... I dunno yet. Good thing that we are not talking about a full review then, but more a philosophical discussion. Thanks! Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.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. signature.asc Description: Digital signature
[linux-sunxi] Re: [PATCH 2/2] dt-bindings: Add vendor-prefix for Wexler
On Thu, Mar 05, 2015 at 12:17:21AM +0300, Aleksei Mamlin wrote: This patch adds vendor-prefix for Wexler. WEXLER trademark owned by AVIRSA Electronics, a member of the diversified holding AVIRSA. Signed-off-by: Aleksei Mamlin mamli...@gmail.com --- Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt index 389ca13..eb67da4 100644 --- a/Documentation/devicetree/bindings/vendor-prefixes.txt +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt @@ -189,6 +189,7 @@ variscite Variscite Ltd. via VIA Technologies, Inc. virtio Virtual I/O Device Specification, developed by the OASIS consortium voipac Voipac Technologies s.r.o. +wexler AVIRSA Electronics Seriously, either call it wexler or Avirsa, but at least make up your mind. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.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. signature.asc Description: Digital signature
[linux-sunxi] Re: [PATCH 1/2] ARM: dts: sun7i: Add dts file for Wexler TAB7200
On Thu, Mar 05, 2015 at 12:16:48AM +0300, Aleksei Mamlin wrote: This patch add support for Wexler TAB7200 tablet. The Wexler TAB7200 is a A20 based tablet with 7 inch display(800x480), capacitive touchscreen(5 fingers), 1G RAM, 4G NAND, micro SD card slot, mini HDMI port, 3.5mm audio plug, 1 USB OTG port and 1 USB 2.0 port. Signed-off-by: Aleksei Mamlin mamli...@gmail.com --- arch/arm/boot/dts/Makefile | 3 +- arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts | 181 + 2 files changed, 183 insertions(+), 1 deletion(-) create mode 100644 arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile index beac15f..f6dc2ac 100644 --- a/arch/arm/boot/dts/Makefile +++ b/arch/arm/boot/dts/Makefile @@ -550,7 +550,8 @@ dtb-$(CONFIG_MACH_SUN7I) += \ sun7i-a20-olinuxino-lime2.dtb \ sun7i-a20-olinuxino-micro.dtb \ sun7i-a20-pcduino3.dtb \ - sun7i-a20-pcduino3-nano.dtb + sun7i-a20-pcduino3-nano.dtb \ + sun7i-a20-wexler-tab7200.dtb dtb-$(CONFIG_MACH_SUN8I) += \ sun8i-a23-ippo-q8h-v5.dtb \ sun8i-a23-ippo-q8h-v1.2.dtb diff --git a/arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts b/arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts new file mode 100644 index 000..b197d57 --- /dev/null +++ b/arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts @@ -0,0 +1,181 @@ +/* + * Copyright 2015 Aleksei Mamlin + * Aleksei Mamlin mamli...@gmail.com + * + * This file is dual-licensed: you can use it either under the terms + * of the GPL or the X11 license, at your option. Note that this dual + * licensing only applies to this file, and not this project as a + * whole. + * + * a) This file is free software; you can redistribute it and/or + * modify it under the terms of the GNU General Public License as + * published by the Free Software Foundation; either version 2 of the + * License, or (at your option) any later version. + * + * This file is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public + * License along with this file; if not, write to the Free + * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, + * MA 02110-1301 USA + * + * Or, alternatively, + * + * b) Permission is hereby granted, free of charge, to any person + * obtaining a copy of this software and associated documentation + * files (the Software), to deal in the Software without + * restriction, including without limitation the rights to use, + * copy, modify, merge, publish, distribute, sublicense, and/or + * sell copies of the Software, and to permit persons to whom the + * Software is furnished to do so, subject to the following + * conditions: + * + * The above copyright notice and this permission notice shall be + * included in all copies or substantial portions of the Software. + * + * THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, + * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES + * OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT + * HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, + * WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING + * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR + * OTHER DEALINGS IN THE SOFTWARE. + */ + +/dts-v1/; +#include sun7i-a20.dtsi +#include sunxi-common-regulators.dtsi + +#include dt-bindings/gpio/gpio.h +#include dt-bindings/input/input.h +#include dt-bindings/interrupt-controller/irq.h +#include dt-bindings/pinctrl/sun4i-a10.h You don't seem to be using the pinctrl header. Also, next time, please mention the version and provide a changelog for your patches. Thanks! Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.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. signature.asc Description: Digital signature
[linux-sunxi] Re: [PATCH v2 1/4] i2c: sunxi: Add Reduced Serial Bus (RSB) support
From that regard, RSB is a multiple device bus, using addresses, just like I2C. The way it communicates is basically the one used by P2WI. I am not keen to allow everything which is a bus and has addresses into the I2C realm. The addresses are 12 bit, whilst I2C has at maximum 10 bit which is rarely used, so mostly 7 bit are used. It has a runtime readdressing mechanism which is not present in standard I2C. And if you look at the protocol with no acks but parities, IMO it doesn't look closer to I2C than to other two wire protocols. So, being in I2C needs more arguments. And while the outcome could be that it really makes sense to add RSB to I2C with I2C_FUNCS_RSB added, it could also be that there is a more suitable place for custom busses in the kernel. Also, the fact that P2WI is in I2C is not an argument IMO. It could have been a mistake to pick it up. So really, it just is more I2C-alike than P2WI has ever been. Because it has addresses? I disagree. Good thing that we are not talking about a full review then, but more a philosophical discussion. Exactly. This is why I wanted to bring this in early. -- 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. signature.asc Description: Digital signature
Re: [linux-sunxi] Allwinner GPL violations: definitive proof.
On Friday, March 6, 2015 at 5:42:22 AM UTC+10, Michal Suchanek wrote: Sure, allwinner is required, legally, to release some sources. And it might have signed some NDAs to not release them so it may as much legally be obliged to not release the same sources. It might in fact have put itself into a situation when it is not allowed to ship a product with this software, legally. However, the copyright of the ffmpeg authors or Linux authors is somewhat theoretical in China while the NDA they signed with the business next door is much less. Michal this logic is wrong. Customs I was referring is China own customs. http://www.chinabusinessreview.com/tackling-intellectual-property-infringement-in-china/ You will find customs as one of the methods to enforce against intellectual property infringement this includes copyright infringement. 1/2 a million routers were crushed by China customs when a company refused to release firmware source code as required and their website blocked by the great china firewall. The GUY next door with the NDA over Allwinner is not going to help Allwinner when the products are crushed and Allwinner web site is blocked from the outside world by the great china firewall. FOSS enforcement only seams theoretical in China because FOSS does not do it often. Also normally when FOSS enforcement does happen to Chinese companies they mostly go out of business. The router vendor tired that Chinese smiley face method as well. Allwinner need to make up its mind either it only sells inside china or it want to sell to the world. If it wants to sell to the world software infringement is not on. Also remember github is USA so anything infringing hosted on github can be removed by DCMA orders. Due to this infringement being found the source code need to be mirror to a country where copyright cannot be enforced until its fixed. In fact to remain legally clear it should be removed from github by them until its fixed. This is the multi country legal problem. And as has been pointed out the situation can be 'corrected' by releasing modularized sources with the blobs as properly separated modules without providing anything useful to linux-sunxi at all. Other than the fact it legally should not be on github in it current state and can be removed at any time due to the fault by a DCMA order. So the benefit it gives linux-sunxi is legal right to use more hosting. Please note China customs the person who can place complain is a FOSS developer or one of their competitors. This is why this is so serous the FOSS developer may do nothing against Allwinner but one of Allwinner competitors take this information to put them out of business. Peter Dolding -- 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] Allwinner GPL violations: definitive proof.
ons 2015-03-04 klockan 17:41 + skrev Manuel Braga: What we get? Just indifference that the reverse engineering effort even exists. Sorry you get this impression. I know I have been silent, but that's mostly because video is not something I am interested in, and especially not Allwinners binary take on it. But it does not mean that I am indifferent to your effort, not at all, to me the documentation of the CedarX hardware and proof of concept software was and is very important, even if far from feature complete. In the end, the users expect all from us, but is not enough. Yes, all software magically works, and can be implemented without any documentation or even half-working binaries to reverse... You know, if we(the reverse engineering people) had a bit more support, we would be motivated to work a bit harder, so that maybe today we all would be much happier. And this page would have progressed much more. http://linux-sunxi.org/VE_Planning I don't know what to say other than community needs a critical mass of interested people to motivate itself in each area, and stamina to ignore users who thinks everything just should work. If there is just one man driving then motivation undoubtedly fails after a while. Unfortunately the ratio users vs developers is not the best in this world, especially not when talking lowlevel hardware releated matters. Regards Henrik -- 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: Allwinner GPL violations: definitive proof.
Many of you say video is not important its so wrong ... Video is the most important ... commercial wise For your knowledge only chinese Tronsmart brand sold more than 100k devices based on A80 sun9i platform under Draco brand boxes ... i don't want to mention all other brands that sold same platform boxes ... some of the end user buyers want to stick to android but many of them would like to go Ubuntu , Debian OSMC , Openelec linux Kodi etc etc... with desktop with vpu gpu hardware acceleration. Nobody can argue against the consumers just because they are the one who bring the profit to companies as Allwinner. Why not fixing the video vpu gpu issues of Allwinner SoC's first ? I am supporting Luc at least from this point of view. -- 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] Derailed thread
*sigh* I have been reading this mailing list for a while and every time somebody starts an argument with luc it´s like watching a plane crash. - You know exactly what is going to happen, actually you don´t like to watch it, but you are too captivated to look the other way and in the end it is going to be messy and people might get lost - Everybody claims to know how to build a community, but cannot stand that the other has a different way of doing things. Can we all be friends again, behave like adults and go back to work? :-) -- 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] Formal request for source code for LGPL licensed software.
Dear Allwinner and allwinner employees, Thank you for releasing your media-codec/CedarX as LGPL v2.1 or later at https://github.com/allwinner-zh/media-codec/ Section 4 of the LGPL v2.1 (https://www.gnu.org/licenses/lgpl-2.1.html) states: You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code. While i have not seen the complete source code inside this repository, and while i also have not seen an explicit offer which provides access to the complete source code, i assume that this is implied and that such a matter will be resolved with the reception of this request. Please, kindly provide the complete, corresponding machine-readable source code to your LGPLed software to either a public place (like that github account), or to me personally (so i can place it on the linux-sunxi github account), in accordance with the license that you have chosen for your software. Thank you, 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: [PATCH v2 1/4] i2c: sunxi: Add Reduced Serial Bus (RSB) support
Hi Wolfram, On Wed, Mar 04, 2015 at 06:27:11PM +0100, Wolfram Sang wrote: On Mon, Mar 02, 2015 at 04:24:43PM +0800, Chen-Yu Tsai wrote: The RSB controller looks like an SMBus controller which only supports byte and word data transfers. It can also do double-word data transfers, but the I2C subsystem does not support this, nor have we seen devices using this. The RSB differs from standard SMBus protocol on several aspects: - it uses addresses set at runtime to address slaves. Runtime addresses are sent to slaves using their 12bit hardware addresses. Up to 15 runtime addresses are available. - it adds a parity bit every 8bits of data and address for read and write accesses; this replaces the ack bit - only one read access is required to read a byte (instead of a write followed by a read access in standard SMBus protocol) - there's no Ack bit after each read access This means this bus cannot be used to interface with standard SMBus devices (known devices supporting this interface are the AXP223, AXP806, AXP809 PMICs and the AC100 codec/RTC). However the RSB protocol is an extension of P2WI, which was close enough to SMBus to be integrated into the I2C subsystem in commit 3e833490fae5 (i2c: sunxi: add P2WI (Push/Pull 2 Wire Interface) controller support). Signed-off-by: Chen-Yu Tsai w...@csie.org I don't have the bandwidth for a full review right now. However, I already wanted to tell you guys that my gut feeling is that this protocol is quite far away from I2C. P2WI was already at the edge. Maybe there is a better place for such custom stuff? I dunno yet. That's unfortunate, especially since it looks closer to SPI than what P2WI even was. What would be your suggestion? Thanks, Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.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. signature.asc Description: Digital signature
[linux-sunxi] Re: [PATCH v2 1/4] i2c: sunxi: Add Reduced Serial Bus (RSB) support
I don't have the bandwidth for a full review right now. However, I already wanted to tell you guys that my gut feeling is that this protocol is quite far away from I2C. P2WI was already at the edge. Maybe there is a better place for such custom stuff? I dunno yet. That's unfortunate, especially since it looks closer to SPI than what P2WI even was. SPI? I assume you mean I2C. Can you elaborate your reasoning? What would be your suggestion? Let me quote: I don't have the bandwidth for a full review right now... I dunno yet. -- 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. signature.asc Description: Digital signature
Re: [linux-sunxi] Derailed thread
Dear Simos, I noticed in your recent blog post that you are starting linux-exynos.org. - Simos Xenitellis. Since you are starting linux-exynos.org, you need to learn this new thing. - Simos Xenitellis. I am one of the two people who has worked on setting up linux-exynos.org for the past year as a response to Luc's talk at FOSDEM 2014. At that talk Luc explained that what sets Allwinner SoCs apart from other SoCs is its community, which other SoCs, such as the Samsung Exynos, clearly lacked at that time. For example, the instructions for installing Linux on the Chromebooks were all scattered around the world-wide web on the Chromium website, several blog posts, several forum threads, etc. What also happened at that talk is that my friend Merlijn Wizzup Wajer asked for some pointers on setting up a community for it, which Luc explained thoroughly. Let me get these facts straight for you, as it seems that you are implying that Luc is shifting towards linux-exynos: - Luc does have an account on our wiki, but hasn't contributed anything. I am not necessarily expecting him to do that either, because it is likely that he already has his hands full with the linux-sunxi community. [1] - Luc is present on both #linux-exynos and #linux-sunxi. - Luc has never replied to any of the mails on the linux-exynos mailing lists, as none of them are relevant to him, I'd presume. Then we have Luc's blog post [2], of which the last section, and only the last section, explains that, as a graphics driver developer, he has to work with various SoCs, which other than sharing the same GPU, are very different. For linux-sunxi one of the frustrating parts is the display driver, and for linux-exynos one of the frustrating parts is the broken KMS driver. Again Luc clearly indicates that linux-sunxi was the only active community at that time, and that that was what other SoCs clearly lacked. He also states that even though he has been working a lot on the linux-sunxi community, he does not want to do this for other communities as he does not have the time for that. Rightfully so, I'd say. Then this last section continues with the story I started this e-mail with, and the rest is simply a call to help us, if you can and want to, of course. Concerning the linux-sunxi wiki, if you want to get somewhere, then first of all stop throwing a bunch of argumenta ad hominem into an e-mail to a public mailing list. It simply won't get you anywhere. Rather than editing the wiki as you see fit, it is usually better to address the issues of the wiki, propose some changes and talk about your proposal with active members of the community, such as Luc. I am quite sure that if you do this properly, that you can reach a point of consensus in that regard. Community building is not about blaming one single person within a community, it is a matter of working as a community, talking to each other, and trying to get somewhere. Finally, if you don't like how someone is reacting to you, then remember that it is hard to read someone's feelings from an e-mail, and that you can always change your own approach to get a different reaction. In the worst case you have to let it rest for a while, instead of adding more fuel to the blazing fire. That way you also get yourself some time to think about it. Yours faithfully, S.J.R. van Schaik. 1. http://linux-exynos.org/wiki/Special:Contributions/Libv 2. http://libv.livejournal.com/27388.html -- 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] Derailed thread
On Thu, Mar 5, 2015 at 3:30 AM, Luc Verhaegen l...@skynet.be wrote: On Thu, Mar 05, 2015 at 02:13:48AM +0200, Simos Xenitellis wrote: On Wed, Mar 4, 2015 at 3:10 PM, Luc Verhaegen l...@skynet.be wrote: On Wed, Mar 04, 2015 at 02:31:41PM +0200, Simos Xenitellis wrote: Simos, I am corrosive and bitter, but perhaps i am not the toxic one here. Luc, Hi. You are not a bad person. We first met at XDS2008, so I have somewhat first-hand experience. We even had lunch/dinner at the pub and you behaved as a normal human being to the waiter; I do not think there was trimmed pubic hair in the haggis we all ate. I have no recollection of this, or what you mean by the above. There were some movie references in there but nevermind. You really try to make good things and help the projects that you are active in. However, in this thing called community building, it's not your cup of tea. While you believe that it is your cup of tea, par excellence, right? I say that community building is something you are bad at it, and you return it back. Since you are starting linux-exynos.org, you need to learn this new thing. You try to insult new contributors into doing NewDevice pages on the Wiki but you end up sending them away. The worst part is that others in the list can see the mess and will not touch the wiki either. Also, edit-war with new contributors? At one point there was the accidental GPL compliance. Today it is the mainline effort, the new device howto (and related howtos) and the number of documented devices that puts sunxi seriously apart from other soc projects. The NewDeviceHowto needs to be simplified. As it, it makes sense to *you*, but it is too complicated for the new user. The skill you are missing is that of reading a document in the eyes of another person. Feel free to show _all_ the instances that an edit war has happened, i will be happy to explain the backgrounds of them (if you can even find multiple), and how useful those people have been or would have been. You mention the svn guys toxic talk below, i will refer to that extensively in my reply. You are happy to explain the background. Wearing the hat of the community builder, you DO NOT antagonize new prospective contributors. And especially, since it's not the area of your expertise, you delegate to some other member of the community that is happy to assist. You need these in any community you are making. The solution here is to get others to help out and you do *not* get involved. You might want to watch https://www.youtube.com/watch?v=Q52kFL8zVoM which discusses the subtleties of community building. I was wondering when you were going to bring that one up. Watch it again, and take particular notice of how it talks about documentation and actual contributions. We might need to watch together, because the message is about poisonous people and how they damage communities. All we ever see you do is trash me. You have written no code, you have not contributed to the wiki, you only now spend some time on irc to try to clean up your image. That's an attempt to divert the discussion to me in person. I am not the story. Should I remind you that this started out as me pointing out Allwinners role in the blatant LGPL violation that is cedarx, and I wasn't the one to go for a personal attack? If there is violation, it's simple to comply by the LGPL and we will be none the wiser. Big companies pay lots of money so they comply to the letter. Like in the TVs and other consumer products as in http://opensource.samsung.com/ The Linux kernel by itself is useless. The only importance of those code dumps is to find out which libraries do not have a usable BSD alternative. Unlike what you claim above, I actually contributed. If you really want to go through this avenue: if I prove you wrong, you back off entirely from all this. In comparison to the noise you are making, and how you like to portray yourself, you have contributed surprisingly little. So, from having no contribution, I have little contribution. You started calling for banishing me, while trying to instigate a fork, almost as soon as you got here. And you try to post about every little positive thing that allwinner does (while allwinner ignores its hard legal responsibilities), to try to take credit for them and to try artificially gain any form of standing here. Personally I cannot think of a way to gain something here. Gain reputation among you all? I respect all of you, but no. Really? Really. In your case, you have things to lose from this community. You have invested in this project. You have invested so much that you would be even a suitable recruit for Allwinner. Even having access to internal documents and source in order to produce a proper libvdpau. But sadly, you come off as a loose cannon. It's scary. It does not appear that you have a flexible strategy. In fact it's so
Re: [linux-sunxi] Derailed thread
Hi, On Thu, 5 Mar 2015 02:13:48 +0200 Simos Xenitellis simos.li...@googlemail.com wrote: In your case, you have things to lose from this community. You have invested in this project. You have invested so much that you would be even a suitable recruit for Allwinner. Even having access to internal documents and source in order to produce a proper libvdpau. Maybe i am wrong, but this form of speaking makes me beleave that you are associating Luc to the video engine work. And this is incorrect, he has nothing to do with it. If you or someone else is not happy with the work done, then it is *me* the one to go complain. Also the proper thing needed is a proper mainlined kernel driver for this video engine, but appears that i am almost exclusive the only one speaking this need. See, this is the page http://linux-sunxi.org/VE_Planning, but in this conditions (well i thought that linux-sunxi was a community), there is no desire to spend the time nor motivation to continue. And to make clear is not because fault of documentation, we have already all that is need more that 1 and half year. But what i see is only talking about binaries, and that is not my business. -- Manuel Braga -- 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] Derailed thread
On Thu, 2015-03-05 at 12:12 +0200, Simos Xenitellis wrote: On Thu, Mar 5, 2015 at 3:30 AM, Luc Verhaegen l...@skynet.be wrote: On Thu, Mar 05, 2015 at 02:13:48AM +0200, Simos Xenitellis wrote: On Wed, Mar 4, 2015 at 3:10 PM, Luc Verhaegen l...@skynet.be wrote: On Wed, Mar 04, 2015 at 02:31:41PM +0200, Simos Xenitellis wrote: Simos, Simos, please stop it. And you failed to respond to Luc's points. PS. Mediatek developers are contributing to mainline kernel. Päikest, Priit Laes -- 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:Re: [linux-sunxi] how to build an linux image for A31S
Hi Siarhei Siamashka, Thank you very much for your help, I think i have to compile the u-boot bootloader and the kernel by myself. but it seems that https://github.com/linux-sunxi/linux-sunxi dosen't have branch for A31S. Thanks, stone At 2015-03-06 12:21:37, Siarhei Siamashka siarhei.siamas...@gmail.com wrote: Hi, On Fri, 6 Mar 2015 11:48:50 +0800 (CST) li lijiamin...@163.com wrote: Hi all, I want to use debian or linaro on A31s, but i don't know how to get one, First of all, you can check if your device already has a page at the linux-sunxi wiki: http://linux-sunxi.org/Category:Devices If yes, then you can find further instructions there and more details about the mainline u-boot and the mainline kernel support for it. The core A31s SoC features are already supported, but different devices may have different configurations for the peripherals. If there is no device page for your device, then you are encouraged to create one. There is a basic instruction and a checklist for the things to do: http://linux-sunxi.org/New_Device_howto For installing Debian on a few supported Allwinner devices, you can check https://wiki.debian.org/InstallingDebianOn/Allwinner But if the device is not fully supported yet, then the whole process of installation in some way resembles the http://en.wikipedia.org/wiki/Ready-to-assemble_furniture Which means that you may need to be ready to compile the u-boot bootloader and the kernel yourself and then unpack the rootfs with the distribution of your choice (the necessary instructions are available in the linux-sunxi wiki). and it seems that the forum only support A10, A20, and A80, Some A31(s) devices are already supported. But A80 is not quite at that level yet. I am realy appreciated if you can provide any suggestion, thank you. Hope this helped. -- Best regards, Siarhei Siamashka -- 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] Backporting simplefb support to 3.16 kernel
Hi Ian, Hans, On 28/02/15 16:18, Ian Campbell wrote: On Sat, 2015-02-21 at 11:49 +0100, Hans de Goede wrote: On 21-02-15 11:26, Ian Campbell wrote: Speaking of which, if someone were to identify a suitable set of simple-fb backports for 3.16 and they are reasonably self contained I'd happily backport them to the kenrel which is going to be in the next Debian release too... You will need all patches by me and by Luc Verhaegen from here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/video/fbdev/simplefb.c As well as these dts patches: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=5790d4ee1e425fefef0e012d1415c25baeb9dae8 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=d501841fc42a97a8b69449135eadf6e9c4589a87 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e53a8b2201384ee1a2cfd1609c9ffdf951b041a1 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=8efc5c2be5b29f7ceec83bb471da81690273e141 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=678e75d I inserted this one here so the following stuff would cherry-pick ok, I think that was the right thing to do. I'm sure it was; it was in that place when the series was committed: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=rangeq=a9f8cda3 Similarly, looking at: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=rangeq=8284731e I think we should also have: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6d09dc6b74caaca83e32e67f2454406041d58fb0 in its original place in the series, which I see Ben Hutchings has recently taken care of: https://anonscm.debian.org/viewvc/kernel?view=revisionrevision=22439 and we should also include: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ba168a3c7ff6df2e346959445190484b8331eb3d Hans, do you agree? Ian, do you need me to raise a Debian bug about this last missing patch? Thanks, B.R. -- 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] Allwinner GPL violations: definitive proof.
On Wed, 4 Mar 2015 19:56:53 -0800 (PST) oia...@gmail.com wrote: I think we need to bring this back to simple. Thanks for sharing your opinion. But first of all, please start playing by the rules yourself. This is a technical mailing used by free software developers. And the subscribers are expected to respect Proper conduct, as explained in the linux-sunxi wiki: http://linux-sunxi.org/Mailing_list Which means making sure that you don't violate: http://linux.sgms-centre.com/misc/netiquette.php And in particular, the Make sure your lines are no longer than 72 to 76 characters in length rule. 1) as FOSS not out to harm allwinnertech all FOSS want is conformance with license. Reality here the two worst laws to break as a hardware vendor is copyright and trademark. Serous-ally. Both you can enforce by customs both can cause product destruction. This is pure nightmare because what would happen if a developer of the work decided to take the customs path a stack of product for one of allwinner customers would get to the board be ruled as contain copyright infringing work then crushed. This has happened to gameconsoles and other items in the past. The buyer is left out of pocket. Its basically a common mistake since FOSS does not act often that it does not have teeth. The reality most FOSS developers know they have the teeth to put a company out of business so try negotiation. https://libav.org/shame.html you will notice all the ones here are fairly much software companies. Developers don't have very effective teeth to go after software companies. Also remember even if the infringement is preformed by a sub-company the fact its on your device can make that device destroyable and you will be expected to get the compensation out the sub company that provided you with the infringing software. As a matter of fact, Allwinner does not make devices. It makes chips. It is the Allwinner's customers who are making devices. And the unique situation with (at least older) Allwinner based devices is that these devices can be running 100% free software. Very few other hardware vendors are able to match this level of freedom (even Intel based devices are typically shipping with proprietary BIOS firmware). And by the way, I'm not sure if you paid attention to the discussion in this thread, but there is also a reverse engineered hardware video decoder implementation available, which is 100% free software. This means that you don't really need to use any blobs from Allwinner to play your video. And to complement the perfect software freedom, some of the device manufacturers are even making open source hardware (if you have ever heard about this concept). For example, you can check https://www.olimex.com/Products/OLinuXino/open-source-hardware The reality is you are better to break patent law than trademark or copyright as hardware company. Something Allwinner take on board is release the source after the fact is an extremely bad idea. If you go to Intel and Amd you will notice they release the open source code before the chip ship. This means the chips cannot be destroyed at customs. The SoC chips obviously do not contain the kernel code or userland software. You are only able to catch up with the source release after the fact because at this stage the FOSS developers are being kind. Look, you have blatantly violated the netiquette rules in this mailing list. And now you are only able to catch up with the rules after the fact. The ignorant people like you can only get away with their misconduct because the free software developers here are being kind. Just be grateful that nobody suggests to get you banned yet. Siarhei Siamashka the case of the firmware not using the Linux kernel firmware loader what promises that we will not have that happen again. Is there staff training to make sure this does not happen again. How can we be sure that your violation of the netiquette rules will not happen again? Siarhei Siamashka there are compliance tools. http://www.linuxfoundation.org/programs/legal/compliance/tools Are you using them. If not please start using them. If you are using them please open bug reports for the cases that these issues got missed. Are you now telling me to do your homework? But this is not how free software development works. Don't just come here with a consumer attitude. We (free software developers) owe you nothing. Please start using these tools yourself and submit issues at github if you are really interested in improving Allwinner's licenses compliance. Thanks in advance for your cooperation. http://www.binaryanalysis.org/en/home This tool is built particularly to allow FOSS developers to locate infringement in closed source binaries. Basically FOSS developers have tools to find infringement and they have made the tools for your side to detect infringement before it gets out the door. Please allwinner stop
Re: [linux-sunxi] Allwinner GPL violations: definitive proof.
Just look at today's news... Statement in support of Software Freedom Conservancy and Christoph Hellwig, GPL enforcement lawsuit On Thursday, March 5, 2015, Christoph Hellwig, with support from the Software Freedom Conservancy https://sfconservancy.org/, filed suit in Hamburg, Germany https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/ against VMware Global, Inc. Hellwig is a prominent contributor to the kernel Linux, releasing his contributions under the terms of the GNU General Public License (GPL) version 2. VMware, like everyone, is free to use, modify, and distribute such software under the GPL, so long as they make available the human-readable source code corresponding to their version of the software when they distribute it. This simple and fair obligation is the cornerstone of the successful cooperation we've seen for decades between organizations both for-profit and non-profit, users, and developers—the same cooperation which has given us the GNU/Linux operating system and inspired a wealth of free software programs for nearly every imaginable use. Unfortunately, VMware has broken this promise by not releasing the source code for the version of the operating system kernel they distribute with their ESXi software. Now, after many years https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html of trying to work with VMware amicably, the Software Freedom Conservancy and Hellwig have sought the help of German courts to resolve the matter. While the Free Software Foundation (FSF) is not directly involved in the suit, we support the effort. From our conversations with the Software Freedom Conservancy, I know that they have been completely reasonable in their expectations with VMware and have taken all appropriate steps to address this failure before resorting to the courts. Their motivation is to stand up for the rights of computer users and developers worldwide, the very same rights VMware has enjoyed as a distributor of GPL-covered software. The point of the GPL is that nobody can claim those rights and then kick away the ladder to prevent others from also receiving them. We hope VMware will step up and do the right thing, said John Sullivan, FSF's executive director. The suit and preceding GPL compliance process undertaken by Conservancy mirror the work that the FSF does in its own Licensing and Compliance Lab. Both the FSF and Conservancy take a fair, non-profit approach to GPL enforcement https://www.fsf.org/licensing/compliance, favoring education and collaboration as a means of helping others properly distribute free software. Lawsuits are always a last resort. You can support Conservancy's work on this case by making a donation https://sfconservancy.org/donate/. Media Contact John Sullivan Executive Director Free Software Foundation +1 (617) 542 5942 licens...@fsf.org Read this online: https://www.fsf.org/news/conservancy-and-christoph-hellwig-gpl-enforcement-lawsuit On Thu, Mar 5, 2015 at 10:31 PM, oia...@gmail.com wrote: On Friday, March 6, 2015 at 5:42:22 AM UTC+10, Michal Suchanek wrote: Sure, allwinner is required, legally, to release some sources. And it might have signed some NDAs to not release them so it may as much legally be obliged to not release the same sources. It might in fact have put itself into a situation when it is not allowed to ship a product with this software, legally. However, the copyright of the ffmpeg authors or Linux authors is somewhat theoretical in China while the NDA they signed with the business next door is much less. Michal this logic is wrong. Customs I was referring is China own customs. http://www.chinabusinessreview.com/tackling-intellectual-property-infringement-in-china/ You will find customs as one of the methods to enforce against intellectual property infringement this includes copyright infringement. 1/2 a million routers were crushed by China customs when a company refused to release firmware source code as required and their website blocked by the great china firewall. The GUY next door with the NDA over Allwinner is not going to help Allwinner when the products are crushed and Allwinner web site is blocked from the outside world by the great china firewall. FOSS enforcement only seams theoretical in China because FOSS does not do it often. Also normally when FOSS enforcement does happen to Chinese companies they mostly go out of business. The router vendor tired that Chinese smiley face method as well. Allwinner need to make up its mind either it only sells inside china or it want to sell to the world. If it wants to sell to the world software infringement is not on. Also remember github is USA so anything infringing hosted on github can be removed by DCMA orders. Due to this infringement being found the source code need to be mirror to a country where copyright cannot be enforced until its fixed. In fact to remain legally clear it should be removed from
[linux-sunxi] how to build an linux image for A31S
Hi all, I want to use debian or linaro on A31s, but i don't know how to get one, and it seems that the forum only support A10, A20, and A80, I am realy appreciated if you can provide any suggestion, thank you. Best Regards, stone -- 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] how to build an linux image for A31S
Hi, On Fri, 6 Mar 2015 11:48:50 +0800 (CST) li lijiamin...@163.com wrote: Hi all, I want to use debian or linaro on A31s, but i don't know how to get one, First of all, you can check if your device already has a page at the linux-sunxi wiki: http://linux-sunxi.org/Category:Devices If yes, then you can find further instructions there and more details about the mainline u-boot and the mainline kernel support for it. The core A31s SoC features are already supported, but different devices may have different configurations for the peripherals. If there is no device page for your device, then you are encouraged to create one. There is a basic instruction and a checklist for the things to do: http://linux-sunxi.org/New_Device_howto For installing Debian on a few supported Allwinner devices, you can check https://wiki.debian.org/InstallingDebianOn/Allwinner But if the device is not fully supported yet, then the whole process of installation in some way resembles the http://en.wikipedia.org/wiki/Ready-to-assemble_furniture Which means that you may need to be ready to compile the u-boot bootloader and the kernel yourself and then unpack the rootfs with the distribution of your choice (the necessary instructions are available in the linux-sunxi wiki). and it seems that the forum only support A10, A20, and A80, Some A31(s) devices are already supported. But A80 is not quite at that level yet. I am realy appreciated if you can provide any suggestion, thank you. Hope this helped. -- Best regards, Siarhei Siamashka -- 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.
