On Tue, 09 Dec 2008 01:51:43 +0100, "Johannes Berg" <johannes@xxxxxxxxxxxxxxxx> said: > On Mon, 2008-12-08 at 19:43 -0500, Dan E wrote: > > > When I reboot, modprobe the driver, and do 'iwconfig wlan0 channel 9 > > commit' the .config callback does run. If I leave off the 'commit' it > > does not. > > Strange. But .start also runs, right? Something must be turning up the > interface. Eh, no you are right. It doesn't run. iwconfig was giving me an error message that I mistook for one of my callback printk debugging calls. I jumped to the wrong conclusion. > > I'm trying to validate as many callbacks as I can before > > moving on to the next step, enabling the interface. > > > > An additional question, if I may... Is wlan0 considered a "virtual > > interface" or does that term only apply to additional interfaces created > > with iw? The whole vif thing has me a little confused. > > Yes, wlan0 is a virtual interface too, the first one. So I should expect the callbacks (e.g. .add_interface and .remove_interface) when wlan0 gets created? I cannot thank you enough for your help here. I'm finally starting to feel like I can get beyond a few mental blocks I've had regarding the underlying framework, and start concentrating on the real driver workings. -- Dan -- http://www.fastmail.fm - I mean, what is it about a decent email service? -- 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
