From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: Wireless statistics for bcm43xx-d80211
Date: Wed, 19 Jul 2006 14:42:01 -0500 [thread overview]
Message-ID: <44BE8B09.3080107@lwfinger.net> (raw)
In-Reply-To: <1153317379.2537.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Dan Williams wrote:
>
> Actually, now that I think about it, why are _any_ applets
> screen-scraping /proc/net/wireless anymore? If they profess to be a
> wireless applet, yet screenscrape /proc/net/wireless, that's suspect
> right there. The ioctls for status are quite well-defined and haven't
> changed in a very long time (ie, SIOCGIWRANGE).
>
> On the flip side, /proc/net/wireless has been supported since the dawn
> of time (ok, not really) and is the textual interface for reporting
> wireless statistic, but maybe that shouldn't be the case anymore.
>
I finally found the source for the applet, and it is using iwlib to get the statistics. If the
kernel's version of WE is really old, it will use /proc/net/wireless. For newer kernels, it is using
the appropriate ioctl. When I get time, I will fix the error and submit a patch to KDE.
As an interim workaround, I downloaded and built kwlaninfo, a different KDE kicker applet. I don't
like it very much but it does show the needed info.
Larry
prev parent reply other threads:[~2006-07-19 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 4:24 Wireless statistics for bcm43xx-d80211 Larry Finger
2006-07-19 11:13 ` Dan Williams
[not found] ` <44BDB400.40408-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-07-19 12:59 ` Michael Buesch
2006-07-19 13:56 ` Dan Williams
[not found] ` <1153317379.2537.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-07-19 19:42 ` Larry Finger [this message]
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=44BE8B09.3080107@lwfinger.net \
--to=larry.finger-tq5ms3gmjblk1umjsbkqmq@public.gmane.org \
--cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.