From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: question: /sys/class/net/*/wireless
Date: Sat, 03 Mar 2007 12:18:11 +0100 [thread overview]
Message-ID: <1172920691.4966.6.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
Hi,
It just occurred to me that /sys/class/net/*/wireless/ completely
depends on wireless extensions. Since we're attempting to kill wireless
extensions and hopefully will succeed in doing that some time soon, it
is possible that people will be running with mac80211 drivers w/o
CONFIG_WIRELESS_EXT.
This leaves us in a sticky situation. People with CONFIG_WIRELESS_EXT
will have /sys/class/net/*/wireless/ directories, but people without
won't, and CONFIG_WIRELESS_EXT will not be necessary for a lot of
people.
Thus, I think we'll need to offer a /sys/class/net/*/wireless/ directory
for cfg80211-only systems as well, since that'd also be the only way to
tell if a device is wireless from sysfs. However, I'd much rather have
that dir called ieee80211 in accordance with what we're doing elsewhere.
But pre-802.11 equipment also uses wireless ext. Hmm :)
We could create ieee80211 and create a symlink to it.
Another thing we could do is simply deprecate the wireless directory
there, but then wireless-ext users wouldn't have a way to tell if a
netdev is wireless from sysfs.... Kinda feels like a "caught between a
rock and a hard place" type of situation to me right now but I'm sure
someone can come up with something perfect :P
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next reply other threads:[~2007-03-03 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 11:18 Johannes Berg [this message]
2007-03-03 11:27 ` question: /sys/class/net/*/wireless Johannes Berg
2007-03-03 17:40 ` Jouni Malinen
2007-03-03 19:53 ` Johannes Berg
2007-03-04 0:21 ` Johannes Berg
2007-03-16 14:03 ` Jiri Benc
2007-03-16 17:07 ` Johannes Berg
2007-03-21 14:12 ` Jiri Benc
2007-03-21 14:16 ` 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=1172920691.4966.6.camel@johannes.berg \
--to=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