<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 29, 2014 at 6:43 PM, Dan Smith <span dir="ltr"><<a href="mailto:dsmith@danplanet.com" target="_blank">dsmith@danplanet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> I don't know what the "backport" process involves, but rolling out a<br>
> v0.4.1 that will prevent the cross loading of pre-N5R-20 firmware .img<br>
> files with N5R-20 firmware radios (and the other way around) seems like<br>
> the right thing to do.<br>
<br>
</span>Okay, just to be clear, can you tell me exactly which changes would need<br>
to be made on top of 0.4.0? I can try to figure it out based on the<br>
issue numbers you provided, but thought maybe there was one specific<br>
change that would be easier to apply (and/or rewrite) just to get the<br>
firmware version protection, without a bunch of other changes.<br>
<br>
Thanks!<br>
<span class="HOEnZb"><font color="#888888"><br>
--Dan</font></span><br></blockquote></div><br></div><div class="gmail_extra">I believe that #1773 should be the only issue number needed to provide the firmware version protection.<br><br></div><div class="gmail_extra">To deal with any of the other 3 issues, the user should just upgrade to the latest daily build.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Jim<br></div></div>