On Mon, Mar 24, 2008 at 4:32 PM, Dan Williams <dcbw@xxxxxxxxxx> wrote: > > On Mon, 2008-03-24 at 00:28 +0200, Tomas Winkler wrote: > > On Mon, Mar 24, 2008 at 12:16 AM, Johannes Berg > > <johannes@xxxxxxxxxxxxxxxx> wrote: > > > > > > On Sun, 2008-03-23 at 20:23 +0100, Jan Niehusmann wrote: > > > > ieee80211_sta_work is disabled while network interface > > > > is down. Therefore, if you configure wireless parameters > > > > before bringing the interface up, these configurations are > > > > not yet effective and association fails. > > > > > > > > A workaround from userspace is calling a command like > > > > 'iwconfig wlan0 ap any' after the interface is brought up. > > > > > > > > To fix this behaviour, trigger execution of ieee80211_sta_work from > > > > ieee80211_open when in STA or IBSS mode. > > > > > > What happens with this patch when you haven't set any configuration > > > items before bringing the interface up? We want it to do nothing, if > > > that behaviour is kept the patch should be fine. > > > > Why should be possible to configure device when it's not up. Shouldn't > > be there some order in which things are happening? > > This was the way that wireless-tools/WEXT worked with older fullmac type > cards; the driver would usually cache the value until the device came up > (and then blast all cached values to the card and try to associate) or > the firmware would still accept commands while the interface was down > because the firmware was already on the card and didn't have to be > loaded at runtime. I'm stopping to like the idea of having firmware loaded in open, there is conceptual problem with this as we've seen in rfkill and now the configuration. Probe is a problem because the filesystem is not available so there have to be something in between. > These days, of course, with cards that load firmware on open() (ex iwl > to save power, and others) this isn't possible unless the driver caches > the values until the device is brought up. > > Personally, I don't really think this is an issue. Things change, some > cards don't allow scanning when they are down, etc. It's a lot of code > to cache the values in the driver that isn't really needed if people > just start setting the device up before configuring it. I think the > tradeoff of having to modify userspace tool behavior versus having to > maintain more code in the drivers/stack is quite clear: less code in > mac80211/drivers. Aggree Tomas -- 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
