All, I've updated the repo[1] so that it downloads the binary backup for the nightly build from ZTE's website (so there's no issue of copyright in the repo).
[1] - https://github.com/diafygi/b2g_inari_nightly/commit/488d759 Happy New Year! Daniel Roesler On Thu, Jan 2, 2014 at 5:12 AM, Chris Mills <[email protected]> wrote: > Hi guys, > > Feel free to pass corrections to me to implement, if needed. I wrote the > current docs as they are because I was told the ZTE Open would work with > Inari B2G builds. Let me know what is wrong and needs updating. > > cheers, > > Chris Mills > Senior tech writer || Mozilla > developer.mozilla.org || MDN > [email protected] || @chrisdavidmills > > > > On 30 Dec 2013, at 07:38, Daniel Roesler <[email protected]> wrote: > >> So should the MDN page be changed to the correct config setting? >> On Dec 29, 2013 4:04 PM, "Robert Kaiser" <[email protected]> wrote: >> >>> Daniel Roesler schrieb: >>> >>>> On Sun, Dec 29, 2013 at 7:24 AM, Robert Kaiser <[email protected]> wrote: >>>> >>>>> 2) To prevent misunderstanding, please do not call them "inari" as that >>>>> code >>>>> name is used for a slightly different (testing-only) device on which >>>>> those >>>>> builds will not work correctly (just like the builds for the inari do not >>>>> work correctly on the ZTE Open) as the kernel modules are different. The >>>>> code name for the ZTE Open is ikura, so that probably makes sense to be >>>>> used >>>>> there. >>>>> >>>> >>>> These are technically inari builds, since the command is "./config.sh >>>> inari". This is the configuration recommended for the ZTE Open in the >>>> wiki[3]. So, I suppose you could flash these builds to your true inari >>>> device, but I don't have one of those so cannot confirm if it works. >>>> >>> >>> The "inari" build configuration can be used to generate builds for the >>> inari (testing device) as well as the ikura (ZTE Open) - but the resulting >>> build only work on the one whose kernel etc. you used for building. I know >>> it's confusing, but that's what it is. I ran into the same kind of issues >>> when trying a build generated for inari on a ZTE Open and found out it does >>> not work correctly (it boots but e.g. wifi isn't working) - I'm pretty sure >>> it's the same the other way round. >>> >>> KaiRo >>> _______________________________________________ >>> 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 > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
