[linux-sunxi] Re: Semi ad-hoc fosdem meetup.
On Thu, Feb 01, 2024 at 11:46:52AM +0100, Paul Kocialkowski wrote: > Hi Luc, > > On Wed 31 Jan 24, 17:27, Luc Verhaegen wrote: > > Andre had the great idea to create a bit of an informal fosdem meetup. > > > > We will try to get a table under the Janson building on saturday > > afternoon, in the cafeteria. > > > > This is the area under the really big (and ancient) auditorium, where > > you can usually buy coffee and sandwiches. > > It's a great spot for an informal meeting! Usually one of the most calm areas > of FOSDEM (and often a cheat-code to get food easily). There are some post-corona changes. The university computer club used to run this, but they have now moved all their activity to the F building. This is in the center of the map. I have absolutely no idea how this is built up, so it will be a bit adventurous. I have two A4s taped together in landscape, i hope it will be clear enough and that there is a bit of wallspace it can be taped to. Hold on to your horses! 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. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/Zb0EBJjpxNife8i0%40skynet.be.
[linux-sunxi] Semi ad-hoc fosdem meetup.
Hi, Andre had the great idea to create a bit of an informal fosdem meetup. We will try to get a table under the Janson building on saturday afternoon, in the cafeteria. This is the area under the really big (and ancient) auditorium, where you can usually buy coffee and sandwiches. It is tricky to find but you can plot a route on the fosdem map: https://fosdem.org/2024/assets/campusmap-6166e45e7e736823c218c45ac65e02f5f7237111253db302da17bbaa0f4b5683.png The J building is in the bottom middle. You can see 2 dotted lines running to the top right of the J building, one from the H building, one from the carpark. Both routes work. >From 17:30 on, we will try to be there with a smallish sign adhoc taped to the wall saying "#linux-sunxi". If this area for one reason or another is not open (would be a first for me), or there is absolutely no hope of occupying anything in there, one of us will be outside with the sign and we can figure out what to do from there. For those that want to, we can try to figure out where to continue the meeting over supper. Oh, and if you wonder what we each look like, just google, there's enough fotos and videos from our individual talks online. See you there! 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. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/Zbp04Hyf38QxRe7q%40skynet.be.
Re: [linux-sunxi] Re: Did lemaker go belly-up?
On Mon, Jan 03, 2022 at 06:04:51AM -0800, @lex wrote: > They started with low-cost board and the target audience was hobbyists, > amateurs, and students. > They have or had really good products and high quality, so they switched to > high-end boards and different target audiences, and that awkward board > format. > Ohh, not saying rpi format is good.. :) > > And don't forget the aggressive prices from other makers. >From where i sit, lemaker undercut cubie and olimex, in more ways than just price. But it goes to show how important an actual grassroots SoC community with its own documentation is. 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. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/20220121134324.GC20783%40skynet.be.
[linux-sunxi] Did lemaker go belly-up?
The domain lemaker seems to have lapsed. It was there in september: https://web.archive.org/web/20210919203228/http://www.lemaker.org/ But it was gone in november: https://web.archive.org/web/2020065151/lemaker.org And so it goes... 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. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/20220102221812.GB27385%40skynet.be.
[linux-sunxi] Allwinner SDK download disclaimer at odds with GPL
Allwinner requires registration to get access to their version of the required software for more recent chips, aka SDK. CNX software has run through the SDK dance with allwinner for the D1 RISC-V SoC [1]. The article shows a disclaimer [2] that needs to be clicked through to get access to the SDK. It reads: "This deliverable may not be altered, copied, reversed, sold, distributed, or otherwise engaged in commercial activities without prior written permission of the company." Which, to my knowledge, is at odds with the GPL. Thanks to our great community, we have the SDK mirrored. A new manifest still needs to be provided, and the process still needs to be documented on our wiki. [4] Luc Verhaegen. [1] https://www.cnx-software.com/2021/05/02/allwinner-d1-sdk-linux-risc-v-documentation/ [2] https://www.cnx-software.com/wp-content/uploads/2021/05/Allwinner-SDK-Disclaimer.png [3] http://dl.linux-sunxi.org/D1/SDK/ [4] https://linux-sunxi.org/D1#Allwinner_SDK -- 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. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/20210718130326.GA28867%40skynet.be.
Re: [linux-sunxi] alternate irc network -> OFTC
On Sat, May 22, 2021 at 09:43:37PM +0200, Luc Verhaegen wrote: > On Fri, May 21, 2021 at 10:01:12PM +0200, Luc Verhaegen wrote: > > All existing and active founders/operators (mnemoc, turl, plaes, rellla, > libv) were moved. And two new ones (wens, apritzel) were added. > > Whitelogger has now also joined: > https://oftc.irclog.whitequark.org/linux-sunxi > > Luc Verhaegen. Things seem to have escalated last night: https://mastodon.sdf.org/@kline/106299403921451814 "andrew lee just seized over 700 channels on freenode because they mentioned libera.chat in their topic." This was in my server log this morning: "06:15 -rasengan(~rasengan@freenode/staff/rasengan)- [Global Notice] In the recent policy enforcement, some channels were erroneously included. We greatly apologize for the inconvenience. Please contact us in #freenode-services or contact...@freenode.net. Thanks for your patience and choosing freenode!" It's time to move, sadly. Many of the regulars are already on OFTC, and the above has left me little option but to +m the channel on freenode. What a waste. 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. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/20210526064210.GC22252%40skynet.be.
Re: [linux-sunxi] alternate irc network -> OFTC
On Fri, May 21, 2021 at 10:01:12PM +0200, Luc Verhaegen wrote: > Hi, annoying email that i wish i never had to send... > > To ensure continuity, #linux-sunxi on OFTC was registered, and the > existing (active) linux-sunxi founders and ops are added to chanserv > already (2 left to go, hope they read irc/email soon). This should > hopefully provide the stability that we have enjoyed for almost 9 > years... Once the founders have talked through some more things, some > usual suspects will be added as ops, as we might need them now that we > no longer have the stable home that we used to have. All existing and active founders/operators (mnemoc, turl, plaes, rellla, libv) were moved. And two new ones (wens, apritzel) were added. Whitelogger has now also joined: https://oftc.irclog.whitequark.org/linux-sunxi 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. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/20210522194337.GE20601%40skynet.be.
[linux-sunxi] alternate irc network.
Hi, annoying email that i wish i never had to send... To ensure continuity, #linux-sunxi on OFTC was registered, and the existing (active) linux-sunxi founders and ops are added to chanserv already (2 left to go, hope they read irc/email soon). This should hopefully provide the stability that we have enjoyed for almost 9 years... Once the founders have talked through some more things, some usual suspects will be added as ops, as we might need them now that we no longer have the stable home that we used to have. Why OFTC? Well... OFTC has a more primitive chan/nickserv than freenode and libera, and forked away from freenode like 15ys ago... So that's not good... But... It forked away from freenode 15ys ago, has yearly elections, bookkeeping by SPI, and projects like debian and gcc have been there for ages. Even though with my history, i almost never use Xorg/fd.o as a positive example, this project is also moving there. All of this is annoying, and pointless, i know. None of us chose for this to happen, but none of us are here to play political games in the middle of a fork of $infrastructure, we are all here to further support for sunxi hw, and OFTC seems like the least painful road ahead at this time. Not that i want to drive people out of freenode en masse right away, i just do not like to see the channel split over 3 or even more places a month from now. And i definitely do not want to see people give up on irc for something like forums or discord or whatever. So while i am sorry for having to write this, I hope that this is an adequate solution that does not drive anyone away from a stalwart tool of open source development. 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. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/20210521200112.GA18184%40skynet.be.
[linux-sunxi] FOSDEM Hardware Enablement Devroom: call for speakers.
Hi, At FOSDEM on sunday the 2nd of february 2020, there will be another hardware enablement DevRoom. URL: https://fosdem.org/2020/ This devroom covers topics related to hardware support and enablement with free software. It includes the following topics: * peripheral/controller firmwares * hw support and drivers in bootloaders * kernel drivers and hardware interfaces * hardware-related adaptation in operating systems * tools for firmware flashing * tools for low-level development FOSDEM is very much an open source community event, please refrain from turning in a talk that is meant to be purely corporate or a product commercial. Also, this is a highly technical devroom on a conference aimed at developers and advanced users, so only submit a talk on a subject you actually are involved with. Finally, this devrooms focus is the technical aspects of the hardware and its enablement in free projects, rather than the specific applications and use cases that benefit from it. With the return of the Embedded and Automotive DevRoom, we have the ability to schedule full hour talks again, and to go in-depth. If you however only need half an hour, then this is of course also possible. Talk Submission: The venerable pentabarf system will once again be used for talk submission. https://penta.fosdem.org/submission/FOSDEM20 When in pentabarf, spend some time on the abstract and description, for both the event and the speaker. The abstract should be a shortened description, and the event abstract will sometimes even be printed directly in the booklet. BUT, on the website the abstract is immediately followed by the full description. If your abstract is fully descriptive, while terse, you might get away with just the abstract. As soon as your talk is scheduled by the devroom managers, you can see the result of your handiwork on the main website. Please re-use your old pentabarf account instead of creating a new one: lost password: https://penta.fosdem.org/user/forgot_password Talks are either 50 minutes or 20 minutes long, plus 5 minutes for questions. All talks will be recorded, and will be streamed out live, and will later be made available as CC-BY, sometimes minutes after your talk has finished. As for deadlines, the fosdem organizers want to have a finished schedule by the 15th of december, but do not count on that deadline, there are only a limited number of slots available. Given my belatedness in sending out this CFP, i might get a few more days if i am really really nice to the core FOSDEM organizers, but again, do not count on that (extra hugs only go so far when you're built like i am). On your personal page: * General: * First and last name * Nickname * Image * Contact: * email address * mobile number (this is a very hard requirement as there will be no other reliable form of emergency communication on the day) * Description: * Abstract * Description Create an event: * On the General page: * Event title * Event subtitle. * Track: Hardware Enablement Devroom * Event type: Lecture (talk) or Meeting (BoF) * Persons: * Add yourself as speaker. * Description: * Abstract: * Full Description * Schedule: * select your preferred talk length, either 55 or 25 minutes. * Links: * Add relevant links. The mobile phone number is the hardest requirement, so you can be contacted on-the-day when something comes up. Speakers will all receive my mobile number in return. Neither email nor phonenumber are publicy visible, nor will this information be used for anything outside of devroom organization. After your talk has been scheduled, i usually only send out a single email with some organizational details in the days before the event. Everything else can be ignored or will be filled in by me or the FOSDEM organizers. I will be keeping a keen eye on your submissions and will come back with further questions or make small fixes as needed. Feel free to poke me with any questions or anything, both on irc (libv@freenode) and on email (hardware-devroom-mana...@fosdem.org). That's about it. Hope to see you all at FOSDEM :) 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. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/20191210223022.GA15788%40skynet.be.
Re: [linux-sunxi] Marketing Channels A Management View 8th Edition Bert Rosenbloom (Test Bank)
On Wed, May 15, 2019 at 10:56:25AM -0700, solutions books wrote: My bad, i pressed the wrong button in the interface. The user has been banned and reported though, and the message has been removed from the archives, the email itself did make it through. 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. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/20190515184130.GA8520%40skynet.be. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [RESEND PATCH] drm/sun4i: hdmi: Improve compatibility with hpd-less HDMI displays
On Mon, Mar 04, 2019 at 03:06:16PM +0200, Priit Laes wrote: > From: Priit Laes > > Even though HDMI connector features hotplug detect pin (HPD), there > are older devices which do not support it. For these devices fall > back to additional check on I2C bus to probe for EDID data. > > One known example is HDMI/DVI display with following edid: > > $ xxd -p display.edid > 000005a1e0030100150f0103800f05780a0f6ea05748 > 9a2610474f20010101010101010101010101010101012a08804520e0 > 0b10200040009536001800fd0034441a2403000a202020202020 > 001000310a202020202020202020202000102a4030701300 > 782d111e006b > > $ edid-decode display.edid > EDID version: 1.3 > Manufacturer: AMA Model 3e0 Serial Number 1 > Digital display > Maximum image size: 15 cm x 5 cm > Gamma: 2.20 > RGB color display > First detailed timing is preferred timing > Display x,y Chromaticity: > Red: 0.6250, 0.3398 > Green: 0.2841, 0.6044 > Blue: 0.1494, 0.0644 > White: 0.2802, 0.3105 > > Established timings supported: > 640x480@60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz > Standard timings supported: > Detailed mode: Clock 20.900 MHz, 149 mm x 54 mm >640 672 672 709 hborder 0 >480 484 484 491 vborder 0 >-hsync -vsync >VertFreq: 60 Hz, HorFreq: 29478 Hz > Monitor ranges (GTF): 52-68Hz V, 26-36kHz H, max dotclock 30MHz > Dummy block > Dummy block > Checksum: 0x6b (valid) > > Now, current implementation is still flawed, as HDMI uses the > HPD signal to indicate that the source should re-read the EDID > due to change in device capabilities. With current HPD polling > implementation we would most certainly miss those notifications > as one can try just swapping two HDMI monitors really fast. > > Proper fix would be skipping the HPD pin detection and relying > on just EDID fetching and acting on its changes. HPD has been a hard requirement since DDWG came up with DVI somewhere in the late 90s. This monitor is plainly broken, and should not get an expensive i2c address polling based workaround at the driver level. 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] messages from bootlin addresses don't show up on the sunxi list
On Wed, Apr 11, 2018 at 12:15:47PM +0200, Luc Verhaegen wrote: > > In any case, Mike, i just provided Maxime with the email address he > registered with, so he can try to fix his account details. I am not able > to alter the email address on this account directly, the only other > option i have would be to remove this account. I worded this wrong. It is the only option i or other ml admins have. Removing this account and creating a new one seems like more work than being able to rescue this account and by maxime changing his email address (if at all possible). 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] messages from bootlin addresses don't show up on the sunxi list
On Wed, Apr 11, 2018 at 11:59:06AM +0200, Maxime Ripard wrote: > On Wed, Apr 11, 2018 at 11:37:10AM +0200, mike.v...@gmail.com wrote: > > 2018-04-10 10:51 GMT+02:00 Luc Verhaegen <l...@skynet.be>: > > > > > > This seems like something maxime specific. Mylene seems to manage to > > > post to the sunxi ml just fine. Quentin schulz is also in the members > > > list and allowed to post. Same for paulk's bootlin account. > > > > > > There are no pending messages, there is no maxime.rip...@bootlin.com in > > > the banned posters (which is where initial post == spam goes). > > > > > > You will have to go ask maxime. > > > > Your messages do not show up on the list. Can you have a look why? > > I haven't been able to unregister my old (@free-electrons.com) mail > address, and I'm still receiving those mails. And I don't want to > receive all of them in double either. Maxime: to be clear: you have not used your bootlin address to email linux-sunxi@ either, so the ml admins did not miss this, or drop this on the floor. Right? In any case, Mike, i just provided Maxime with the email address he registered with, so he can try to fix his account details. I am not able to alter the email address on this account directly, the only other option i have would be to remove this account. 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] messages from bootlin addresses don't show up on the sunxi list
On Tue, Apr 10, 2018 at 01:32:13AM -0700, Mike Valk wrote: > > Op dinsdag 10 april 2018 10:23:41 UTC+2 schreef Luc Verhaegen: > https://groups.google.com/forum/#!topic/linux-sunxi/s0_rAFP8xx4 > https://lists.denx.de/pipermail/u-boot/2018-April/thread.html#324966 > > I'm not a recipient of either mailing lists. I just use the google > groups/ml archives to keep informed. So full headers will be little > difficult to get for me. But I hope the above example might help. There are > more. > > I guess it happened since Maxime switched to the bootlin.com domain. This seems like something maxime specific. Mylene seems to manage to post to the sunxi ml just fine. Quentin schulz is also in the members list and allowed to post. Same for paulk's bootlin account. There are no pending messages, there is no maxime.rip...@bootlin.com in the banned posters (which is where initial post == spam goes). You will have to go ask maxime. 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] messages from bootlin addresses don't show up on the sunxi list
On Tue, Apr 10, 2018 at 01:20:23AM -0700, Mike Valk wrote: > > > Op dinsdag 10 april 2018 10:17:20 UTC+2 schreef Luc Verhaegen > Hi Luc > > As usual, ml admins will review and whitelist as mails come in and get > > caught. Those admins get sent an email when a mail gets caught. > > > > Fair enough. Maxime's messages don't seem to come through though. Please point out such a message on another ml, or forward an example to me with full mail header info. I think something else is going on here that has nothing to do with the settings or the members list of the linux-sunxi mailing list. 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] messages from bootlin addresses don't show up on the sunxi list
On Tue, Apr 10, 2018 at 12:35:21AM -0700, Mike Valk wrote: > L.S. > > Can someone whitelist bootlin addresses on the sunxi mailinglist? > > Kr, Mike As usual, ml admins will review and whitelist as mails come in and get caught. Those admins get sent an email when a mail gets caught. There is no point in proactively doing this before mails actually hit the ml, or before accounts have had their addresses updated. 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] CHIP goes bankrupt?
On Wed, Apr 04, 2018 at 04:22:02PM +0200, Luc Verhaegen wrote: > On Wed, Apr 04, 2018 at 01:55:36PM +, Benjamin Henrion wrote: > > CHIP goes bankrupt?: > > > > https://hackaday.com/2018/04/03/is-this-the-end-for-the-c-h-i-p/ > > Another $hitpi down the drain. > > ($hitpi: a cheap board, often chinese, trying hard to compete with the > raspberry pi) > > The only notable difference is that this was (at least superficially, > they did seem to have quite some chinese ties) a .us based kickstarter, > and their crowdfunding campaign got bitten hard by the GPL violations > drumbeating. > > So much so that they made a u-turn halfway through their kickstarter > campaign and ended up paying free-electrons to have some of their > developers work on upstream code on paid time. > > But mostly, NTC is/was a lot more noise compared to other $hitpis. > > The only $hitpi i truly am not glad to have seen go was the cubieboard, > as Tom Cubies board(s) and attitude helped make linux-sunxi big. And > that was soon 6 years ago. Also, we still do not have any real info about the c.h.i.p. in our wiki. NTC of course wanted to build its own totally separate community, which is standard $hitpi practice tbh. So here it once again should be clear just how important a vendor neutral wiki is. But that's something sunxi and other projects' longtimers should've known already. 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] CHIP goes bankrupt?
On Wed, Apr 04, 2018 at 01:55:36PM +, Benjamin Henrion wrote: > CHIP goes bankrupt?: > > https://hackaday.com/2018/04/03/is-this-the-end-for-the-c-h-i-p/ Another $hitpi down the drain. ($hitpi: a cheap board, often chinese, trying hard to compete with the raspberry pi) The only notable difference is that this was (at least superficially, they did seem to have quite some chinese ties) a .us based kickstarter, and their crowdfunding campaign got bitten hard by the GPL violations drumbeating. So much so that they made a u-turn halfway through their kickstarter campaign and ended up paying free-electrons to have some of their developers work on upstream code on paid time. But mostly, NTC is/was a lot more noise compared to other $hitpis. The only $hitpi i truly am not glad to have seen go was the cubieboard, as Tom Cubies board(s) and attitude helped make linux-sunxi big. And that was soon 6 years ago. 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] linux-sunxi.org down
On Wed, May 17, 2017 at 09:01:30AM +0200, Benjamin Henrion wrote: > Hi, > > Just to let you know that linux-sunxi.org seems to be down. > > Best, Hetzner moved the server, the xen images for the different vms were not loaded, looking into it. 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] Olimex A20 SOM EVB + DRM + LCD panel, a (someway working) experience..
On Wed, Jan 04, 2017 at 03:44:29PM +0200, Priit Laes wrote: > On Tue, 2017-01-03 at 23:02 -0800, Steffie Chou wrote: > > i compiled with the default defconfig for this Graperain [xxx] EVB > > board and booted. > Ok, so this user should be moderated then. 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: Recommendations for hardware designer for custom Allwinner based Single Board Computer (SBC)?
On Tue, Jan 03, 2017 at 10:46:42PM -0800, Steffie Chou wrote: > Graperain Embedded Industrial SBC Single Board Computer > <https://www.graperain.com/ARM-Single-Board-Computer/> is 8-layer design > which makes it more stable. As full as most wanted expansions, the single > board computer can be used as final product directly, short time to market. > Unlike traditional SBC, Graperain have 32 bit and 64 bit processor, such as > Samsung S5P4418(Cortex-A9), S5P6818(Cortex-A53), RK3288(Cortex-A17, coming > soon) and other arm single board computer Linux and Android design boards. > With it’s full featured I/O, Graperain embedded SBC can be used in a full > range of applications, game machines, education board, kiosk etc. In > addition of SBC, Graperain offer more services like, custom SBC > development, review for custom-design schematic, system engineering tech > support, Android, Linux + qt, Ubuntu developing etc, more than you can > imagine. > > On Friday, October 7, 2016 at 7:01:40 PM UTC+8, Senthil Seveelavananan > wrote: > > > > Hi all, > > > > Given this is where people that actually know whats going on hang out, was > > hoping people could recommend me companies / people to design a custom > > Allwinner based board. > > > > I know about > > - Olimex > > - Banana Pi > > - Orange Pi > > - Friendly Pi, > > > > all recommendations appreciated. > > > > Many thanks > > > > Senthil > > Guys. I noticed this a few s too late. This does not sound like something that should be propagated on our ML. What should i do here... block the user? 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] Fwd: nasty recruiter bs.
On Wed, Sep 21, 2016 at 05:20:40PM -0400, rani rautela wrote: > Hi > > Hope you are doing fine. . !!! > And there goes your posting rights. 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] Kernel damaged device?
On Sat, Aug 20, 2016 at 07:26:46PM -0700, Leonardo wrote: > Hi. I'm building a very minimal Linux distro to use as an embedded system > on a A20 tablet. I don't want to believe this, but I think that booting my > distro has damaged the device. The tablet came with Android. I had it > rooted so I could extract the fex file. Then I got kernel 3.4.104 and uboot > 2016.02 from GitHub, built my file system with buildroot and so on. I'm > using an SD card for now. So I tried booting my system and nothing came up > on the LCD. Then I remove my SD card, try to get back to Android and still > nothing on the screen! The device is not dead. I can access it using ssh > over the wifi, the usb port works fine. Basically I can do anything > remotely. At first I thought I might have damaged something on the PCB > while performing the tests, so I had a second tablet. Boot on Android, > display works fine. Boot on my distro, nothing on screen. Try to get back > to Android, and nothing on the screen again. By the way, the backlight > lights up as usual, so the display is not dead also. I've worked on a > similar project last year and had no problem like this at all. I have no > idea what went wrong. Is it possible that my kernel has damaged the device > somehow? Damage, no. Ruined nand content due to different settings, yes. Thank allwinner for changing its mind on how to configure its nand controller in the middle of the A20 lifetime, while having code in its nand driver that clears the ram if it finds garbage. 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] Request for additions to documents
On Sat, May 21, 2016 at 11:11:27PM +0200, Luc Verhaegen wrote: > On Sat, May 21, 2016 at 01:55:03PM -0700, markdamerell via linux-sunxi wrote: > > > 2. Installing on SD card. This howto assumes that you have > > connected the card to Linux on another machine. But I cannot > > see anything to show how you are to make this connection. > > This is how our manual build howto started. Go read up. Seems i was too impatient on this one. How about this: a) you slot your SD card into your host machine. b) your kernel notices the sd card and assigns it a set of device nodes. If it doesn't you might not have not properly slotted it in, try a) again. c) your system might actually mount existing filesystems for you, in case it probably is wise to unmount them first. This is standard linux usage and not for our howtos. Please use google creatively. 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] Request for additions to documents
On Sat, May 21, 2016 at 01:55:03PM -0700, markdamerell via linux-sunxi wrote: > > The "documents" are the manual build howto & other howtos > that this refers to. It's a wiki. Create an account like normal people. > 1. Git. I believe that Git will work best if new users are > willing to adopt good habits from the beginning. They can > only do this if they are told what the correct practices > are. So I ask that the howto should point new users at > an introduction to Git. No. We are not wikipedia, or a beginners guide on development. Go read up on git somewhere else (like, pretty much the whole of the internet, there are a gazillion howtos there). > 2. Installing on SD card. This howto assumes that you have > connected the card to Linux on another machine. But I cannot > see anything to show how you are to make this connection. This is how our manual build howto started. Go read up. > 3. Backups. If things go wrong, you may well find that you > cannot boot Linux (for reasons unknown) or Android (because > you have over-written it). The Howtos should explain how to > make a backup and how to recover. We tend to only rarely overwrite the actual nand. Sometimes we do kill the nand (with the 3.4 kernel), but you do not get to make backups then either. Go read up. > 4. If you install Linux and it works, you then need a > different set of instructions for recovery. Before you began, > the card probably contained a mixture of Android apps (now > useless) and user data (useful). You need to know how to > separate these and recover only the data. Again, how about using an SD card if you are not sure? Amazing. 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: [PATCH 2/2] ARM: dts: sunxi: Add pll3 and pll7 clock to sun[47]i.dtsi
On Wed, May 04, 2016 at 09:55:47AM +0200, Alexander Syring wrote: > > > > > -- I think i should've marked this one as spam instead. My mistake, sorry. Alexander: plain text emails, like sane people. 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] Ditter V21 HDMI Android TV stick - FEL mode?
On Thu, Jan 28, 2016 at 07:04:28AM -0800, ffum...@googlemail.com wrote: > Hi all, > > I've got a Ditter V21 HDMI Android TV stick, based upon Allwinner A31s SoC: > > http://freaktab.com/forum/tv-player-support/allwinner-tv-players/10567-ditter-v21-a31s-1gb-ram > > Mine gets with the two buttons on the main board (v1.3). http://linux-sunxi.org/New_Device_howto 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] Ditter V21 HDMI Android TV stick - FEL mode?
On Thu, Jan 28, 2016 at 07:41:52AM -0800, Fabio Fumi wrote: > This is the info from Android /system/build.prop, which should help > identifying the device: This is pretty pointless. Create a device page, and follow the new device howto. 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: Mele A200
On Sat, Dec 12, 2015 at 05:57:09PM +, Erico Mendonça wrote: > Hello all, > > I got ahold one a Mele A200, which runs on a Allwinner A10S. I have already > soldered the serial pins, and can see the terminal fine. But couldn't get > working images for anything other than the stock Android firmware. > > Has anyone dealt with this little beast here? Any pitfalls that I should be > aware before delving into the linux-sunxi sources? > Please help improve the wiki page for this device: http://linux-sunxi.org/Mele_A200 By properly working through the http://linux-sunxi.org/New_Device_howto 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] FYI: Wiki problems
On Tue, Dec 01, 2015 at 07:46:01AM +0100, Thomas Kaiser wrote: > Hi, > > currently it's not possible to edit anything in the wiki. Authentication > problems due to "Warning: Unknown: write failed: No space left on device > (28) in Unknown on line 0" > > Best regards, Fixed, again. 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] Requesting Help on a USD15, Allwinner Quadcore 1.2Ghz 64-bit A53 Hardware
On Sat, Nov 28, 2015 at 05:43:45PM -0800, KH Goh wrote: > Hi Luc Verhaegen, > Thanks for your advise, we get what you are saying. From our side, we are > trying out best to work closely with the open source community and trying > to do our part as much as possibly can. We are committed to make our > hardware and software as open as possible, but subject to the license > agreement that place upon us by our supplier. But by having a good > relationship between us and the supplier, I think we should be able to iron > out most of the problem. > > In terms of the hardware, at the moment we are having 2 unit of Pine64 > Engineering board (Please refer here for the spec http://pine64.com/product > ), and would like to donate it to the community for further evaluation and > testing. Since we are a newcomer in this community, we would like you to > advise us on who and where should we send the 2 board to. > > Thanks for your advise and appreciate your kind assistance. > Regards, > KH Goh > > > On Saturday, November 28, 2015 at 9:01:31 PM UTC+8, Luc Verhaegen wrote: > > > > On Sat, Nov 28, 2015 at 12:38:16AM -0800, khg...@gmail.com > > wrote: > > > > Thanks for contacting the canonical source of most things > > sunxi/allwinner before actually launching your kickstarter campaign. > > > > This is the first time since the original cubieboard that such a thing > > has happened. Many companies with similar products only afterwards find > > out to what extent they do depend on the linux-sunxi community, and then > > change their story in either direction. Often the work done by the > > people of the linux-sunxi community gets used directly, cloned/forked, > > and nothing is ever given back. > > > > As you can see, we (and while i do not speak for all of us, i know that > > i am not alone here) are sceptical about whoever approaches us like > > this, especially when one of the first statements is "budget > > constraints". You cannot expect the linux-sunxi community to do your > > work for you for free. > > > > You should however donate boards to many known and active linux-sunxi > > developers, but for that you must not expect anything in return. > > Whatever then happens, happens, or it doesn't. The results are usually > > quite positive, especially given the limited cost of said boards, but it > > will hardly ever consist of full support for your product (especially > > when based on a new SoC variant). > > > > If you wish to have more complete support, you can always try to hire > > known linux-sunxi developers directly, or work with those members of our > > community who do contracting. The choice is up to you. > > > > Thanks for reaching out to us before launching your marketing campaign, > > i hope that your collaboration with linux-sunxi ends up being just as > > fruitful as your kickstarter. > > Thanks for your advise, we get what you are saying. From our side, we are > trying out best to work closely with the open source community and trying > to do our part as much as possibly can. We are committed to make our > hardware and software as open as possible, but subject to the license > agreement that place upon us by our supplier. But by having a good > relationship between us and the supplier, I think we should be able to iron > out most of the problem. That last sentence reads, to me, as; "we will work out all product support issues with our supplier" (being allwinner). That then makes me wonder how far along you are with developing software support for your product. You will be amazed to what extent you do depend on linux-sunxi, for a very broad range of what you would call product support. I do wish to warn you though, about the use of the term "open source platform". Be very careful with your marketing there: 1) I see no indication that your product will be "open source hardware" (OSHW), like with Olimex devices. 2) Allwinner is known to ship binary, GPL violating, blobs and to need hard convincing to change this. The status of their ffmpeg LGPL violation is still very questionable, but has entered a dark grey zone now, where legal action is a toss-up. Allwinner, and its customers, had to be forced, hard, and even then did only as much as they could get away with. 3) Due to the hardware you are using, you are going to have non open source software (CedarX, Mali). All three of the above make your statement that "The PINE64 platform is fully open source" very questionable. So given both of the above points, i implore you to do more than your competition, otherwise you will risk becoming yet another $shit_pi
Re: [linux-sunxi] Requesting Help on a USD15, Allwinner Quadcore 1.2Ghz 64-bit A53 Hardware
On Sat, Nov 28, 2015 at 12:38:16AM -0800, khgo...@gmail.com wrote: > Hi, > We are a group of people currently trying to come out with a very low > cost single board computer, by making use of Allwinner Quadcore 1.2Ghz > 64-bit A53 CPU. The target costing for the single board computer is > USD15. The hardware will have a 4K HDMI video output and on board > ethernet connection. Further more, each board will has its own unique > MAC address. The objective for this project is to allow individual, > having the opportunity to learn IT knowledge with a friction of the > cost. Please refer to pine64.com for more detail on the hardware > specification. > > Currently, the hardware development on the board is almost ready. And > with us, is the full Linux BSP with the true 64bit compiler. Due to > budget constrain and our limited know-how in Linux, We would like to > request the help from this community to bring up the Linux into a full > function Ubuntu desktop, thus allow the user to truly owning a fully > function open source computer with just a friction of the cost. > > As for the hardware itself, currently we are in the mist of building > some sample board to allow any interested developer to work on it. > > Thanks and Regard, > KH Goh Hi, Thanks for contacting the canonical source of most things sunxi/allwinner before actually launching your kickstarter campaign. This is the first time since the original cubieboard that such a thing has happened. Many companies with similar products only afterwards find out to what extent they do depend on the linux-sunxi community, and then change their story in either direction. Often the work done by the people of the linux-sunxi community gets used directly, cloned/forked, and nothing is ever given back. As you can see, we (and while i do not speak for all of us, i know that i am not alone here) are sceptical about whoever approaches us like this, especially when one of the first statements is "budget constraints". You cannot expect the linux-sunxi community to do your work for you for free. You should however donate boards to many known and active linux-sunxi developers, but for that you must not expect anything in return. Whatever then happens, happens, or it doesn't. The results are usually quite positive, especially given the limited cost of said boards, but it will hardly ever consist of full support for your product (especially when based on a new SoC variant). If you wish to have more complete support, you can always try to hire known linux-sunxi developers directly, or work with those members of our community who do contracting. The choice is up to you. Thanks for reaching out to us before launching your marketing campaign, i hope that your collaboration with linux-sunxi ends up being just as fruitful as your kickstarter. 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] Banana Pi M3 (A83T based) soon ready to donate
On Sat, Nov 28, 2015 at 05:51:15PM +0100, Thomas Kaiser wrote: > Hi, > > anyone interested in one of SinoVoip's Banana Pi M3 to improve A83T > support? > > I've been selected to receive a free sample by SinoVoip due to being their > most active forum member (a bit weird since most of the times I advise > there against choosing SinoVoip products due to worst software/support > possible :-) and still can't believe that instead of sending a contract > killer to my address they obviously shipped the board instead: > > https://nolp.dhl.de/nextt-online-public/set_identcodes.do?idc=7214605425 > > I'll take some pictures for our wiki, fill in informations there, provide > a working Debian image and a set of tools to combine any rootfs with > bootloader/kernel (none of the few linux images SinoVoip provides for > download currently work since they're all corrupted... and they ship the > devices without eMMC being populated) and write a review of the board. > Will take approx. 2 weeks counting from the board's arrival ‹ see tracking > URL above if you apply. > > Then I'm done with it and would love to send the board to someone else > working on A83T who has a better use for it than me (don't need it, A20 > still the best due to SATA even if it's slow for unknown reasons :-) Keep it, you're doing good work. 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] Updated manual build howto and device page suggestion.
Hi, Since our current world is one where people like me and Alejandro are not able to spend that much time on sunxi anymore, and one where the upstream support has advanced massively, it is high time to update our wiki. Since i am giving my lime board an actual purpose, i adjusted the lime page's (http://linux-sunxi.org/Olimex_A10-OLinuXino-Lime) Manual build section to be more in touch with the current reality. I have reduced the information under the manual build section to only show the relevant build targets or board config files. This reduces the chance of people taking shortcuts and getting lost, instead of using the manual build howto. It also reduces the chance of device pages becoming out of date. I have also restructured the manual build howto to clearly show the difference between sunxi/legacy and upstream/mainline. Not all children of the manual build howto are properly updated yet, but now that at least the direction should be clearer. Since it is the weekend and we have become more incorporated this last year or so, feedback on irc has so far been limited. So more feedback welcomed. 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] Login to wiki not possible
On Fri, Sep 04, 2015 at 01:11:10AM -0700, m.silentcr...@gmail.com wrote: > Hi, > > the login to the wiki isn't possible at the moment. It throws the following > error: > > > Warning: Unknown: write failed: No space left on device (28) in Unknown on > > line 0 > > > > Warning: Unknown: Failed to write session data (files). Please verify that > > the current setting of session.save_path is correct (/var/lib/php5) in > > Unknown on line 0 > > If it's not just me who sees this message, then maybe somebody can take care > of it? > > Thanks and regards, > > Timo Fixed now. Thanks for reporting this! 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] Broken Links - http://linux-sunxi.org/More-images
On Thu, Jul 23, 2015 at 08:56:35PM -0700, Jan Zumwalt wrote: Re: http://linux-sunxi.org/More-images The links to images on this page are broken. They link to Ubunta One file server which says the server has been shutdown. So where is a comprehensive list of CB2 OS imgs? It's a wiki. Feel free to fix it. 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] Your outrageous wiki edits.
Hi Kevin, I just noticed your edits to our GPL violations page. It seems that you and Allwinnwer still have not fully comprehended just how you went wrong and what can be done to fix it. The most remarkable changes (which i have undone) were: a) that since you aren't really using some parts of the code (dram scaling) anymore these days, Allwinner isn't really violating the gpl all that much anymore and then the fact that it once violated the GPL can be totally brushed under the carpet. b) the fact that allwinner was not the original violator on some touchscreen drivers, the fact that it was not allwinner that produced those binaries, makes it all totally ok that allwinner shipped those binaries, which in turn makes allwinner definitely not a repeat violator of the gpl, and this bit of history should totally be brushed under the carpet as well. WTF? Have you not learned anything, or are you actively playing with us? How many months now have you and the rest of your company had to get up to speed on this topic? What is it that is so difficult here, or why are you trying to play these games still? Also, with changes like this, it would not be wrong for me or others to block your wiki account. Be very careful what future steps you take. In a case like this, it is also seriously not done to execute such controversial edits yourself. You ask someone from the opposite side (like me) or someone totally independent (as in, not one of your pathetic strawmen) to review the current status and validity of the content of such a controversial wiki page. It seems that you and Allwinner haven't learned anything there either. Are the things that i beat into you and allwinner really the only things that stick? 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] Further Allwinner misbehaviour.
On Mon, Jun 29, 2015 at 02:19:00AM +0200, Henrik Nordström wrote: tor 2015-06-25 klockan 12:13 +0200 skrev Luc Verhaegen: The bad copyright headers is just stupidity. The direct loading of non-LGPLed binaries into LGPLed code is very deliberate. And to my best understanding is not in any way a violation of the LGPL license. Care to explain what I am missing? (ignoring any past state of these files) If the code had been GPL licensed then sure. But this is LGPL with it's implicit linking exception. Yes, you are right. I always assumed that LGPL only worked upwards, but after a very thorough read there is nothing in the license that clearly defines this. It does however seriously push the boundary of derivative work, not only because it is being loaded into the LGPLed library and does not work standalone or with other software, but more importantly because this .so does not function without LGPLed infrastructure provided in the top level software. The line becomes very blurry here, and whether this is derivative work or not will probably differ upon which lawyer you ask. What is clear however is that Allwinner can no longer feign innocence, lack of information, lack of knowledge, lack of understanding or just plaing old stupidity. It clearly is very much aware of what its legal obligations are, and is very actively feeling for where those boundaries truly lie, and where the lines of the LGPL license become blurry. Allwinner is trying to get away with the maximum of what it thinks it can get away with, and nothing has changed. Allwinner has not learned a single thing, and still is actively hostile towards free software, and has no real intention of proactively working with the linux sunxi community and its customers. While we all knew that to be true, this action is solid proof to that end. It is time to extend the negative marketing campaign to some of Allwinners customers, and truly hit Allwinner where it hurts. 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] Further Allwinner misbehaviour.
On Thu, Jun 25, 2015 at 12:56:37PM +0300, 'Simos Xenitellis' via linux-sunxi wrote: My point has been that if there are things in the repository that should be fixed, then point them out and explain them. The bad copyright headers is just stupidity. The direct loading of non-LGPLed binaries into LGPLed code is very deliberate. We could very well push for a full and complete release of the original code, and get Allwinner in even more legal trouble with other parties. Or, and this is, or was if allwinner keeps this bullshit up, clearly what i was aiming for, Allwinner plays nice and releases _everything_ in freshly written code which does not violate the IP/copyright of non-open source participants. Allwinner clearly does not want to go there, so perhaps we should go do what we legally can do. The way I see the whole situation is this: It is true that Allwinner did not make effort over the years for mainline Linux kernel support. Whatever support is there for the A10, A13, A20, etc, is the result of the hard work of this community. Working on mainline support is initially expensive in terms of resources but builds an ecosystem and opens up markets. It makes business sense. As a community, we need to figure out what we need from Allwinner. Do we need specific SoC information so that we do the mainline effort on our own? And among all things that can be asked, we prioritize to those that are really needed at the moment. Do we need Allwinner to fund some developers so that they work full-time on this? We would need to start talking about goals and targets. Stop it, you are just stalling. Allwinner knows what we want, but it very clearly does not want to give it. Let me quote a recent comment on phoronix: But to find people accusing phoronix of copy-paste journalism (which as far as I know would be no crime) and at the same time justifying a multimillion company for taking the work of others and infringing the law is astonishing. So big companies must be prompty excused and gently persuaded that obeying the law is good for them so that they maybe can find a way to further their profits even without selling other people's (companies and volunteers) works without their consent, but a website must be required to excel in journalistic fact-checking and never blow the whistle? What's next ? Are they going to arrest me for public disorder if I cry thief! at someone running away with my wallet ? Someone which of course has a different enterpreneurship culture, faces neck-breaking competition and tries hard to improve best practices in his pickpocketing cutting edge innovation, so should be invited to tea in a cozy lobby at his earliest convenience and nicely begged (again) asking to maybe please return the wallet or at least some documents there when he can spare a little moment and kindly get his busy fingers to it. Simos, you are not in any way credible. You very one-sidedly chose Allwinners side, and have always downplayed allwinners legal obligations. Whatever Allwinner has promised you or is paying you, it is being wasted, as very few people take you seriously. You are noise, and are wasting a lot of our time in the process, and on top of that giving Allwinner false ideas of what they could potentially get away with. 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] Further Allwinner misbehaviour.
On Wed, Jun 24, 2015 at 10:25:16PM +0300, 'Simos Xenitellis' via linux-sunxi wrote: On Wed, Jun 24, 2015 at 7:51 PM, andres...@gmail.com wrote: If something needs to get fixed in those repositories (https://github.com/allwinner-zh/), point it out constructively. It is constructive to pinpoint the list of files that need changing, as in https://github.com/allwinner-zh/media-codec/issues/8 Simos Ben and Kevin had been told in the region of a dozen times that all those files needed to be LGPLed. There has been no excuse for misunderstanding this. Their lack of comprehension is very deliberate, and can only be understood as deceipt. And that is how i understand you as well. 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] Further Allwinner misbehaviour.
Hi, It's been a month since Allwinners big open source release, where they tried to shut up the big (and very justified) GPL violations noise by releasing some code which moves decoder codecs into modules, and by releasing some codecs as open source as well. As i predicted then, Allwinner now has taken the next step: They produced a binary for the decoder, which is loaded in: https://github.com/allwinner-zh/media-codec/blob/72f2b8537/sunxi-cedarx/SOURCE/vencoder/venc_device.c Note the Proprietary license notice on top of this and other new files. Even if we ignore the past, all of this is built together with LGPLed code, and the binary is being dlopened into this LGPLed code. Quite illegally so. This is further deliberate avoidance of responsibility by Allwinner. One can only assume that Allwinner is incorrigible at this point. They have been told time and time again what is wrong and they have time and time again been given possible ways out, in great detail. All we get though, is microsteps to take off the heat, followed by further deliberate breaking/bending of the rules. This also sheds a further shadow on the C.H.I.P. project. Clearly the Next Thing Co. guys were very gullible when they went into business with Allwinner (and believed the statements made by allwinner). Later during the run of the kickstarter campaign, after all the noise had been made on the internet about GPL Violations, Next Thing Co. loudly claimed that they are working the Free Electrons and that all promises of open sourceness and such would be kept (all?). While this move in itself was very laudable, it did underline the fact that Next Thing Co. had not done its homework beforehand. Now Allwinner does this, which clearly goes in against everything the Next Thing Co. people have promised us so far... Allwinner has some explaining to do (as does Next Thing Co, to a lesser extent). 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] Further Allwinner misbehaviour.
On Mon, Jun 22, 2015 at 04:28:56PM +0300, 'Simos Xenitellis' via linux-sunxi wrote: On Mon, Jun 22, 2015 at 3:19 PM, Luc Verhaegen l...@skynet.be wrote: Hi, Hi, This is another 'Luc drama' installment, full of loaded, sentimental phrases. Just like watching another episode of The Thick of It while it has ceased to be funny any more. The main character in that series is trying to be the central figure by being ferocious on anything that does not go through him first. All that leads to a dysfunctional result and makes the viewers think: do we really need that? Finest satire that show, I tell you. Are we able to get any important bits out of the sentimental stuff? It's been a month since Allwinners big open source release, where they tried to shut up the big (and very justified) GPL violations noise by shut up releasing some code which moves decoder codecs into modules, and by releasing some codecs as open source as well. As i predicted then, i predicted Allwinner now has taken the next step: They produced a binary for the decoder, which is loaded in: https://github.com/allwinner-zh/media-codec/blob/72f2b8537/sunxi-cedarx/SOURCE/vencoder/venc_device.c Note the Proprietary license notice on top of this and other new files. The licence text in a header file. It's one of the easy things to fix. Such cases occur frequently with many companies. There was a similar issue earlier and got fixed. Even if we ignore the past, all of this is built together with LGPLed code, and the binary is being dlopened into this LGPLed code. Quite illegally so. The question is, what options are there for an LGPL library to use dynamically other (non-LGPL) code, or how can your program use that LGPL library and dynamically some other (closed-source) code as well. Here is a good summary, https://en.wikipedia.org/wiki/GNU_General_Public_License#Linking_and_derived_works This is further deliberate avoidance of responsibility by Allwinner. One can only assume that Allwinner is incorrigible at this point. They have been told time and time again what is wrong and they have time and time again been given possible ways out, in great detail. All we get though, is microsteps to take off the heat, followed by further deliberate breaking/bending of the rules. deliberate breaking/bending of the rules One may ask, deliberate? (if it is even really breaking/bending). On the Internet apparently it does not matter if you justify a claim. This also sheds a further shadow on the C.H.I.P. project. Clearly the Next Thing Co. guys were very gullible when they went into business with Allwinner (and believed the statements made by allwinner). Later during the run of the kickstarter campaign, after all the noise had been made on the internet about GPL Violations, Next Thing Co. loudly claimed that they are working the Free Electrons and that all promises of open sourceness and such would be kept (all?). While this move in itself was very laudable, it did underline the fact that Next Thing Co. had not done its homework beforehand. Now Allwinner does this, which clearly goes in against everything the Next Thing Co. people have promised us so far... Apparently, this e-mail is meant for those like Phoronix, so that they can rehash without checking and quickly repost. Is there really need for such drama? The A13 has been largely mainlined by members of this community and the R8, being a bit different, needs some extra work. Instead of making it a volunteer effort to linux-sunxi, they are working with Free Electrons in order to fix any issues pertaining to mainline support. Simos You can stop attempting to justify Allwinners' (and their partners') actions now, it's simply no longer credible. 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] Storage issue on linux-sunxi.org
On Tue, Jun 16, 2015 at 10:18:33AM +0300, 'Simos Xenitellis' via linux-sunxi wrote: Hi All, One of the partitions on linux-sunxi.org got full and requires attention. When you visit the website, it shows at the bottom of each page Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php5) in Unknown on line 0 Simos As you noticed, you should poke people on irc next time: likely candidates: mnemoc, turl, libv, ... 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] Discussion about mainlining the A83T
On Sat, Jun 13, 2015 at 12:05:28PM +0300, 'Simos Xenitellis' via linux-sunxi wrote: Hi All! Recently, several people received developer boards with the A83T SoC. I have collected information from a few sources and put them on https://linux-sunxi.org/User:Simos/H8HomletProtoV20_A83T The page includes a comparison of modules of the A83T with other A-line SoCs. There are high-resolution images of the board. In addition, the page has boot messages and also output of commands from the pre-installed BR Linux (kernel version: 3.4). I'ld like to start a thread about the planning of the mainlining of the A83T. If there are any other topics not directly related to this thread, please start a new thread. Simos Try the New_Device_Howto. 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: New Linux Foundation Members Advance Open Source In Enterprise Computing
On Fri, Jun 12, 2015 at 11:59:50AM +0300, 'Simos Xenitellis' via linux-sunxi wrote: Hi All, Another relevant item from the Linux Foundation regarding new members, http://www.linuxfoundation.org/news-media/announcements/2015/06/new-linux-foundation-members-advance-open-source-enterprise Among the newest members is Allwinner and the press release mentions: *Allwinner is joining the Linux Foundation to support Linux and to improve what we see as two important open source software development capabilities: collaboration and compliance,* said Jack Lee, Chief Marketing Officer, Allwinner Technology. *These two concepts are critical yet difficult to master for new Linux community entrants like ourselves.* Simos Would any of this have happened if Allwinner hadn't been so publically exposed for being the GPL violators that they (still!) are? 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: 2015 SBC survey by Linux Foundation/LinuxGizmos
On Fri, Jun 12, 2015 at 11:13:34AM +0200, Luc Verhaegen wrote: On Fri, Jun 12, 2015 at 11:46:27AM +0300, 'Simos Xenitellis' via linux-sunxi wrote: On Thu, May 21, 2015 at 5:24 PM, Simos Xenitellis simos.li...@googlemail.com wrote: Hi All, The Linux Foundation and Linux Gizmos are running (also) this year a survey on small-board computers, 1. http://www.linux.com/news/embedded-mobile/mobile-linux/831550-survey-best-linux-hacker-sbcs-for-under-200 2. http://linuxgizmos.com/rate-these-sub-200dollar-hacker-sbcs-win-one-of-20/ This year they include 54 SBCs, out of which 12 are based on Allwinner SoCs, a. Two from Olimex b. One from SinoVoip c. One from LeMaker d. Three from CubieTech e. Three from LinkSprite f. Two from Shenzhen Xunlong Software The result of the survey is to produce a Top 10 list based on popularity. The purpose of the survey appears to be to gauge interest in open designs of boards and get manufacturers to work towards that direction. Here are the guidelines for the inclusion of a new board to the list, http://linuxgizmos.com/rate-your-favorite-open-single-board-computers/#open-sbc-guidelines If a company is producing developer boards and satisfy the requirements for inclusion, they can provide five boards to the Linux Foundation so that they are given away to those that took the survey. At this survey, there are four different boards to be given away and none has an Allwinner SoC. Here is the survey, https://www.surveymonkey.com/r/2015SBCS The 2015 Hacker SBC Survey has ended and here are the results, http://linuxgizmos.com/raspberry-pi-stays-sky-high-in-2015-hacker-sbc-survey/ Specifically, 1. The survey had a special feature where you picked three SBCs depending on how favorite they were to you. Then, it would triple the votes for Choice #1, double the votes for Choice #2 and extract the results. Obviously, such a method favors what has been put as Choice #1, the most favorite. 2. At positions #1 and #3, the Raspberry Pi 2 and Raspberry Pi respectively. Yep, the single core Raspberry Pi got third place. 3. At position #2 was the BeagleBone Black. 4. In the top ten, there were three ODROID SBCs. ODROID is doing a great job in promoting their boards. They have a great page showcasing what you can do with their boards (such as http://www.hardkernel.com/main/products/prdt_info.php?g_code=G141578608433), they have a monthly magazine at http://magazine.odroid.com/ and their forum is very active. 5. Out of the 53 Small Board Computers in the competition, there were no Allwinner boards this year in the top Ten. 6. An easy comparison of the specs for the Top Ten is at http://files.linuxgizmos.com/2015-hacker-sbc-survey-top-10-sbc-specs-comparison.jpg It is interesting to notice that several Mali and PowerVR GPUs make it to the top ten. 7. The Raspberry Pis have the Videocode IV GPU. When the first RPi board was released, it did not have a free driver for the GPU. Two years later, Broadcom released some source and documentation which were not sufficient. The turning point was in June 2014 when Eric Anholt was employed by Broadcom to write a free driver for VC4, https://en.wikipedia.org/wiki/VideoCore#Linux_support 8. There were three Cubieboard models which got 357 points and two OLinuXino models that got 195 points. 9. In the 2014 SBC Survey, the Banana Pi got the fifth place. This year, the companies (LeMaker, SinoVoip) that made the Banana Pi decided to split, creating their separate products. The SinoVoip board got 14th place, the LeMaker got the 16th place. 10. The Orange Pi was quite low in the ranking (too new entrant for the survey). 11. Among the buying criteria, the highest was Open source software support (sic). Next came the Community ecosystem. I think these two are critical for the success of an SBC, and companies that make SBCs, should make effort to create such communities. Simos Amazing how you left the following snippet out: One processor trend did seem clear, however, judging both from the selections and reader comments. The open source community appears to be increasingly frustrated with Allwinner’s Linux support. While three Allwinner based boards made last year’s top 10, there are none this year. After the 11th Place Cubieboard4, with its octacore Allwinner A80, the next Allwinner board on the list is the A31-based Banana Pi M2 at number 14. People would think that that is the most relevant statement in that whole survey, but not a hint of it can be seen in your email. Stop trying to distort the truth. Similarly, i cannot find any mention of your point 7 in that article. But thanks for reminding me that that would not have happened if it was not for the fact that i did lima, and that i corrected
Re: [linux-sunxi] Re: 2015 SBC survey by Linux Foundation/LinuxGizmos
On Fri, Jun 12, 2015 at 11:46:27AM +0300, 'Simos Xenitellis' via linux-sunxi wrote: On Thu, May 21, 2015 at 5:24 PM, Simos Xenitellis simos.li...@googlemail.com wrote: Hi All, The Linux Foundation and Linux Gizmos are running (also) this year a survey on small-board computers, 1. http://www.linux.com/news/embedded-mobile/mobile-linux/831550-survey-best-linux-hacker-sbcs-for-under-200 2. http://linuxgizmos.com/rate-these-sub-200dollar-hacker-sbcs-win-one-of-20/ This year they include 54 SBCs, out of which 12 are based on Allwinner SoCs, a. Two from Olimex b. One from SinoVoip c. One from LeMaker d. Three from CubieTech e. Three from LinkSprite f. Two from Shenzhen Xunlong Software The result of the survey is to produce a Top 10 list based on popularity. The purpose of the survey appears to be to gauge interest in open designs of boards and get manufacturers to work towards that direction. Here are the guidelines for the inclusion of a new board to the list, http://linuxgizmos.com/rate-your-favorite-open-single-board-computers/#open-sbc-guidelines If a company is producing developer boards and satisfy the requirements for inclusion, they can provide five boards to the Linux Foundation so that they are given away to those that took the survey. At this survey, there are four different boards to be given away and none has an Allwinner SoC. Here is the survey, https://www.surveymonkey.com/r/2015SBCS The 2015 Hacker SBC Survey has ended and here are the results, http://linuxgizmos.com/raspberry-pi-stays-sky-high-in-2015-hacker-sbc-survey/ Specifically, 1. The survey had a special feature where you picked three SBCs depending on how favorite they were to you. Then, it would triple the votes for Choice #1, double the votes for Choice #2 and extract the results. Obviously, such a method favors what has been put as Choice #1, the most favorite. 2. At positions #1 and #3, the Raspberry Pi 2 and Raspberry Pi respectively. Yep, the single core Raspberry Pi got third place. 3. At position #2 was the BeagleBone Black. 4. In the top ten, there were three ODROID SBCs. ODROID is doing a great job in promoting their boards. They have a great page showcasing what you can do with their boards (such as http://www.hardkernel.com/main/products/prdt_info.php?g_code=G141578608433), they have a monthly magazine at http://magazine.odroid.com/ and their forum is very active. 5. Out of the 53 Small Board Computers in the competition, there were no Allwinner boards this year in the top Ten. 6. An easy comparison of the specs for the Top Ten is at http://files.linuxgizmos.com/2015-hacker-sbc-survey-top-10-sbc-specs-comparison.jpg It is interesting to notice that several Mali and PowerVR GPUs make it to the top ten. 7. The Raspberry Pis have the Videocode IV GPU. When the first RPi board was released, it did not have a free driver for the GPU. Two years later, Broadcom released some source and documentation which were not sufficient. The turning point was in June 2014 when Eric Anholt was employed by Broadcom to write a free driver for VC4, https://en.wikipedia.org/wiki/VideoCore#Linux_support 8. There were three Cubieboard models which got 357 points and two OLinuXino models that got 195 points. 9. In the 2014 SBC Survey, the Banana Pi got the fifth place. This year, the companies (LeMaker, SinoVoip) that made the Banana Pi decided to split, creating their separate products. The SinoVoip board got 14th place, the LeMaker got the 16th place. 10. The Orange Pi was quite low in the ranking (too new entrant for the survey). 11. Among the buying criteria, the highest was Open source software support (sic). Next came the Community ecosystem. I think these two are critical for the success of an SBC, and companies that make SBCs, should make effort to create such communities. Simos Amazing how you left the following snippet out: One processor trend did seem clear, however, judging both from the selections and reader comments. The open source community appears to be increasingly frustrated with Allwinner’s Linux support. While three Allwinner based boards made last year’s top 10, there are none this year. After the 11th Place Cubieboard4, with its octacore Allwinner A80, the next Allwinner board on the list is the A31-based Banana Pi M2 at number 14. People would think that that is the most relevant statement in that whole survey, but not a hint of it can be seen in your email. Stop trying to distort the truth. Similarly, i cannot find any mention of your point 7 in that article. But thanks for reminding me that that would not have happened if it was not for the fact that i did lima, and that i corrected the Raspberry Pi Foundations big but ultimately statement late 2012. Luc Verhaegen. -- You received this message because you are subscribed to the Google Groups linux-sunxi group
Re: [linux-sunxi] Re: New Linux Foundation Members Advance Open Source In Enterprise Computing
On Fri, Jun 12, 2015 at 11:14:44AM +0200, Luc Verhaegen wrote: On Fri, Jun 12, 2015 at 11:59:50AM +0300, 'Simos Xenitellis' via linux-sunxi wrote: Hi All, Another relevant item from the Linux Foundation regarding new members, http://www.linuxfoundation.org/news-media/announcements/2015/06/new-linux-foundation-members-advance-open-source-enterprise Among the newest members is Allwinner and the press release mentions: *Allwinner is joining the Linux Foundation to support Linux and to improve what we see as two important open source software development capabilities: collaboration and compliance,* said Jack Lee, Chief Marketing Officer, Allwinner Technology. *These two concepts are critical yet difficult to master for new Linux community entrants like ourselves.* Simos Would any of this have happened if Allwinner hadn't been so publically exposed for being the GPL violators that they (still!) are? Luc Verhaegen. Which reminds me... It's been almost a month since they released a partial replacement for CedarX. I think some more noise needs to be made before Allwinner completes this. 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] uboot source contained in merii optimus image
On Wed, May 27, 2015 at 01:16:58PM +0300, Simos Xenitellis wrote: On Wed, May 27, 2015 at 12:53 PM, Wilfried Gösgens dotheb...@gmail.com wrote: I've located the uboot sourcecode inside of the A80 Optimus Meriilinux sdk found at: http://bbs.merrii.com/en/viewtopic.php?f=48t=2086sid=5101df3045fa900da3f162048a5d8ea2 it can be found in: a80_MerriiLinux_optimus_v1/brandy/u-boot-2011.09 (just in case there are any differences to the official allwinner source drop on Github) The SDK is a big file to download from pan.baidu.com. You can either compare with https://github.com/allwinner-zh/bootloader (includes the A80) or put the zipped SDK subdirectory somewhere online. Simos You clearly missed the conversation on irc which preceded this. 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] Lemon Pi on Indiegogo campaign,$35 ARM Quad-core A9 and Imagination PowerVR SGX544 open source board
On Wed, May 27, 2015 at 02:52:57PM +0200, Carlo Caione wrote: On Wed, May 27, 2015 at 9:04 AM, Luc Verhaegen l...@skynet.be wrote: On Tue, May 26, 2015 at 08:06:13PM -0400, jonsm...@gmail.com wrote: Are there lists for these other Chinese vendors? I haven't found one for Rockchip or AMLogic. As stated on http://linux-rockchip.info/mw/ it is on googlegroups as well: https://groups.google.com/forum/#!forum/linux-rockchip For amlogic, things are not as far advanced: http://linux-meson.com/doku.php#community Well, things are going on actually. Really slowly since I'm basically the only one working on it, but they are going on. :) 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] Lemon Pi on Indiegogo campaign,$35 ARM Quad-core A9 and Imagination PowerVR SGX544 open source board
On Wed, May 27, 2015 at 09:28:18AM +1000, Julian Calaby wrote: Hi, Stupid question: isn't this kinda off-topic for this list as the SoC on the LemonPi isn't an Allwinner part? This is very off-topic and should be considered spam indeed. So this is what the crowd-funding and/or raspberry pi beater golddiggers have come to these days... 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] Lemon Pi on Indiegogo campaign,$35 ARM Quad-core A9 and Imagination PowerVR SGX544 open source board
On Wed, May 27, 2015 at 10:58:45AM +0300, Priit Laes wrote: On Wed, 2015-05-27 at 00:54 -0700, Andrea Venturi wrote: On Wednesday, May 27, 2015 at 9:13:05 AM UTC+2, Julian Calaby wrote: ... I'm waiting for them to run out of fruit options. just to keep this thread REALLY out of topic, the fruit race remembers me my early days (80ies..) of computing when my father bought me and my brother a not so cheap Apple //e (beware the precise syntax.. not an older Apple ][ :-) but there were already at the time, the china clones (at the time the 6502 based Apple was more or less an open design..) with resembling names like PearPc or Lemon and Orange.. (as far as i remember..) Not only China, but Europe and South America too. http://en.wikipedia.org/wiki/Apple_II_series#Clones Somehow, this discussion about history repeating is more interesting and ontopic than the spammail it is based on :) 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] Empty bootinfo dram layout parameters.
Hi Siarhei, As the resident sunxi dram controller expert, what do you make of this: [dram_para] dram_baseaddr = 0x4000 dram_clk = 408 dram_type = 3 dram_rank_num = -1 dram_chip_density = -1 dram_io_width = -1 dram_bus_width = -1 dram_cas = 9 dram_zq = 0x7f dram_odt_en = 0 dram_size = -1 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_tpr4 = 0x1 dram_tpr5 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 This is for the horribly incomplete http://linux-sunxi.org/Inet_k70e which has an A20, from the image which sandpox posted. The script.bin has the exact same info which bootinfo retrieves from BOOT0. I do not think i have seen such results before and i wonder where this information could otherwise be coming from. Perhaps any of the people in CC could finally fully run through the new device howto and post the output of meminfo (next to completing the rest of that page). 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: [ANNOUNCE] Allwinner releasing CedarX open source
On Wed, May 20, 2015 at 12:05:53AM -0700, Andrea Venturi wrote: Hi Kevin, as a casual tinkerer of Allwinner (AW) SOCs, let me tell you i appreciate A LOT AW attitude and commitment for becoming more and more a proper citizen in the free software and open source community. This release is a step in a continuous process BUT is surely a step in the right direction. THANX! i really think AW, since the last few years, has been doing a breakthrough revolution in the so called internet of things (IoT) space.. not really because there are new features implemented in its SOCs but because AW is packing SO MUCH stuff in a cost effective chip that's enabling the next level of pervasive computing. you are permitting a world of programmable toys that can be effectively used and enable new products; i started playing with A10 some years ago with Tom Cubie's Cubieboard, but i'll cite also Olimex open source boards and Luke Leighton's EOMA86 effort as very interesting developments born thanx to your business proposition; now we are seeing the new H3 sold for 25$ as dev card, Orange PI mini 2, and the next to come Kickstarter campaign for a $9 board named CHIP.. it a staggering progression.. so the SOC is surely beefy, but for it to become cornerstone of new projects for advised people like the ones embodied in the linux-sunxi community, it has to be dependable i.e. you want it to be available and controllable for ever as software development progresses (and as we can see in the open source model, the snowball becomes avalanche pretty fast). that's why full disclosure and datasheets are more preferred than code drops as the latter is just a single representation (in the writer mindset and in the writer context) of a use case, the former gives everyone the freedom to do its own evaluation and choice and development/integration. coming to Cedarx, i for first believe everything now is going in the right direction toward full disclosure, and that's a GOOD THING. i suppose this is happening because the HW core is more or less exclusive of Allwinner chips. a really different issue is around the 2D/3D MALI 400MP core that's the last unknown big black box of the actual AW bulk lineup (i'll keep the PowerVR stuff out of my way with a 10 feet pole.. :-) i understand that, as it's a graphic core used in many competitors chips too, it's difficult for any chip house to step in and make a liberal move, surely it's a CORE out of chipmaker control as it's ARM own, then there's also the ARM attitude toward open community (well explained by libv mails) that's not helping too, here. it's something that surely has to be dealt in the future someway; anyway i would really appreciate a public statement from AW official on the matter (AW as a pretty huge ARM customer could make the difference here and get back some good PR recognition on this issue..) Supposed open source shops like Linaro, Jolla and Mozilla are not going there. Everyone is afraid of the big bad GPU providing troll in the corner. So i have little hope that a small fry like Allwinner, who until recently was happy to hide behind the chinese wall with respect to copyright violations, would invest any significant business and or political weight into pushing that troll into the right direction. at the end of the day, I understand AW (as all chipmakers) is living a hard time, having to be competitive EVERY day in this chip business (where the bulk of sales and revenues is on products like low cost Android tablets where end users are not interested into this kind of IP issues and development models..) so it struggles to find the right balance in the mix between hiding the secret sauce of the kitchen and sharing info with community who boosts development. let me tell i believe anyway AW would deserve at least the same public recognition that's going toward Raspi/Broadcom because they are key enablers of the open makers ecosystem and this could be a powerful business game changer in the longer term IMHO. so hat tip to Allwinner and keep up this good work with the growingly open attitude you are showing toward us, the people, your final customers in the end.. Yes, and no. Here it is a very obvious legal matter. Allwinner has no choice but to do this after (L)GPLed code has been discovered, or for kernel or uboot code. It would have been nice if we wouldn't have had to revert to the route of massive marketing damage to convince Allwinner to meet its legal obligations. Let's just hope that this course of action will now no longer be needed, and that Allwinner simply delivers upon its obligations, and perhaps exceeds them, as they only stand to gain from that. 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
Re: [linux-sunxi] Re: iNet K70E board
On Thu, May 21, 2015 at 03:00:14AM -0700, sand...@outlook.com wrote:
On Wednesday, January 22, 2014 at 10:52:27 PM UTC+7, Luc Verhaegen wrote:
On Wed, Jan 22, 2014 at 10:40:49AM -0500, ferar achkar wrote:
greetings Luc,
I am trying to build a boot-able SD card i.e.
*u-boot-sunxi-with-spl.bin* based on u-boot-sunxi source tree, for an
INET-K70E board that has currently a working android, I have generated
*u-boot-sunxi-with-spl.bin *based on your INet_K70HC board cfg, but it
did not boot, can you please advise on how you populated struct
dram_para in 'board/sunxi/dram_inet_k70hc.c' file:
static struct dram_para dram_para = { /// for INet_K70HC board as
authored by Luc Verhaegen l...@skynet.be 2014-01-02 06:37:24
.clock = 384,
.type = 3,
.rank_num = 1,
.density = 4096,
.io_width = 16,
.bus_width = 32,
.cas = 9,
.zq = 0x12331a7f,
.odt_en = 0,
.size = 1024,
.tpr0 = 0x42d899b7,
.tpr1 = 0xa090,
.tpr2 = 0x22a00,
.tpr3 = 0,
.tpr4 = 1,
.tpr5 = 0,
.emr1 = 0x4,
.emr2 = 0x10,
.emr3 = 0,
};
since the i have used the same script.bin currently on the nand flash, i
am not sure, but i think the dram_para values for INet_K70HC are not
correct for the INET-K70E board (below is a snapshot of the board).
much appreciated,
ferar
Do not send emails to people directly, especially when they are general
sunxi questions. Use the mailing list.
it did not boot could be a great many things. Attach serial and find
out.
The image attached shows only a tiny part of the board. So it usually
would not be very useful to begin with.
But... Even with this small part of the board visible, it is clear that
this is a completely different board from the k70hc. Please work through
the http://linux-sunxi.org/New_Device_howto meticulously before you do
anything else.
Luc Verhaegen.
here: http://thuvien.bkc.vn/Tablet/Firmware/2GOOD/2Good.VenusPro.rar
Thanks. I will pull that in on the weekend and extract the necessary
info then.
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] [ANNOUNCE] Allwinner releasing CedarX open source
On Tue, May 19, 2015 at 08:44:13AM +0800, ke...@allwinnertech.com wrote: Hi All, We're proud to announce a new code release today for CedarX. Before delving into the details, I'd like to share some context: 1. As a growing company, we are doing our best to understand the needs of the open source software community. This is a learning process. We're working with different people across the Linux development community to better understand best practices. 2. Open source software development is a collaborative process. It works because people genuinely want to help others improve and be successful. Some people are new and others help them learn the ropes over time. We hope that this same positive feedback process can be applied to GPL. With that context, here's an update on our CedarX code release (we welcome constructive feedback!) 1. New code architecture. Driver has been split into several plugins, one plugin per video format. 2. GPL-complaint. We have scanned and analyzed the code to ensure that there is no GPL code used or called. 3. Partial CedarX video decoder source code release. MPEG2, MPEG4, MJPEG, and H264 drivers source code available. We hope this is helpful to everyone. If not, please let us know how we can improve. Thanks! This is a good first step, not only to try to meet some legal obligations, but also to support Allwinners customers and the sunxi community. But... The choice of exactly those codecs for a first(?) release, the fact that you underline the use of a code scanner/analyzer, and then the fact that Allwinner chose to turn this into a modular design with codecs as modules... All that seems to hint at Allwinner intending to keep upcoming modules as binaries. If this happens, not only will that be another massive marketing setback for Allwinner, but we will push the legal limits hard and force a full release of the source code of all binaries that allwinner has released so far. As said countless times before, the LGPL applies to the whole of the binaries Allwinner released before, not just those codecs where LGPLed code was used. 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] It seems that AllWinner released media codec source code
On Mon, May 18, 2015 at 02:59:41AM -0700, jacky lau wrote: At least the source code of mpeg2, mpeg4, jpeg, h.264 decode library has been released today: github.com/allwinner-zh/media-codec Well done, allwinner. Hope encode library will follow. This does not absolve Allwinner from its legal requirements. There is a lot more going on in those binaries of theirs than what they released just now. Plus, i've been told that Cedrus supports those same codecs. 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] Allwinner R8 module
On Sun, May 10, 2015 at 09:49:43PM -0400, jonsm...@gmail.com wrote: Does anyone have any info on the new Allwinner R8 module being used in the Chip $9 PC Kickstarter? It is A13+flash+RAM on module. I'd like to get a pin out and projected price. That module has to be really low cost if they are able to make a $9 computer out of it. *sigh* I am amazed that people still fall for what i can now only call the kickstarter trap. * only 9usd * 1y delivery time * full mainline support * linux-sunxi is not mentioned even once None of that fits together, and i am amazed that people actually fall for that still. 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] Availability of A83T boards for developers
On Fri, May 01, 2015 at 06:37:11AM +0300, Simos Xenitellis wrote: Dear All, The newer octa-core SoC from Allwinner is the A83T (octa-core ARM Cortex-A7 @ 2.0 GHz with the PowerVR SGX544MP GPU) and can be found in tablets such as the one that Jean-Luc reviewed a few months ago, http://www.cnx-software.com/2014/12/06/allwinner-a83t-tablet-unboxing-first-boot-and-benchmarks/ For the A83T, there is documentation available at https://github.com/allwinner-zh/documents/tree/master/A83T The bootloader is at https://github.com/allwinner-zh/bootloader/tree/master/basic_loader The 3.4 Linux kernel is at https://github.com/allwinner-zh/linux-3.4-sunxi/tree/A83T Very soon, a few A83T dev boards will be produced in order to be given to developers who might be interested in mainline support. As with the previous donation of boards, I'll be doing the clerical work this time as well. Send me mail in private if you are interested to receive one. I'll process the requests and forward to Allwinner so that they can send you the boards. Simos Are you playing santa clause with other peoples accomplishments or donations again? 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] Fwd: Re: [media-codec] media-codec / cedar released as LGPL, but where is the source? (#5)
On Thu, Mar 19, 2015 at 11:05:30AM +0100, Olliver Schinagl wrote:
Luc, Sunxi-community,
It looks like they replaced a few function (names only) so the symbols
don't show up with a simple grep (I cannot find ff_huff_build_tree for
example). Can anybody confirm/deny that they went over a list of a few
functions just to change the names/obfuscate things? The symbols still
show a mix and match of coding style (camelcase etc etc) which still
indicates a lot of copy/paste.
I don't even know how this all works legally, so curious on that regard too.
Anyhow, if somebody can help with some 'proof', that'd be great, though
I'm sure they just obfuscate (if i'm right about that) some more.
Olliver
Forwarded Message
Subject: Re: [media-codec] media-codec / cedar released as LGPL, but
where is the source? (#5)
Date: Thu, 19 Mar 2015 00:42:57 -0700
From: allwinner-zh notificati...@github.com
Reply-To: allwinner-zh/media-codec
reply+0013009d911e6a9cdfd4aa8b9bd4bea2b90606ffdbe5170792cf00011122400192a169ce03bfc...@reply.github.com
To: allwinner-zh/media-codec media-co...@noreply.github.com
CC: Olliver Schinagl oli...@schinagl.nl
No, there is none GPL issues in the media-codec-lib.
Please provide the evidence to me.
Yes. Jens Kuske alerted me to that a few days ago. I have done the
legwork on one of those functions, but was too busy yesterday to make a
stink about it yet.
What is shown below is next to lgpl symbols that i had identified before
and which (also) still remain, and which i will not expose to allwinner
today, as i know how they will react. What Jens told me about is
separate, and new, and therefor shows just how nasty this game of
Allwinner is.
H264FillDefaultRefList() and a lot of code around it is straight out of
the libavcodec h264 decoder. The original name for that function is
ff_h264_fill_default_ref_list() in libavcodec/h264_refs.c:
https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/h264_refs.c#L115
This is new, as some totally different code for h264 was available in
the previous versions of the cedarx binaries.
When Allwinner stated that they did CedarX2.0 about two months ago, they
added _more_ lgpled code. But this time they tried to trivially disguise
the code origins. This is a totally new low for Allwinner, and it shows
clearly that they have no licensing control over the contents of their
binary driver, and that no-one can believe them when they state that
they are adhering to licenses. No matter what binaries Allwinner
produces, nobody can believe that these are completely Allwinners
property and that Allwinner has the right to distribute such software.
Attached is the manual decompilation of H264BuildDefList() (originally
build_def_list() in h264.c). This can be compared easily by
looking at
https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/h264_refs.c#L67
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.
int
H264BuildDefList(uint8_t *arg0, uint32_t *arg1, uint32_t arg2, uint32_t arg3,
uint32_t arg4)
{
int j = 0;
int k = 0;
int i = 0;
while ((j arg2) || (k arg2)) {
while ((k arg2) (!arg1[k] || !(arg4 arg1[k][0xA4])))
k++;
while ((j arg2) (!arg1[j] ||
!((arg4 ^ 3) arg1[j][0xA4])))
j++;
if (k arg2) {
if (arg3)
arg1[k][0x10] = k;
else
arg1[k][0x10] = arg1[k][0x0C];
H264SplitFieldCopy(arg0[224 * i], arg1[k], arg4, 1);
k++;
i++;
}
if (j arg2) {
if (arg3)
arg1[j][0x10] = j;
else
arg1[j][0x10] = arg1[j][0x0C];
H264SplitFieldCopy(arg0[224 * i], arg1[j], arg4 ^ 3, 0);
j++;
i++;
}
}
return i;
}
Re: [linux-sunxi] Fwd: Re: [media-codec] media-codec / cedar released as LGPL, but where is the source? (#5)
On Thu, Mar 19, 2015 at 12:44:40PM +0100, Olliver Schinagl wrote: Hey, On 19-03-15 12:39, Luc Verhaegen wrote: On Thu, Mar 19, 2015 at 11:05:30AM +0100, Olliver Schinagl wrote: snip When Allwinner stated that they did CedarX2.0 about two months ago, they added _more_ lgpled code. But this time they tried to trivially disguise the code origins. This is a totally new low for Allwinner, and it shows clearly that they have no licensing control over the contents of their binary driver, and that no-one can believe them when they state that they are adhering to licenses. While you are 100% correct and true, I do want to say, this may not be Allwinner in general, just some lone engineer* (and maybe his direct manager) that are responsible. It very well does reflect badly on Allwinner together, as they communicate it as such to the outside world. I still have hope for Allwinner as a company. * I heard in the past, that the cedarX code was written by some engineer who didn't really care for OSS and wanted to do his thing on his little island. How much of this is true and how much of this is in the past, I don't know, just some background. I myself doubt, that a manger is pushing him to keep it closed, if anything it sounds like it would be the reverse. This all being just my view and opinion of the case however. Olliver Still. Allwinner could not be in a worse position with their CedarX driver. I think the time for letting Allwinner bullshit us and stall us is over completely now. 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] Some info on Google Summer of Code (GSoC) 2015 and linux-sunxi
On Mon, Mar 16, 2015 at 02:59:07PM +0200, Simos Xenitellis wrote: Hi All, Here are some details for those that may be interested in taking part in Google Summer of Code (GSoC) 2015 or one in a subsequent year. Here is the page for GSoC 2015, https://www.google-melange.com/gsoc/homepage/google/gsoc2015 Here is the page with the timeline (deadlines), https://www.google-melange.com/gsoc/events/google/gsoc2015 GSoC is a project by Google that runs every year since about ten years ago, and provides financial support for work on open-source projects. It requires different open-source projects to apply as organizations so that they can then accept students to work for them (the open-source projects) over a period of three months during the summer. The students get US$5500 and the mentor from the organization gets US$500. A prospective student needs to be a university student (tertiary education in general). There is no limitation as to what cource they are studying. They need to show proof that they are University students in around May. Last year, Emilio applied for GSoC through the organization Linux Foundation and had Maxime as his mentor, http://linux-sunxi.narkive.com/VYmpmy4Q/improve-allwinner-socs-support-on-mainline-linux Sadly, this year the Linux Foundation was not accepted as an organization, http://www.linuxfoundation.org/collaborate/workgroups/gsoc/google-summer-code-2015 In addition, Linaro, which also took part in GSoC 2014, was not accepted this year. This makes it a bit more difficult to find a suitable host organization for linux-sunxi. The list of the 2015 organizations is at https://www.google-melange.com/gsoc/org/list/public/google/gsoc2015 One option could be X.Org Foundation for graphics-related tasks. X.Org was accepted for 2015. Their list of project ideas is at http://www.x.org/wiki/SummerOfCodeIdeas/ They mention relevant projects such as accelerated video decoding for some NVidia SoCs (Maxwell Accelerated Video Decoding), so it might be viable to add something even for CedarX. For this to work, it requires: 1. one or more students to volunteer to undertake such relevant projects. 2. a mentor to volunteer to oversee the work. 3. communication with the X.Org Foundation to accept the project in their allocation of funded projects The hard deadline for students to apply is Friday, 27th March 2015. Simos Yet another instance of you trying to play santa with other peoples work? Have you even talked to the Xorg board members who are working on this? Let me ping my friend mupuf and find out. 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] Open source CedarX driver
On Sun, Mar 08, 2015 at 02:34:54AM +0200, Simos Xenitellis wrote: On Sun, Mar 8, 2015 at 12:32 AM, Henrik Nordström hen...@henriknordstrom.net wrote: fre 2015-03-06 klockan 18:28 +0800 skrev Quink: cedarx2.0 is a refactoring of cedarx1.0. The job is finished about just three month ago and not used by most vendors yet. Some work is still needed to port cedarx2.0 to linux. The directory of cedarx2.0 in Android SDK is frameworks/av/media/liballwinner. The directory of cedarx1.0 in Android SDK is frameworks/av/media/CedarX-Projects. Most part of cedarx2.0 is open source. It's not the same situation compared with cedarx1.0. Maybe it is not a big step and not enough, it is a right direction. The latest cedarx code released by Allwinner is still non-GPL in the important parts, and no indications that this will change any time soon. Yes they have released much of the glue layers with GPL license, but the actual video encoding/decoding parts is till in a binary library which is incompatible with the GPL license terms. As an interim solution for the repo at https://github.com/allwinner-zh/media-codec (with the aim to keep the glue code as LGPL while the .so libraries as closed-source), would it make sense to split the repository into two parts? That is, have a https://github.com/allwinner-zh/media-codec-lib repository that will contain the two .so closed-source libraries. Then, the https://github.com/allwinner-zh/media-codec repository will include the media-codec-lib as a 'git submodule'. Simos Even if people ignore the terms of the LGPL, like you clearly do, there are still LGPLed symbols present in that binary. I suggest that you start by reading up on the GPL and LGPL licenses. 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: What open source community is this?
On Mon, Mar 16, 2015 at 04:56:10PM +0100, Irgendeiner wrote: Am 15.03.2015, 17:16 Uhr, schrieb Luc Verhaegen l...@skynet.be: On Sun, Mar 15, 2015 at 06:12:10PM +0200, Simos Xenitellis wrote: On Sun, Mar 15, 2015 at 5:56 PM, Luc Verhaegen l...@skynet.be wrote: On Sun, Mar 15, 2015 at 11:51:03PM +0800, Quink wrote: ... Luc Verhaegen. Luc, please, start your own thread. What you are doing is hijacking. Simos I will continue the original thread later on, Mr. Pot. Luc Verhaegen. With all due respect for your contributions, may I suggest that you stop blaming people and ranting? I further suggest that your anger about various violations of the GPL by Allwiner is strictly limited to the appropriate thread Allwinner GPL violations: definitive proof. Thank you! I.Irgendeiner If you at all wish to be taken serious, try using your real name. 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] Open source CedarX driver
On Mon, Mar 16, 2015 at 03:16:47PM +, Simon Kenyon wrote: On 03/16/15 14:52, Luc Verhaegen wrote: Even if people ignore the terms of the LGPL, like you clearly do, there are still LGPLed symbols present in that binary. I suggest that you start by reading up on the GPL and LGPL licenses. Luc Verhaegen. i think he already has: https://github.com/simos/keyboardlayouteditor/blob/master/COPYING His statements suggest that he just pro-forma copied that. 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: Formal request for source code for LGPL licensed software.
On Fri, Mar 13, 2015 at 12:13:42PM +0800, ke...@allwinnertech.com wrote: Hi, Luc, Thanks for your suggestion. We have update the Cedarx. What we have done is as follows: 1. Update the License text, the media-codec is fully following LGPL; But it is not, it depends on a strange binary still. 2. Splite the binary to submodule media-codec-lib; BTW, the binary is just video engine driver implement in user mode, All code is wrote by Allwinner, based on Allwinner's video engine hardware, no third part used; Wrong. Even the latest binary has code that originated from FFMpeg/libavcodec. It seems that Allwinner has absolutely no control or insight in what code came from where with Cedar. 3. Fix some issue of the code; Oh? Which? With these actions, is there any license issue yet? Yes. First off, LGPLed symbols and code remains. I have manually decompiled the disassembly of one of the functions, and for this function there is absolutely no doubt that the code originated from FFMpeg/libavcodec, and that code was always LGPLed. I will not disclose which symbols and code these are at this point, as that will only trigger Allwinner to rename/restructure this code, and then Allwinner will subsequently (falsely) claim to adhere to the licenses. It is however rocksolid proof that will survive even the harshest legal scrutiny. Secondly, removing or hiding LGPLed code does not change the fact that the LGPL license once applied to the full source tree (and still does). It also does not change the fact that hundreds of thousands of devices out there are shipping with LGPL licensed cedar binaries. Allwinner is still legally bound to release their whole source code for each and every version Allwinner distributed to any party, when requested by that party. Please help to give a check, if any suggestion, please let me know. We will try to fix it ASAP. Thanks! None of the current actions; namely splitting out of the binary into another repository, removing vp6 support and attached code, absolves Allwinner in any way. At best, it shows that Allwinner does not understand or does not want to understand the terms of the (L)GPL. It is now also extensively proven that Allwinner has no control over the contents of the Cedar binaries. Allwinners Cedar binaries are tainted in many many different ways and this wholly illegal software cannot be distributed and should never have been distributed. 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: What open source community is this?
On Sun, Mar 15, 2015 at 06:12:10PM +0200, Simos Xenitellis wrote: On Sun, Mar 15, 2015 at 5:56 PM, Luc Verhaegen l...@skynet.be wrote: On Sun, Mar 15, 2015 at 11:51:03PM +0800, Quink wrote: ... Luc Verhaegen. Luc, please, start your own thread. What you are doing is hijacking. Simos I will continue the original thread later on, Mr. Pot. 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: What open source community is this?
On Sun, Mar 15, 2015 at 11:51:03PM +0800, Quink wrote: Sorry Simos, I just want to invite some students in local community to join sunxi and take part in GSOC. That email has nothing to do with the CedarX. It's so sad that there are so many misunderstand. If we have more tolerant attitudes, technical discussing should not become a flashpoint, and we can be more open too. I just found some lgpled symbols in your supposed clean binaries. I will now spend the time to irrefutably prove that Allwinner CedarX binaries are a cesspool of license violations that Allwinner has had no and still has no control over. So much for more tolerant attitudes and misunderstandings. Allwinner has absolutely no credibility left in this story. 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] Derailed thread
On Wed, Mar 11, 2015 at 06:29:50PM +0100, Luc Verhaegen wrote: The only workable solution for Allwinner now is full support of the cedrus REing project, and using the code that comes from that, across the board. As was suggested on August 23rd last year, when i publically exposed the (L)GPL violation while also reaching out to allwinner in private conversation, about the much more volatile libvp62 illegal code. Nobody believes allwinner any more at this point. 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: OFFTOPIC: Re: [linux-sunxi] Derailed thread
On Thu, Mar 12, 2015 at 11:25:19AM +0200, Simos Xenitellis wrote: On Wed, Mar 11, 2015 at 3:48 PM, Benjamin Henrion zoo...@gmail.com wrote: On Wed, Mar 11, 2015 at 12:34 PM, Simos Xenitellis simos.li...@googlemail.com wrote: On Wed, Mar 11, 2015 at 9:39 AM, Benjamin Henrion zoo...@gmail.com wrote: On Tuesday, March 10, 2015, Quink wantl...@gmail.com wrote: I have communicated with the author of source code of libvdecoder.so. The code has been rewrote completely, has no relationship with FFmpeg, I don't think it would resist a binary analysis. Doesn't pass the code of conduct (for example, http://www.ubuntu.com/about/about-ubuntu/conduct). I don't see how I am violating any code of conduct here, quite the contrary. The issue is that you *insinuate* that the claim (no relationship with FFmpeg) is false. What would be the next step to such a discussion? The one side claims no, the other yes, ad infinitum. For this to go forward, you or someone else needs to do this binary analysis. Once the binary analysis is done and you have something to show, you can reply with your data. In that way, such a discussion could potentially move forward. I have done a full symbol analysis of libvecore as shipped on the cubieboard back in august. It clearly shows ffmpeg and libavcodec vs libvp62 and other questionable code whose origins are not clear. It's a txt file, but i should still toss it onto the wiki. I have done a brief nm of the newly LGPLed binary to find libavcodec and libvp62 symbols. I will happily spend a few hours and take that new library apart as i did the older one. I stated that i would do so last week, but i of course have not gotten to that yet. Having an allwinner employee state that that violating code has all been removed now, in this last... Week? That is just not credible. After legal advice has been acquired, i will be happy to do the binary analysis, accounting for every hour, and Allwinner will then end up paying for my time. I can then get the cedrus guys a wide range of hw, and stick some cash in our linux-sunxi infrastructure. Everyone wins. Except allwinner. In terms of code of conduct documents, the idea is, when replying, to move a discussion forward. If a thread veers off, then change the Subject:, thus start a new thread. If you find any evidence of common binary code, you can present it respectfully and still it is going to be strong evidence (i.e. I did arm-linux-gnueabihf-objdump -d libvdecoder.so and the same to that other lib, and function xyz matches as shown here and here). Again, if anyone who states anything that is supporting established and proven open source licenses, licenses which allwinner has been proven, without a doubt, to breach, you want to see them removed or at least silenced. How many people will be left in that ideal linux-sunxi community of yours, and how many of them will be able to usefully contribute code, documentation, or user help in your dystopia? 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: OFFTOPIC: Re: [linux-sunxi] Derailed thread
On Wed, Mar 11, 2015 at 01:34:18PM +0200, Simos Xenitellis wrote: On Wed, Mar 11, 2015 at 9:39 AM, Benjamin Henrion zoo...@gmail.com wrote: On Tuesday, March 10, 2015, Quink wantl...@gmail.com wrote: I have communicated with the author of source code of libvdecoder.so. The code has been rewrote completely, has no relationship with FFmpeg, I don't think it would resist a binary analysis. Doesn't pass the code of conduct (for example, http://www.ubuntu.com/about/about-ubuntu/conduct). Simos Am i reading this right? Do you now wish to see Ben removed from the linux-sunxi community as well? So basically, everyone who wants established and proven open source licenses honoured, you would like to see them removed from linux-sunxi? Good luck with that. 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] Derailed thread
On Wed, Mar 11, 2015 at 12:32:25AM +0800, Quink wrote: I have communicated with the author of source code of libvdecoder.so. The code has been rewrote completely, has no relationship with FFmpeg, except some function names. This is a silly mistake, but maybe it's true. Does anybody know how to prove that? We've proven extensively that Allwinner breached not only ffmpeg/libavcodec licensing, it also used illegal code, and given that wide a span of very foul license violations, nobody can trust allwinner any more when it claims that it now has clean hands. Allwinner should not be asking linux-sunxi.org for advice on how to prove that their hands are clean today. They should have a small army of lawyers at the ready this point. These lawyers should be well versed in international copyright and IP matters, and also have a good grasp of the english language. If the LGPL violations of libvdecoder.so can be cleaned up, how can we use the shared library on open source sunxi kernel, and even mainline kernel? I don't what's the low level part in the kernel that libvdecoder.so depends on, a thin VPU driver and some special memory management modules? If those parts can be solved, does the cedar + openmax + gstreamor openmax plugin workable? The only workable solution for Allwinner now is full support of the cedrus REing project, and using the code that comes from that, across the board. Any solution which has allwinner using any binary is now suspicious and allwinner will not be able to satisfactorilly prove the origins of such code or the fact that no licenses or other things are breached this time round. Plus, some well known REers probably need to go waste a lot of time on said binaries, and this time will in the end be billed to Allwinner. So Allwinner should give up on any strategy that involves binaries. Now. And have some chance of seeing this resolved amicably. 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: Reviewing the book Getting Started with Cubieboard (Packt Publishing Ltd)
On Tue, Mar 10, 2015 at 09:41:14AM +0200, Simos Xenitellis wrote: On Wed, Mar 4, 2015 at 11:43 AM, Simos Xenitellis simos.li...@googlemail.com wrote: Hi All, As you may know, there is an introductory book about the A-Series of Allwinner SoCs (specifically A10, A13 and A20), called Getting Started with Cubieboard, written by Olliver Schinagl and published by Packt Publishing Ltd. Read more at https://www.packtpub.com/hardware-and-creative/getting-started-cubieboard Packt is doing some publicity for this book. What they are doing is that they give the e-book version of the book in exchange for an online review. The idea is that by having several online reviews for the book, it helps prospective buyers to decide whether to buy or not. Obviously, you are free to write whatever you want in the review. I offered them my help in finding such reviewers, and they are looking for 3 persons. Here are the details: 1. Have a look at https://www.packtpub.com/hardware-and-creative/getting-started-cubieboard to decide if you are interested to go through this. 2. Write a review on Amazon, Google Books and goodreads. For Amazon, you need to have an account and have bought something in order to be able to post reviews. 3. Write a review on your personal blog or similar social media. If you are interested in taking part, please send me a private email. Please also add a sentence describing why it would be helpful to you to get a copy (to be used in case there are more than 3 replies). I'll collect replies until this Friday. If there are any general questions, reply here. I have no affiliation with Packt Publishing Ltd. I got some good replies and forwarded them to Packt. They confirmed that they will be contacting you (if they did not do already) with further details. I also suggested to Packt to get someone from either CubieTech or Allwinner to review the book. Obviously, such a thing would be mutually beneficial in terms of marketing. So, if you are from CubieTech or Allwinner, do contact me in private. Simos Did you involve the author of the book in this action, at all? 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] Derailed thread
On Tue, Mar 10, 2015 at 01:38:30PM +, Manuel Braga wrote: Hi, That was a joke mail, in response to the joke that allwinner gave us when allwinner added the LGPL license to source code that includes a binary accused of being in noncompliance. This was not a joke email. Its contents was very serious, and it should be interpreted as such. Allwinner needs/needed to know what it had just done, and that it has to fullfill its obligations. The fact that I did so, _after_ the facts had been often and openly discussed, and after allwinner had been explained their obligations countless times, does make it less than serious. The contents however is nothing to be laughed about. try to get the support of something like the SFC so that they can evaluate the merits of pursuing. And then the SFC would do the talking. I heared (but don't have the details), and this looks to be true. SFC or someone from SFC is aware of this issue. But maybe others can make this more clear. But nobody is here to sue, (why do i have to keep saying this) i think i can speak for all and say that we want to resolve this in a friendly way, but for that, there most be dialog between parties. Not excuse to ignore the issues. And Simos look at the news, with SFC and vmware, look at the time it took and no result. People tried talking to VMWare for 7-8 years. We have been trying to talk to Allwinner at least since 2012 (i am sure that LKCL would be happy to divulge his conversations with allwinner if it comes to legal action). Allwinners case is pretty open and shut, especially since they actively use both the kernel and uboot, and the symbols in cedar are clearly visible. And unlike VMWare Allwinner has its _whole_ business to lose. When there is any legal action, it could be a lot swifter. Perhaps Allwinner should act quickly and do so in an all encompassing way. If not, it stands to lose quite a lot. 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] 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.
Re: [linux-sunxi] Allwinner GPL violations: definitive proof.
On Wed, Mar 04, 2015 at 04:55:57PM +0100, Irgendeiner wrote: Am 04.03.2015, 12:57 Uhr, schrieb Luc Verhaegen l...@skynet.be: 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. Luc Verhaegen. Luc, of course it is your personal decision to organize a shitstorm when you believe that it results in compliance, but I have many doubts about that. However, I would hope that you organize it without referring to the sunxi project and list, because imho the project would be more harmed than helped! This is not a new issue, far from it. This has been going on for years and what you see now is the culmination of years of asking nicely and either being ignored or getting fed bullshit excuses. 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] Allwinner GPL violations: definitive proof.
On Wed, Feb 25, 2015 at 04:55:15AM +0100, Luc Verhaegen wrote: This was just posted on the allwinner github account: https://github.com/allwinner-zh/media-codec This contains: https://github.com/allwinner-zh/media-codec/blob/master/sunxi-cedarx/LIBRARY/CODEC/VIDEO/DECODER/libvdecoder.so This binary contains symbols from both ffmpeg (LGPL, but altered/hacked up) and libVP62 (anti-compiled from java, and taken off the web in 2006). The LGPL forces Allwinner to produce the full and complete source code of these binaries. How they are going to explain libVP62 to On2 Technologies, now google, is beyond me (cfr. http://en.wikipedia.org/wiki/VP6) With all the previous indiscretions, it was always possible to claim that there was some chance that Allwinner was not the source of the many violations. It was always pretty clear that Allwinner was the source, there were just too many coincidences, the violation was too all encompassing, and not a single device maker spilled the goods. The fact that they threw out a kernel tree with most code and all binaries removed, was, despite being a ludicrous and laughable action, another very clear sign that Allwinner was indeed the source of these violations. Now however, the fact that allwinner posted this very clearly shows that Allwinner is the source. It is absolutely unequivocal this time round. To top this off, it is 6 months after the last GPL violation shitstorm. This puts serious doubts behind the claims that Allwinner truly is learning and willing to cooperate. Allwinner, it is very high time to start playing nice. You've been at it for 4 years now and seem utterly incapable of or unwilling to change. Luc Verhaegen. 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. 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] Allwinner GPL violations: definitive proof.
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. 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 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. 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] [New Device] Giada Q11 Mini
On Wed, Feb 04, 2015 at 05:41:22AM -0800, alatnet wrote: Pictures of it can be found here: http://www.techpowerup.com/reviews/Giada/Q11/4.html Com port on left side does not output anything. Port in front of sata connector might be a usb connection but unknown. Multimeter shows that 1st port on left when viewing from front outputs 4.76V on 20 Vdc settings. 4th port from left pulls a 20k Ohms setting to 0. USB 3.0 port on the right side is USB OTG connection. Using a USB A to USB A connection and pressing the far back button on the left side sets it to FEL Mode. Firmware that is flashable to the device in FEL Mode: http://download.giadatech.com.cn/driver/jt/Q11_v18_4.0.4_20130226_P008.rar Booting off of SD Card slot works. Was able to boot an MK802 Linux firmware without issues. Processor is an Allwinner A10. Yes I am a noob with this stuff. If anyone needs any more info, i'll be glad to provide it. I'll see about extracting the files from /boot and the MBR and adding it to this thread. http://linux-sunxi.org/New_Device_howto 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: Allwinner GPL violations: definitive proof.
On Wed, Feb 25, 2015 at 02:06:59PM +0800, ke...@allwinnertech.com wrote: Hi, Luc, Allwinner is trying to fix the GPL issue taken on Cedarx. It's been 4 years since your violations started. You have been told often enough. At least from 2012 onwards Allwinner has been very aware of the legal status of the software its business fully depends on. You were even given a nice consistent list of issues back in August, and in the 6 months that passed since then you have not fixed a single thing. We have release the latest version of cedarx with LGPL. No, you have not. And just close the code of Video Engine hardware, the framework and API is opensource. This is where you violate at least the ffmpeg LGPL license and breach on2 technologies (now google) copyright with the libVP62 symbols in there. I have been very clear and consistent about this, yet you still either fail to or are unwilling to understand. We will review the code again, to fix the GPL issues still existed. We are trying to do better, if you found any GPL issue, please let us know, we will fix it and update it ASAP. I have been pointing these out since at least august, quite concisely and very understandably. And all allwinner ever does is come with excuses and nonsense code or binary releases which just continue the violations. About the kernel GPL issue, we are fixing it now, we will update the code to open some drivers. Not some. ALL. As required by the GPL. Truly unbelievable and absolutely ludicrous. 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] Allwinner GPL violations: definitive proof.
This was just posted on the allwinner github account: https://github.com/allwinner-zh/media-codec This contains: https://github.com/allwinner-zh/media-codec/blob/master/sunxi-cedarx/LIBRARY/CODEC/VIDEO/DECODER/libvdecoder.so This binary contains symbols from both ffmpeg (LGPL, but altered/hacked up) and libVP62 (anti-compiled from java, and taken off the web in 2006). The LGPL forces Allwinner to produce the full and complete source code of these binaries. How they are going to explain libVP62 to On2 Technologies, now google, is beyond me (cfr. http://en.wikipedia.org/wiki/VP6) With all the previous indiscretions, it was always possible to claim that there was some chance that Allwinner was not the source of the many violations. It was always pretty clear that Allwinner was the source, there were just too many coincidences, the violation was too all encompassing, and not a single device maker spilled the goods. The fact that they threw out a kernel tree with most code and all binaries removed, was, despite being a ludicrous and laughable action, another very clear sign that Allwinner was indeed the source of these violations. Now however, the fact that allwinner posted this very clearly shows that Allwinner is the source. It is absolutely unequivocal this time round. To top this off, it is 6 months after the last GPL violation shitstorm. This puts serious doubts behind the claims that Allwinner truly is learning and willing to cooperate. Allwinner, it is very high time to start playing nice. You've been at it for 4 years now and seem utterly incapable of or unwilling to change. 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: Communication with Allwinner
On Tue, Feb 17, 2015 at 02:21:28PM +0100, David Lanzendörfer wrote: Hi It makes business sense to be open and I think it is healthy to align with the FSF goals because it's also good for business. The field of SoC manufacturers gets somewhat saturated, and those that will get open first, will probably capture the market. I'm totally about free and open source software, I'm just not about Stallman and the FSF dictatorship about the definition of what exactly is free and what unfree. (see the public argument between him and me which was on youtube a while ago) Rest assured Allwinner is highly interested into mainlining as much of the drivers as possible since they think as well that mainlining the drivers will spare a lot of additional development efforts in the future. Also our goal is to move more towards being a community friendly manufacturer so we build an open sourced platform of which everyone can reuse design for his own projects. Hopefully that doesn't sound too assholish from me, but I had a lot of trouble with some of the people (Stallman and Luke) already which were mentioned in the last few emails... That's amazing. It's like these last three years just melted away now. Oh wait. I do not know what grass you smoke or what fun events happened when you visited allwinner, but all i see you do now is grandstanding about how things will be soo great in future. All you do is talk, talk, talk, and i see no actions. And now you even are going down the route of eroding away at Allwinners legal requirements, especially those which cost time and money to fix, two things Allwinner clearly still is not willing to invest. On top of that, you have started to badmouth people who have actually done stuff in their lifetimes. What gives you that right? And what's next on this path? Why don't you just shut up, completely, until you actually have something worth talking about. Say, after you produced code and/or datasheets. 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] Communication with Allwinner
On Tue, Feb 17, 2015 at 03:46:34PM +0100, Koen Kooi wrote: How's that DRM driver doing, any code yet? At some point. But at least i am not the one whining about it all the time. I will make noise when it's there. 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: Announcing easy Linux installation on Allwinner devices for non-geek users
console could be configured correctly according to some heuristic rules. However later it turned out that the heuristics does not really work on some A13 devices and they may have mutually incompatible UART configurations: https://www.mail-archive.com/linux-sunxi@googlegroups.com/msg07057.html This particular problem just confirms the general rule about relying only on what is also used by BROM. Oh, and some functionality is also provided by dedicated SoC pins, which are strictly used only for a single purpose and can't be re-configured for doing anything else. This can be safely used too. Anyway, the really missing part was the user friendly output and user friendly input for generic u-boot binaries. HDMI is widely used in Allwinner hardware and it supports autoconfiguration. USB host ports use dedicated pins and only enabling/disabling power can be device specific. The missing USB power can be solved by using a powered USB hub, which is not very convenient, but still a workable solution. After the initial discussion and planning on the IRC, Luc Verhaegen stepped in to implement the video driver for u-boot, together with simplefb support for the linux kernel: http://lists.denx.de/pipermail/u-boot/2014-August/185193.html And Roman Byshko stepped in to implement the USB EHCI support: http://lists.denx.de/pipermail/u-boot/2014-July/183349.html Many thanks to them for spearheading the development of these important features! And of course, Hans de Goede did a great job bugfixing and further improving this code, probably investing even more efforts than the initial contributors. Not to mention the participation in lengthy simplefb political battles, which looked really scary and discouraging, but ended up well. With all these features in place, now we can do something like this: https://github.com/ssvb/sunxi-bootsetup/releases/tag/20141215-sunxi-bootsetup-prototype It is a demo of a universal SD card image, which should be bootable on any Allwinner A10/A10s/A20 device. With an installer of u-boot v2015.01-rc3 as the initial demo simple payload. By using a HDMI monitor for output and a USB keyboard or FEL button for input, it offers a menu based user interface. The menu allows to select the exact type of the user's Allwinner device and install the right bootloader for it. In principle, even now it is usable as a base for the SD card distro image. Maybe with http://www.berryterminal.com/doku.php/berryboot chained as the next installation stage. There is of course a huge room for improvements, which are yet to be done. Some of the potential improvements are listed below. = == 3. Relocatable SD card = Maybe not every user really needs a full-fledged bootloader, so a basic device independent bootloader with just SD card support and HDMI can be probably used not only for the initial setup of the hardware type, but kept indefinitely for booting the linux kernel too. Naturally, in order to get good performance, the DRAM parameters need to be patched into the SPL, replacing the generic failsafe ones. The DRAM parameters can (and should) be tied to the unique chip ID: http://linux-sunxi.org/SID_Register_Guide So that if anyone tries to move the SD card to a different Allwinner device, this situation can be detected and the menu with the device type selection can be shown again on the HDMI monitor instead of failing in a non-obvious way. Storing SID values and DRAM settings for more than one device is also an option, so repeatedly swapping between two devices will trigger the device type selection menu activation only once for each device. = == 4. NAND = NAND is the hardware, which is supported by BROM. Which means that it should be usable in a generic way by the universal device independent u-boot binary. NAND is a perfect place to store the device specific information. So that the user can avoid the annoying device type selection choices. = == 5. Support more devices! = The number of supported Allwinner devices in u-boot v2015.01 is really small. A few more devices are being added for v2015.04 While the progress is steady, I'm not convinced that the support for all the 100+ Allwinner devices can be added in a reasonable time frame. The owners of some these devices are non-geeks and will not be able to submit patches to u-boot and the linux kernel on their own, even if provided with detailed instructions. This process just does not scale. Moreover, it is not very nice to force the users
Re: [linux-sunxi] Re: Allwinner documentation (hardware datasheet, user manual) for A10, A10s, A13, A20, A31, A31s
On Sun, Jan 18, 2015 at 10:59:56AM +0200, Simos Xenitellis wrote: Hi All, Sugar (shuge) posted a few updated documents on https://github.com/allwinner-zh/documents so in case you are not watching that repository, here is the summary. You can use diffpdf (sudo apt-get install diffpdf) to compare between the versions. diffpdf gives a lot of false positives as it does a page to page comparison. Another tool to compare PDFs is https://www.inetsoftware.de/products/pdf-content-comparer which comes with a 30-day trial (no restrictions). Written in Java. On Sat, Sep 27, 2014 at 4:26 PM, Simos Xenitellis simos.li...@googlemail.com wrote: Hi All, ... Hardware datasheets A10: version 1.70 (previously known version 1.21) A10s: version 1.40 (previously known version 1.20) A13: version 1.30 (previously known version 1.12) A20: version 1.40 (none) Updated version 1.41. The changes are 1. page 20, at the table Port PB3 / Multi4: changed from - to OWA-MCLK Port PB12 / Multi4: changed from - to OWA-DI Port PB13 / Multi4: changed from - to OWA-DO A31: version 1.40 (previously known version 1.00) A31s: version 1.40 (previously known version 1.30) User manual A10: version 1.50 (previously known version 1.20) A10s: version 1.30 (none) A13: version 1.30 (previously known version 1.20) A20: version 1.20 (previously known version 1.00) Updated to version 1.3. The changelog says: Add SD/MMC and OWA register description. OWA is One-Wire Audio. A31: version 1.20 (previously known version 1.10) A31s: version 1.10 (previously known version 1.00) ADDITIONS: A33: datasheet and user guide, both at version 1.1. (released 5 days ago) A80: datasheet and user guide, both at version 1.1. (released 2 months ago). Finally, at the https://github.com/allwinner-zh/bootloader repository, code for u-boot has been released by Sugar (two days ago). Simos The reason for this release new is this: http://electronics360.globalspec.com/article/4895/allwinner-accused-of-breaking-linux-license-rules http://electronics360.globalspec.com/article/4899/allwinner-to-address-linux-open-source-issues Triggered from a linkedin discussion in the arm based group on linkedin. 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: Allwinner documentation (hardware datasheet, user manual) for A10, A10s, A13, A20, A31, A31s
On Sun, Jan 18, 2015 at 07:33:42PM +, Ian Campbell wrote: On Sun, 2015-01-18 at 11:46 +0100, Luc Verhaegen wrote: ADDITIONS: A33: datasheet and user guide, both at version 1.1. (released 5 days ago) A80: datasheet and user guide, both at version 1.1. (released 2 months ago). Finally, at the https://github.com/allwinner-zh/bootloader repository, code for u-boot has been released by Sugar (two days ago). The reason for this release new is this: Or, more likely, because someone emailed Sugar privately (I was on CC) late last week and asked for a bunch of this stuff to be made available, so it was. Thanks Sugar! Ian. Ah, just like with the kernel tree: https://github.com/allwinner-zh/bootloader/blob/master/u-boot-2011.09/arch/arm/cpu/armv7/sun9iw1/dram/Makefile 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] [PATCH] Mainline U-boot -- Tristan Auron Planet 1 tablet
On Sat, Jan 10, 2015 at 05:02:58PM +0100, Lars Doelle wrote: Hi Luc, thank you for reviewing the device description so throughout. I'll work through your comments doing my best to make the description confirm to your standards. This is an Inet K970??, and like all inet devices this is very often rebadged. Referring to some of your notes [[Inet K970]]: As described in the wiki page, please fire up android, and find out the last 1-2 letters, which usually are tied to a given display size and wifi module, and use this name everywhere instead. I broke the Android partition while probing ft5x_ts prior starting the device description, so I could not report the Android's bits anymore. Meanwhile I restored the image. Anyway, if you mean the 'Build number', its in the wiki page now, saying: A20_K9701_K9701L2B_1210239.20121030 Otherwise I'm not clear, to what you might refer to by last 1-2 letters. Ok, let's keep the name at K970 for now, perhaps no other K970 devices will turn up. The K970 can be found on aliexpress though. Another point you notices, is the Wifi part. If possible, please reread what i wrote there: 1) The first link is IMO a proper reference to the relevant Wifi section. Yes and no. The way i changed it makes it conform to the other devices, and, it is more future proof, meaning that you will not have to go revisit when the wifi page changes, or the status of this driver changes. 2) The second link refers to a patch making the third USB-head going, to which the RTL8723AU, which is USB-device is connected. So it was not in the fex. If I did something wrong activating it this way, I like know about it. Nobody has so far gone and created a bluetooth page. For the OTG, state is as described. W.r.t. OTG the only note on the [[USB]] page is: On an Hackberry and A20-based tablet (with a single OTG USB port) the main sunxi-3.4 branch kernel (as of 22 Nov 2013) with default defconfig settings also seems to leave USB devices without power. This can be fixed by enabling the Inventra Highspeed Dual Role Controller in Device Drivers - USB Support and selecting the Allwinner Platform Glue option. By saying This is standard A20 stuff. Move to the USB page., do you mean I should not use this options? Otherwise I could file a proper report of the state. Yes, this is specific to the A20 SoC. All A20 based devices have OTG issues as the A20 - sunxi codebase otg port was not complete. For the last points, uart and pictures, this basically a matter of equipment. As this is the first time for me dealing with small electronics and I to check whether my probes and soldering stuff are sharp enough for this purpose. Contrary to the other Inet board pictures in the wiki, i could not locate any writings on the board indicating the uart on the first examination. Thus almost certainly, I'll have to probe them. Get a good board picture. The picture of the board on the inet site very clearly shows the uart pins. Most of the pictures have been taken free-hand though with some support with the flash deactivated causing them to become blurry. I'm looking to get a tripod, perhaps this will do better. For the same reason, I did not yet publish a detailed picture of the board and its chips. Try multiple passes for focussing correctly, and try supporting your elbows. Thanks for sticking with this. This could be another solidly supported and properly documented device. 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] [PATCH] Mainline U-boot -- Tristan Auron Planet 1 tablet
On Sat, Jan 10, 2015 at 12:15:42AM +0100, Luc Verhaegen wrote: On Fri, Jan 09, 2015 at 05:33:17PM +0100, Lars Doelle wrote: This patch adds settings for yet another A20 tablet. To reduce the various dram settings, dram_sun7i_384_1024_iow16 has been used. This changes the .trp4 register from 3 to 0 and lets the device run somewhat underclocked. No device tree settings have been created for the device, yet. This is an Inet K970??, and like all inet devices this is very often rebadged. As described in the wiki page, please fire up android, and find out the last 1-2 letters, which usually are tied to a given display size and wifi module, and use this name everywhere instead. Luc Verhaegen. cfr http://linux-sunxi.org/Inet_K970 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] [PATCH] Mainline U-boot -- Tristan Auron Planet 1 tablet
On Fri, Jan 09, 2015 at 05:33:17PM +0100, Lars Doelle wrote: This patch adds settings for yet another A20 tablet. To reduce the various dram settings, dram_sun7i_384_1024_iow16 has been used. This changes the .trp4 register from 3 to 0 and lets the device run somewhat underclocked. No device tree settings have been created for the device, yet. This is an Inet K970??, and like all inet devices this is very often rebadged. As described in the wiki page, please fire up android, and find out the last 1-2 letters, which usually are tied to a given display size and wifi module, and use this name everywhere instead. 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 v4 0/5] simplefb: add clock handling code
On Sun, Nov 02, 2014 at 10:28:48AM -0500, jonsm...@gmail.com wrote: Simplefb is also being developed as a way of protecting the BIOS setup of the framebuffer past the boot process and out into use as a normal user space console. I in no way support this use. We have experienced decades of problems on the x86 with VGA and BIOSes that I do not wish to repeat in the ARM world. Oh wow. Luc Verhaegen, aka, the guy who made BIOS-free display drivers possible. -- 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: iNet K70E board
On Tue, Nov 04, 2014 at 01:51:58AM -0800, zyanna...@gmail.com wrote: hello guys i need the firmware for my tablet which is inet k70e rev01 please anyone can give me? i flashed the wrong firmware now the wifi, and the auto rotation doesnt work. any help is appreciated Nope. http://linux-sunxi.org/Inet_k70e lacks the really reall important bits. 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: iNet K70E board
On Tue, Nov 04, 2014 at 06:43:31AM -0800, Zyan Nawaz wrote: so i need stock rom for INET K70E REV01 to flash back to stock Do not take these things off the list. But yes. And you might consider fixing that device page so you or someone else wouldn't have to find the stock image in future and could just use our code. 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] Wiki page to track allwinner datasheets (user manual) errata
On Wed, Oct 01, 2014 at 09:04:36AM +0200, Hans de Goede wrote: Hi, Sounds good. Unfortunately I've come to the conclusion that I'm way too busy lately, and that I've to better prioritize things (and actually drop low priority items after setting priorities). I'm afraid this item has been put on the to be dropped list. I'm sorry (really I am). I hope someone else can pick this up. Regards, Hans I already found it, let's call it, out of place, when you offered to work the wiki. 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: [PATCH 4/4] simplefb: add clock handling code
On Wed, Oct 01, 2014 at 12:12:20PM -0600, Stephen Warren wrote: On 10/01/2014 11:54 AM, jonsm...@gmail.com wrote: On Wed, Oct 1, 2014 at 1:26 PM, Hans de Goede hdego...@redhat.com wrote: ... We've been over all this again and again and again. RGH! All solutions provided sofar are both tons more complicated, then the simple solution of simply having the simplefb dt node declare which clocks it needs. And to make things worse all of them sofar have unresolved issues (due to their complexity mostly). With the clocks in the simplefb node, then all a real driver has to do, is claim those same clocks before unregistering the simplefb driver, and everything will just work. Yet we've been discussing this for months, all because of some vague worries from Thierry, and *only* from Thierry that this will make simplefb less generic / not abstract enough, while a simple generic clocks property is about as generic as things come. Note: I haven't been following this thread, and really don't have the time to get involved, but I did want to point out one thing: As I think I mentioned very early on in this thread, one of the big concerns when simplefb was merged was that it would slowly grow and become a monster. As such, a condition of merging it was that it would not grow features like resource management at all. That means no clock/regulator/... support. It's intended as a simple stop-gap between early platform bringup and whenever a real driver exists for the HW. If you need resource management, write a HW-specific driver. The list archives presumably have a record of the discussion, but I don't know the links off the top of my head. If nobody other than Thierry is objecting, presumably the people who originally objected simply haven't noticed this patch/thread. I suppose it's possible they changed their mind. BTW, there's no reason that the simplefb code couldn't be refactored out into a support library that's used by both the simplefb we currently have and any new HW-specific driver. It's just that the simplefb binding and driver shouldn't grow. Define resource management. Simplefb should never alter resources. It should never alter anything that $bootloader set up. It should however claim resources to prevent them from being altered. Perhaps the word managing should be split up in claiming and altering here. 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] Wiki page to track allwinner datasheets (user manual) errata
On Tue, Sep 30, 2014 at 06:21:18PM +0200, Hans de Goede wrote: Hi All, I think we should start an errata page on the linux-sunxi wiki somewhere, specifically targeting errata for the official user manual documents. I know we already have various pages to document specific blocks, the idea here would be to have a general errata page. The purpose is to have a single place to gather doc fixes for blocks which are adequately documented in the user-manual, except for one or two missing bits. IMHO it is not worth the trouble / useful to create an entire new page for cases where we're talking about just 1-2 bits. But it would be useful to gather these little fixes somewhere, hence the suggestion to have a generic errata page. For blocks for which we already have extensive documentation in the wiki, this generic page can contain links to the documentation for these blocks. So good or bad idea ? And if you believe this is a good idea, any suggestions for a name / hierarchy for these pages ? ### The specific case triggering this idea is the lack of documentation for bits 10-12 of the GMAC clk register (0x01c20164). I've been in contact with allwinner about these 3 bits, and they configure the GMAC Transmit Clock Delay Chain (GTXDC), they are the transmit equivalent of bits 5-7. Regards, Hans Sounds like a plan. Let's start out with something like this: Start with a page called documentation or something. Then start listing the datasheets, one section per chipset (single =) on that page. Have the device pages link to those sections. Then have a per chipset errata page reachable from each chipset specific section. We will see where to go from there. 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: Re: [linux-sunxi] Allwinner documentation (hardware datasheet, user manual) for A10, A10s, A13, A20, A31, A31s
On Mon, Sep 29, 2014 at 05:46:35PM +0800, ke...@allwinnertech.com wrote: Hi All, I have put the documents on github, and the url is https://github.com/allwinner-zh/documents.git Thanks Simos, Henrik and Luc's suggestion. And other documents will be upated to here when released. Thanks! Everyone who is interested who has a github account can set himself to watching and not miss a thing :) 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: [PATCH 4/4] simplefb: add clock handling code
On Mon, Sep 29, 2014 at 06:28:14PM +0200, Maxime Ripard wrote: On Mon, Sep 29, 2014 at 03:47:15PM +0200, Thierry Reding wrote: This is a fundamental issue that we are facing and I'm trying to come up with a solution that is future-proof and will work for drivers other than simplefb. Just because we currently lack this functionality doesn't make it a hack trying to add it. Or maybe it's just showing that the trend to rely more and more on the firmware is a bad idea? I really start to consider adding a sunxi-uboot-fb, that would just duplicate the source code of simplefb but also taking the clocks. Somehow, I feel like it will be easier (and definitely less of a hack than using the generic common clock API). In the 2nd round of this discussion, i stated that another fb or even a drm driver altogether seemed to be the sensible way out of this mess. I suggest drm_rescue. Then instead of hacking existing drivers to work on your particular platform you should start looking into hacking your platform drivers to cope with the lack of a proper display driver. Or alternatively spend the time getting a proper display driver merged. Whether simplefb is used as primary framebuffer or just during only boot until hand-off to a real driver, it still remains a stop-gap solution. Then really, simplefb deserves a more appropriate name. Like uselessfb, tegrafb, DONOTUSEITYOUSTUPIDDEVfb or whatever makes it not look generic. Very early on, now almost two months back, i used the word denialfb. rpifb is the real name of this thing though, but then the dt binding names would have to change and whatnot. I don't get the resistance, at least not from a technical point of view. And i do not care enough to get properly involved in this pointless and endless discussion. drm_rescue it is. 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: [PATCH 4/4] simplefb: add clock handling code
On Mon, Sep 29, 2014 at 06:58:42PM +0200, Luc Verhaegen wrote: In the 2nd round of this discussion, i stated that another fb or even a drm driver altogether seemed to be the sensible way out of this mess. I suggest drm_rescue. Very early on, now almost two months back, i used the word denialfb. rpifb is the real name of this thing though, but then the dt binding names would have to change and whatnot. I don't get the resistance, at least not from a technical point of view. And i do not care enough to get properly involved in this pointless and endless discussion. drm_rescue it is. Luc Verhaegen. So Thierry, let's review what we have achieved here. 1) you keep simplefb absolutely true to the name. Congratulations. 2) Simplefb will only have a single user: the rpi. As the only other users i can think of, which does not have a full driver and which does not have clocks automatically disabled, are discrete cards. And they do not really tend to happen with dt or platform devices. 3) a competing driver will be created, which will do these dt-ishy things. 4) it's just a matter of time before the rpi either gets a full driver, or switches over to the driver that everyone else is actually using. And then the misnomer gets deprecated. Was that the outcome you were looking for? I think not. 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] Allwinner documentation (hardware datasheet, user manual) for A10, A10s, A13, A20, A31, A31s
On Sat, Sep 27, 2014 at 04:26:26PM +0300, Simos Xenitellis wrote: Hi All, I just received from Sugar the documentation files (hardware datasheet and user manuals) for the A10, A10s, A13, A20, A31 and A31s. This is part of the release of documents of documents that was announced a few weeks ago. There should be a subsequent release of the remaining SoCs at a later date. I offered to curate the documents, so here we go: In each document there is a revision history that shows what changed between versions. The revision history is consistently followed, thus I did not add any dates in the filenames. The filenames have two decimal digits (instead of one) for the version because some old versions did use the second decimal digit. Here are the version numbers of the new documents compared to what was previously available at http://dl.linux-sunxi.org/ Hardware datasheets A10: version 1.70 (previously known version 1.21) A10s: version 1.40 (previously known version 1.20) A13: version 1.30 (previously known version 1.12) A20: version 1.40 (none) A31: version 1.40 (previously known version 1.00) A31s: version 1.40 (previously known version 1.30) User manual A10: version 1.50 (previously known version 1.20) A10s: version 1.30 (none) A13: version 1.30 (previously known version 1.20) A20: version 1.20 (previously known version 1.00) A31: version 1.20 (previously known version 1.10) A31s: version 1.10 (previously known version 1.00) Here are the SHA1 checksums, b0507d4f96ceafe08eddb3182c5f328614deb606 AllwinnerDocs/A10s/A10s User Manual V1.30.pdf 3cb77cde50d6e720af8ee9de1bc167253670741d AllwinnerDocs/A10s/A10s Datasheet V1.40.pdf 6984efaeb7fbb046df2145d3b988cf7fda1e822a AllwinnerDocs/A31s/A31s User Manual V1.10.pdf 0d2bf1356906c47ccca977449a17bc2aa15008e9 AllwinnerDocs/A31s/A31s Datasheet v1.40.pdf b341bed4e7b2d653265cb2abe088a32aac563222 AllwinnerDocs/A13/A13 Datasheet V1.30.pdf 9c555300f673c2334c821823f83c7af2115a3b81 AllwinnerDocs/A13/A13 User Manual V1.30.pdf ca6c4ae69db8df28b0bf99326f41a87cd6659a24 AllwinnerDocs/A20/A20 Datasheet V1.40.pdf 83526d6f80bdcf22011bbd1ba2b811e91dfac21f AllwinnerDocs/A20/A20 User Manual V1.20.pdf eaa07db283c609b36d19d8b0d014debc42a0d85c AllwinnerDocs/A10/A10 User manual V1.50.pdf 978d45b865c426dbfbfe3f08666f47265fbd2c00 AllwinnerDocs/A10/A10 Datasheet V1.70.pdf 423e8564bc1e190af67262b32b840ae37b2d3a51 AllwinnerDocs/A31/A31 User Manual V1.20.pdf e9c2226d0d16bff66d2d53dd2c08ac3185dc6905 AllwinnerDocs/A31/A31 Datasheet V1.40.pdf You can find the docs at http://dl.linux-sunxi.org/ in their respective directories with the filenames shown above. If you would like to download these files as a set, see http://dl.linux-sunxi.org/users/simos/ Simos Why didn't someone from Allwinner send these documents in him/herself? 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: * failed to open vchiq device
On Thu, Sep 25, 2014 at 12:16:18PM -0700, willemjan.deh...@gmail.com wrote: Hi, I also have a banana pi and installed precompiled mali gpu packages from here: http://forum.lemaker.org/2872-1-1-precompiled_mali_gpu_drivers_for_debian.html (I use the Lubuntu image). Had to compile my own version of fbturbo though. Just tried the test/test from sunxi-mali and I get to see the colored triangle. One thing was that I had to add -lX11 to the build command for 'test'. Oh wow. I just looked at that guys libump... He just cleared out the changelog and removed my name from the debian control file. Unbelievable. Why do i even bother with doing the right thing? 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.
