>-----Original Message----- >From: ipw3945-devel-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:ipw3945-devel- >bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of dragoran >Sent: Thursday, August 02, 2007 12:17 PM >To: Johannes Berg >Cc: Dan Williams; linux-wireless@xxxxxxxxxxxxxxx; network manager; ipw3945- >devel@xxxxxxxxxxxxxxxxxxxxx >Subject: Re: [ipw3945-devel] chaning mode only when interface down? > >Johannes Berg wrote: >> On Thu, 2007-08-02 at 09:44 +0200, dragoran wrote: >> >>> I noticed that I have to do ifdown wlan0 before I can change the mode >>> with iwconfig. >>> When I do it while the interface is up I get a error that the device is >>> busy. >>> >> >> It is busy. >> >> >ok >>> It seems to happen with ad-hoc, master and back from them to managed. >>> Is this a bug in the iwlwifi driver or in mac80211 ? >>> >> >> Neither, it is expected behaviour. >ok thx for this info. >> Blame it on Jean that wireless >> extensions are ill-defined and don't mandate this. >> >> >>> Because of this NM can't create ad-hoc networks because it does it while >>> the device is up. >>> Any ideas? >>> >> >> Fix NM? >> >> >Dan, something for you ;) >does NM knows if the driver is a mac80211 one? > > There is a definitely a known issue in the driver that we still need to resolve, but I agree with Johannes that there is a problem in design of the configuration as well. Unfortunately as this is in lower priority on my list now it will take few weeks till I get to solve this. Tomas >----------------------------------------------------------------------- -- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> http://get.splunk.com/ >_______________________________________________ >Ipw3945-devel mailing list >Ipw3945-devel@xxxxxxxxxxxxxxxxxxxxx >https://lists.sourceforge.net/lists/listinfo/ipw3945-devel - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
