Le 29/12/2013 17:24, Daniel Dressler a écrit : > 2013/12/29 Daniel Roesler <[email protected]>: >> On Sun, Dec 29, 2013 at 7:24 AM, Robert Kaiser <[email protected]> wrote: >>> Daniel Roesler schrieb: >>>> >>>> I finally got around to making a nightly build script for the ZTE >>>> Open. I've only tested these my US version of the ZTE Open (updated to >>>> Version 02 before flashing), so I don't know if they work on the UK >>>> version of the ZTE Open. >>> >>> >>> 1) How are you able to distribute the binary blobs that AFAIK are not >>> allowed to be redistributed? >> >> The custom boot binary was originally released for open >> distribution[1], so including it in the repo isn't a license issue. >> >> I'm not aware that a /system backup (backup-inari.zip) from my ZTE >> Open cannot be included with the repo [2]. Can you please link to the >> license agreement that must be accepted when purchasing the ZTE Open >> that restricts system backups from being published? > > The problem is under the Berne Convention copyright is automatic and > restrictive by default. Without an explicit license allowing us the > right to redistribute we are not allowed to distribute the binaries. > The evil goes deep. It's not just a matter of getting ZTE's permission > since they are in turn dependent on their upstream: the SoC > manufacturer and related companies. Even Google has not gotten > redistribution rights for all their phone's parts. > > You might have encountered a similar situation if you used linux with > a broadcom wireless a few years back. The wireless required a binary > blob which no linux distribution was allowed to include on the install > CD. What we ended up doing was writing a program which would download > the windows driver and extract the binary blob. > > So what we could do is if ZTE has a working zip on their site we can > have the build script download that and extract the relevant files. > The risk of course is not that anyone on this list will get mad but > rather that ZTE or their upstream will sue you.
This is already what is done for Nexus devices and for all of our devices supported: we download blobs from website (Nexus) or from device itself. This also explains the issues we encounter with some devices, where we do not have uptodate blobs to build a fully working image from scratch. > > Daniel > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
