I see. <br>But i hope this is not done only because of the airline issue, and that there are other reasons that it useful to boot with firmware unloaded.<br><br>Because as far as the airline issue is concerned, we should not take it tooo seriously. As long as we have a working solution it is fine. Not many people will use it anyway.
<br>U see my point?<br><br>Also, if it is smth simple we can quickly implement is for Update.1.<br><br><br><div class="gmail_quote">On Jan 17, 2008 7:36 PM, David Woodhouse <<a href="mailto:dwmw2@infradead.org">dwmw2@infradead.org
</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>On Thu, 2008-01-17 at 19:16 -0500, Giannis Galanis wrote:
<br>> It must be noted that the important issue of this discussion is how to have<br>> the radio blocked from BEFORE the XO boots, so as not to be conflicting with<br>> the airline regulations.<br><br></div>We should change the firmware so that it isn't active automatically as
<br>soon as it's loaded -- let the driver activate it when it's appropriate.<br>Then the decision as to whether the radio is blocked can properly be<br>handled in userspace, and the device can be left quiescent if
<br>appropriate.<br><font color="#888888"><br>--<br>dwmw2<br><br></font></blockquote></div><br>