<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 31, 2014 at 2:05 PM, Chris Larson <span dir="ltr"><<a href="mailto:clarson@kergoth.com" target="_blank">clarson@kergoth.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="">On Friday, January 31, 2014, Nicolas Dechesne <<a href="mailto:nicolas.dechesne@linaro.org" target="_blank">nicolas.dechesne@linaro.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Fri, Jan 31, 2014 at 8:01 PM, Iorga, Cristian<br>
<<a>cristian.iorga@intel.com</a>> wrote:<br>
> On my Ubuntu 13.10 dev machine, wireless-tools and iw are both installed by<br>
> default (I might be wrong here, maybe I installed them some time ago by<br>
> hand).<br>
<br>
you are right, they are both on the default install, see<br>
<br>
<a href="http://releases.ubuntu.com/13.10/ubuntu-13.10-desktop-amd64.manifest" target="_blank">http://releases.ubuntu.com/13.10/ubuntu-13.10-desktop-amd64.manifest</a></blockquote><div><br></div></span><div>For what its worth, I personally would love to see wireless-tools go away in favor of iw, much as ifconfig has gone to the wayside in favor of iputils.</div></blockquote><div><br></div><div>Bringing this back up again, as I think we really need to at the *very* least pull in iw from meta-oe into oe-core, and adjust packagegroup-base (worst case, with a VIRTUAL-RUNTIME), and better yet also drop wireless-tools / move it to meta-networking.</div><div> </div></div><div class="gmail_extra">From the debian /usr/share/doc/iw/README.Debian:</div><div class="gmail_extra"><br></div><div class="gmail_extra"> Why is wireless-tools being replaced?</div><div class="gmail_extra"> =====================================</div><div class="gmail_extra"><br></div><div class="gmail_extra"> A complete summary of technical reasons for the abandonment of Linux Wireless</div><div class="gmail_extra"> Extensions API is documented on the <a href="http://wireless.kernel.org">wireless.kernel.org</a> wiki page for WEXT [3].</div><div class="gmail_extra"><br></div><div class="gmail_extra"> In brief, WEXT uses ioctl's as the kernel<->userspace communication mechanism,</div><div class="gmail_extra"> but some developers wish to have a more structured transport mechanism, which</div><div class="gmail_extra"> cfg80211 and nl80211 provide, to allow them to address old nagging problems</div><div class="gmail_extra"> with the current wireless device configuration implementation, and give them</div><div class="gmail_extra"> more freedom to enhance the process of wireless configuration [4].</div><div class="gmail_extra"><br></div><div class="gmail_extra"> WEXT is in deep maintenance mode, cfg80211 and nl80211 are the communication</div><div class="gmail_extra"> transport mechanism of the future.</div><div class="gmail_extra"><br></div><div class="gmail_extra"> [3] <a href="http://wireless.kernel.org/en/developers/Documentation/Wireless-Extensions">http://wireless.kernel.org/en/developers/Documentation/Wireless-Extensions</a></div><div class="gmail_extra"> [4] which is one of the areas which, in my opinion, has always been difficult</div><div class="gmail_extra"> for new adopters on Linux, especially on the desktop.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Also:</div><div class="gmail_extra"><br></div><div class="gmail_extra"> <a href="https://wireless.wiki.kernel.org/en/users/Documentation/iw">https://wireless.wiki.kernel.org/en/users/Documentation/iw</a> indicates "The old tool iwconfing, which uses Wireless Extensions interface, is deprecated and it's strongly recommended to switch to iw and nl80211."</div></div><div class="gmail_extra"><div class="gmail_extra">-- <br></div><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>