From: "Dan E" <trg_info@mailhaven.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Userspace tools: Roadmap?
Date: Mon, 08 Dec 2008 20:01:41 -0500 [thread overview]
Message-ID: <1228784501.31197.1288992887@webmail.messagingengine.com> (raw)
In-Reply-To: <1228783903.22164.166.camel@johannes.berg>
On Tue, 09 Dec 2008 01:51:43 +0100, "Johannes Berg"
<johannes@sipsolutions.net> 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?
next prev parent reply other threads:[~2008-12-09 1:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 23:29 Userspace tools: Roadmap? Dan E
2008-12-08 7:02 ` Rami Rosen
2008-12-08 8:13 ` Johannes Berg
2008-12-08 23:18 ` Dan E
2008-12-08 23:26 ` Johannes Berg
2008-12-08 23:52 ` pat-lkml
2008-12-09 0:02 ` Johannes Berg
2008-12-09 0:08 ` pat-lkml
2008-12-12 4:58 ` pat-lkml
2008-12-12 16:24 ` Pavel Roskin
2008-12-12 21:58 ` Johannes Berg
2008-12-12 22:37 ` pat-lkml
2008-12-12 22:38 ` Johannes Berg
2008-12-12 23:36 ` pat-lkml
2008-12-12 23:42 ` pat-lkml
2008-12-12 23:50 ` Johannes Berg
2008-12-12 23:48 ` pat-lkml
2008-12-13 0:05 ` Johannes Berg
2008-12-13 0:10 ` pat-lkml
2008-12-13 0:10 ` Johannes Berg
2008-12-09 0:43 ` Dan E
2008-12-09 0:51 ` Johannes Berg
2008-12-09 1:01 ` Dan E [this message]
2008-12-09 1:05 ` Johannes Berg
2009-01-15 7:52 ` David Shwatrz
2009-01-15 9:35 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1228784501.31197.1288992887@webmail.messagingengine.com \
--to=trg_info@mailhaven.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).