From: Johannes Berg <johannes@sipsolutions.net>
To: Jiri Benc <jbenc@suse.cz>
Cc: netdev@vger.kernel.org, Jouni Malinen <jkm@devicescape.com>
Subject: Re: [d80211 rfc] link master interface from wiphy
Date: Thu, 17 Aug 2006 09:18:08 +0200 [thread overview]
Message-ID: <1155799088.3653.1.camel@ux156> (raw)
In-Reply-To: <20060816190520.57cb676f@griffin.suse.cz>
On Wed, 2006-08-16 at 19:05 +0200, Jiri Benc wrote:
> Btw, we will probably need some way to ask d80211 about all interfaces
> belonging to given wiphy anyway. Crawling all network interfaces and
> searching for correct wiphy symlinks is probably not the best way. I
> think a new netlink interface can be used for this.
Yeah, that should be fairly easy.
> > wpa_supplicant could use this, I guess. I think
> > another link to wlan#ap should be created (or does wpa_supplicant set
> > the name of that so it knows which one it will get?), or something like
> > that anyway.
>
> wmgmt# will go away in future. There is an ioctl to get its ifindex, so
> no need for the link.
Right, Jouni pointed that out already. Forget what I said :) Besides,
I'm already working hard on deprecating it :P
> What do you mean by "making the virtual devices all children of the
> wiphy"? Currently, all virtual devices (of one physical device) have the
> same pointer to ieee80211_local in their net_dev structure and pointers
> to them are stored in the linked list in ieee80211_local.
I was wondering why they in sysfs have their device link set to the
physical device instead of the master wiphy. I'm not sure if the latter
makes sense though.
> Do you know about /sys/class/net/X/wiphy symlinks?
yes, I'm actually using them :)
Thanks,
johannes
next prev parent reply other threads:[~2006-08-17 7:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 8:07 [wireless] bunch of questions and notes on d80211 Johannes Berg
2006-08-14 8:10 ` bcm43xx for d80211 softirq loop Johannes Berg
[not found] ` <44E0300D.1000402-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2006-08-14 8:21 ` Johannes Berg
2006-08-14 13:27 ` Michael Buesch
2006-08-14 8:12 ` [d80211 rfc] link master interface from wiphy Johannes Berg
2006-08-14 12:01 ` Dan Williams
2006-08-16 17:05 ` Jiri Benc
2006-08-17 7:18 ` Johannes Berg [this message]
2006-08-14 8:13 ` [PATCH] d80211: fix some 0 vs. NULL comparisons Johannes Berg
2006-08-14 13:20 ` Johannes Berg
2006-08-14 15:48 ` Jouni Malinen
2006-08-14 8:15 ` [PATCH] d80211: get rid of the WME bitfield Johannes Berg
2006-08-14 16:12 ` Jouni Malinen
2006-08-15 7:11 ` Johannes Berg
2006-08-14 8:16 ` ieee80211_japan_5ghz / firmware etc.?? Johannes Berg
2006-08-14 8:16 ` ieee80211_set_encryption Johannes Berg
2006-08-14 15:53 ` ieee80211_set_encryption Jouni Malinen
2006-08-14 8:18 ` network manager confused with bcm43xx-d80211? Johannes Berg
2006-08-14 11:46 ` Dan Williams
2006-08-14 12:28 ` Johannes Berg
2006-08-14 12:48 ` Larry Finger
2006-08-14 12:54 ` Johannes Berg
2006-08-14 8:19 ` d80211 and sta_aid for AP functionality Johannes Berg
2006-08-17 18:21 ` Jiri Benc
2006-08-14 8:22 ` wlan#ap seems bogus Johannes Berg
2006-08-14 14:04 ` Johannes Berg
2006-08-14 18:53 ` Simon Barber
2006-08-15 7:22 ` Johannes Berg
2006-08-14 15:58 ` Jouni Malinen
2006-08-14 16:04 ` 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=1155799088.3653.1.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=jbenc@suse.cz \
--cc=jkm@devicescape.com \
--cc=netdev@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).