From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dan Williams <dcbw@redhat.com>,
Michael Buesch <mbuesch@freenet.de>,
netdev@vger.kernel.org
Subject: Re: network manager confused with bcm43xx-d80211?
Date: Mon, 14 Aug 2006 07:48:22 -0500 [thread overview]
Message-ID: <44E07116.6060208@lwfinger.net> (raw)
In-Reply-To: <44E06C8B.1040400@sipsolutions.net>
Johannes Berg wrote:
> Dan Williams wrote:
> Yeah, I noticed it wasn't in /proc/net/wireless. Should've tipped me off
> I guess. And I probably also should've thought that nm would ask HAL.
> Looks like I wasn't really on track when I wrote this yesterday ;)
>> So if the wlanX interface isn't in /proc/net/wireless, you lose. I
>> think we discussed this in the private rt2x00 thread about a month ago?
>> Some patches came out of that one, specifically the SET_NETDEV_DEV ones
>> for rt2x00 and d80211. The problem with d80211 was that it didn't
>> implement the get_wireless_stats() handler function, and that function
>> (I think?) is the one that lets the wlanX device show up
>> in /proc/net/wireless.
>>
> Yeah, that sounds about right. Larry, do you remember/know more about
> this? I think you were working in this area?
Yes, get_wireless_stats is needed for the device to show up in /proc/net/wireless.
The RFCd patch to add wireless stats to d80211 received only minor comments,
which have all been addressed. I will be submitting a proper patch to Linville's
tree today. In addition, I have reached an agreement with the authors of all
other drivers that use d80211 on a scheme that will implement the stats code for
them as well. Unfortunately, none of them provide such useful quantities as
noise values, but perhaps the prominent FIXMEs will spur action by those who
have detailed device specifications.
Larry
next prev parent reply other threads:[~2006-08-14 12:48 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
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 [this message]
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=44E07116.6060208@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=mbuesch@freenet.de \
--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).