<arnd>
This probably depends on whether they consider the GPL "prior written permission of the company". They can probably argue that they have given written permission to distribute the GPL bits by including the license text and stating "the licenses in here must be strictly observed"
<libv>
another view is that click through eulas were iirc not enforceable in the eu
<libv>
and that european law and the actual license takes precedence
<libv>
still very bad form
<smaeul>
a little bit better than having to get the source "leaked" by a distributor
<smaeul>
but that's a terribly low bar :)
<arnd>
that wouldn't help them, since they would still have lost the right to distribute that software in other parts of the world
<libv>
smaeul: that source was leaked _9_ys ago
<libv>
and we slapped them with the ffmpeg stuff 6 years ago
<libv>
when they tried to get around the lgpl by stripping the binaries
<smaeul>
libv: I'm talking about the BSPs released by Pine64, Xunlong, etc.
<libv>
first off, the board vendors are the first point of contact for compliance with gpl by owners of respective boards
<libv>
secondly, we have been playing this game for 9 years, and they still have not learned much
<smaeul>
which are downloaded from exactly the same place as the D1 BSP, but supposedly aren't public
<arnd>
libv: IIRC they never renewed the membership after the first term ended
<libv>
back then i warned people that it would lead to allwinner no longer doing the actual work necessary, as they claimed to be a member of linaro, and then they did not have to do anything more
<libv>
arnd: wow
<libv>
and a term would be 1y?
<arnd>
you won't ever see an announcement of anyone leaving some organization, no matter whether that is the Linux Foundation, Linaro, or the RISC-V foundation
<libv>
sure
<arnd>
most Linaro members have 24 month terms, not sure what exceptions there are, if any
<libv>
but only a single term, for what is arguably the most popular sbc soc maker after broadcom
<arnd>
also, note that 'member of the digital home group' is almost nothing at all, that was a fairly small group within Linaro, and there were a bunch of members that never did anything useful either
<libv>
cheap sbc maker
<libv>
yeah, and it seems like set top boxes are no longer a useful market from where i sit
<libv>
but i have an incredibly small window of visibility there
<arnd>
I don't know if they joined the 96boards group as well
<gamiee>
but actually, their SoCs are used only on set top boxes as far as I know
<gamiee>
H6 & H616 (or H313) is most occuring, but other their SoCs are hard to find at market. (that means it's not much used)
<arnd>
the digital home group also stopped existing in the meantime, and they had already not been overly active for a few years
<arnd>
(in Linaro)
<smaeul>
their automotive head unit SoCs (T3 and T7) seem to be reasonably obtainable
<smaeul>
but yeah, the tablet series might as well not exist
<libv>
another story of inability to understand what is going on and how to do things properly, and a lot of missed opportunities
jakllsch has quit []
jakllsch has joined #linux-sunxi
<libv>
via all over
<gamiee>
libv: exactly, Allwinner lives only thanks to sunxi community
<gamiee>
smaeul: yes, they are used a bit in cheap car entertainment systems, but the amount of those systems with allwinner soc are nothing in opposite of systems with Rockchip PX-Series SoCs
jakllsch has quit []
jakllsch has joined #linux-sunxi
<arnd>
are there any cars shipping with either of them? I thought they are all aftermarket radio parts, which don't make a lot of money
<libv>
arnd: thanks for the info, i had no idea that it was _that_ shortlived, i just felt like it would make them even more complacent than they already were
<gamiee>
arnd: I mean those aftermarket android radios. But I heard that they are using in some car, but I can't confirm this.
<aperezdc>
libv: <3
<aperezdc>
(That wad about the SDK link)
<gamiee>
(and there is also V-series, which is bit used in gopro clones or car driving recorders, but still it's hard to find them)
<libv>
aperezdc: got sidetracked several times trying to read up on repo manifests again, i will get to that tonight and get repos up on our github account
<smaeul>
I think all you have to do is modify the <remote fetch=""> part
<aperezdc>
libv: no worries, no hurries
<aperezdc>
Is there something I can help with? Me being a total newbie to kernel development, that is.
<aperezdc>
I do WebKit for a living, and maintain the corresponding Buildroot packages (and some of the dependencies)
<smaeul>
> "The certificate for dl.linux-sunxi.org expired on 4/26/2015."
* aperezdc
mostly wanted to pick a RISC-V board because they enjoyed doing MIPS assembler in the past and this seems the obvious evolution
<aperezdc>
I did clone sunxi-tools to try and make it recognize the D1
<aperezdc>
I have the "version" command printing "D1" and I started looking at the D1 docs and the sunxi-fel code around to understand how the SRAM swap stuff and memory info is used
<aperezdc>
But I'm going super slow because this is something I am doing in hobby time
<aperezdc>
Meaning: if somebody else writes a patch, that's fine, I don't mind
<smaeul>
the problem with sunxi-tools is that it sends a bunch of assembly thunks to the device... and those are all ARM assembly
<aperezdc>
ah, let's take a look, I hadn't noticed that branch
<aperezdc>
ah, yes I see why the commit message says it's hackish, it replaces some options from the ARM compiler commands to have -march=rv64g and other amusing bits like that