<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2016-09-14 12:34 GMT+02:00 Luke Kenneth Casson Leighton <span dir="ltr"><<a href="mailto:lkcl@lkcl.net" target="_blank">lkcl@lkcl.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">---<br>
crowd-funded eco-conscious hardware: <a href="https://www.crowdsupply.com/eoma68" rel="noreferrer" target="_blank">https://www.crowdsupply.com/<wbr>eoma68</a><br>
<br>
<br>
</span>On Wed, Sep 14, 2016 at 10:07 AM, Josh Branning<br>
<<a href="mailto:lovell.joshyyy@gmail.com">lovell.joshyyy@gmail.com</a>> wrote:<br>
<br>
> Getting rid of boot0 is not far away:<br>
><br>
> <a href="http://git.denx.de/?p=u-boot/u-boot-sunxi.git;a=tree;f=board/sunxi;h=6419936f8b204d43c146ff5d8c88d1b0484fdcae;hb=refs/heads/next" rel="noreferrer" target="_blank">http://git.denx.de/?p=u-boot/<wbr>u-boot-sunxi.git;a=tree;f=<wbr>board/sunxi;h=<wbr>6419936f8b204d43c146ff5d8c88d1<wbr>b0484fdcae;hb=refs/heads/next</a></blockquote><div><br></div><div>Can't reply to josh directly. </div><div><br></div><div>There are two problems. 1st a legal one 2nd a technical. The technical one is being resolved by the community. With little help from Allwinner. I say a "little help" not "no help". When A64 is bootable by uboot then it might by a possible EOMA68 target, from firmware perspective. </div><div><br></div><div>AFAIK:</div><div><br></div><div>The early boot loader in AW SOC's is BROM: <a href="http://linux-sunxi.org/BROM">http://linux-sunxi.org/BROM</a>. It built in on production and cannot be modified, hence ROM: Read Only Memory. The ROM can be read however. The BROM is the first software loaded in the chain. Currently it can load the AW Boot0 or U-Boot SPL.</div><div><br></div><div>After Boot0 comes Boot1. After U-Boot SPL comes U-Boot.</div><div><br></div><div>boot1 is a AW modified U-Boot.</div><div><br></div><div>So if i'm correct there is a for stage boot sequence.</div><div>1. BROM (Find and start bootable software)</div><div>2. Boot0/U-Boot SPL (Init Hardware like memory, uart, clocks, regulators then load the next stage)</div><div>3. Boot1/U-Boot (Init perhipials and load the final stage: Linux)</div><div>4. Linux</div><div><br></div><div>The SoC have a tiny bit embedded RAM (SRAM). Just large enough for boot0 os U-Boot SPL which init's the external RAM (DRAM) and load the next boot stage to is and starts it. </div><div><br></div><div>The legal problem is different. And the cannot, easily, be fixed afterwards. AW has sold/is selling SoC's including binary, modified, copies of GPL software. U-Boot (boot1), FFMpeg(cedar) and few other.</div><div><br></div><div>While in China this is not a big, legal, problem. In most other countries this is plain illegal. </div><div><br></div><div>So if I were to buy hardware from AW along with the software they provided and resell it I would be making three violations. </div><div>1. Selling illegal software</div><div>2. Buying illegal software</div><div>3. Helping another parties sell illegal software</div><div><br></div><div>And anyone reselling my products would face the same issues</div><div><br></div><div>And once done it cannot be undone, damage has been done. But as long as nobody complains I can keep doing it. That's the way the world works. But it still would put me at risk of prosecution, import blokkades, etc. </div><div><br></div><div>Every country weighs violations differently. In some countries I would be part of criminal cartel, not very hard to imagine.<br></div><div><br></div><div>I can try to rectify and publish afterwards. But I can still be held accountable for damage done. </div><div><br></div><div>I can try sending out replacement software "stripped" of the GPL violation stuff. But I can still be held accountable for damage done. </div><div><br></div><div>I can try sending out replacement software masking the GPL violation stuff. But I can still be held accountable for damage done and being done.<br></div><div><br></div><div>When I'm reselling I don't have any of the options above. I can only hope AW wil help me. But as they already have my money I'm of little interest i guess. I could spend a lot of time and money to rectify it myself, but as you can see with the sunxi community that probably be too slow and expensive. But for Allwinner it would be almost cost-less to do.</div><div><br></div><div>GPL software is free but comes with some, legally binding, restrictions. When your not abiding those restrictions you are violating a legal contract. Hence the illegal software. Contracts do not always require signatures. Contracts are a formal agreement of terms.</div><div><br></div><div><div>Look at Oracle, Samsung, Google, SCO, etc. They have done all of the above. And now they are 'actively' changing their ways. But they are big enough to stall. SCO tried and died. It's never pretty.</div></div><div><br></div><div>Luke's EOMA68-A20 is something unheard of. Buying hardware without SDK and probably support. And selling it with a totally free stack of software and firmware.</div><div><br></div><div>That and no co-processors which can work independently from your system to help/spy/corrupt you.</div><div><br></div><div>The only exception is the BROM. But that can/should be considered hardware as it cannot be changed and is build-in. Plus the bonus that it can be read and verified.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
i'm not sure why you're referencing this, josh - it<br>
<br>
> I'm sure, and there is some evidence that Olimex puts pressure as it is on<br>
> Allwinner to release their code and stop ignoring GPL licensing conditions.<br>
<br>
you'll need to be more specific.<br>
<br>
> You say Olimex made a GPL-violation and then basically made the fool of you<br>
> 'in-front of 20,000 people', but they seem otherwise. [1]<br>
<br>
you'll need to reference <a href="http://archive.org" rel="noreferrer" target="_blank">archive.org</a> to find the conversation.<br>
tsvetan's disdain is very very clear. and he also, just as clearly,<br>
doesn't actually answer the question.<br>
<br>
<br>
> According to them, you were complaining that they hadn't released the source<br>
> early enough, because they hadn't written a tutorial of how to build as soon<br>
> as they released the images.<br>
<br>
i don't believe it (but i could be wrong - i often am). allwinner<br>
hadn't actually released the source of the proprietary boot0<br>
bootloader back then, and things were a total mess. i've yet to reply<br>
but paul might actually be right about <a href="http://git.rhombus-tech.net" rel="noreferrer" target="_blank">git.rhombus-tech.net</a> because it<br>
might contain (for example) libnand. i *think* on review of the code<br>
i did go "i ain't frickin well putting *that* in the git repo" but<br>
i'll have to double-check. it was a long time ago.<br>
<br>
<br>
> Though I guess it is unclear as to what<br>
> actually happened back then. (<a href="http://lists.gpl-violations.org" rel="noreferrer" target="_blank">lists.gpl-violations.org</a> is down).<br>
<br>
it's permanently offline after the server was hacked. it won't be restored.<br>
<br>
> Either way, it doesn't really matter much, I appreciate what you're doing,<br>
> making another libre computer, and for that I am grateful. I'm also pleased<br>
> you posted the schematics and pcb files as you said you would.<br>
<br>
various parts already were - have been for many years.<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
l.<br>
<br>
______________________________<wbr>_________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" rel="noreferrer" target="_blank">http://lists.phcomp.co.uk/<wbr>mailman/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a></div></div></blockquote></div><br></div></div>