From: Michael Wu <flamingice@sourmilk.net>
To: wireless@lists.tuxdriver.org
Subject: Re: SIOCGIWRANGE and dscape
Date: Tue, 30 Jan 2007 20:12:19 -0500 [thread overview]
Message-ID: <200701302012.23302.flamingice@sourmilk.net> (raw)
In-Reply-To: <9e4733910701301636i18a21f31q421cc7d5c61f6c99@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1558 bytes --]
On Tuesday 30 January 2007 19:36, Jon Smirl wrote:
> Looking in ieee80211_ioctl.c the implementation is in
> ieee80211_ioctl_giwrange().
>
> I can work on this, but how should it be done? There is no callout
> from the stack to the drivers for this IOCTL. It also doesn't make
> sense that each driver have the code to build the entire channel
> lists. But you do need to know whether the driver is b/g or a/b/g. How
> does the driver indicate which channel domain it is in, Japan/US/EU?
>
Fixing up giwrange is currently on my d80211 blockers todo list since it is
part of fixing wireless statistics reporting in d80211. Helper functions for
filling the channel lists is also somewhere on the todo list, though it isn't
on the blocker list. The driver currently has no way to indicate what
regulatory domain the hardware has stored in eeprom, and d80211 just assumes
FCC. (after all, d80211 isn't merge ready yet ;) Yes, basic driver regulatory
domain support is on my blocker todo list.
Listing rates and channels in giwrange should be easy - find the current mode,
and iterate through the list of channels and rates in there. Ignore any
channels which are not enabled. Count up all the enabled channels and stick
it in num_channels and num_frequency. I could probably just copy the code
from the adm8211 (wireless-2.6 version) giwrange handler and modify it to
traverse lists instead of arrays. Feel free to hack and submit a patch though
- it's not like I don't have enough things on my todo list. :)
-Michael Wu
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
wireless mailing list
wireless@lists.tuxdriver.org
http://lists.tuxdriver.org/mailman/listinfo/wireless
next prev parent reply other threads:[~2007-01-31 1:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 0:36 SIOCGIWRANGE and dscape Jon Smirl
2007-01-31 0:54 ` Daniel Drake
2007-01-31 1:12 ` Michael Wu [this message]
2007-01-31 2:52 ` Jouni Malinen
2007-01-31 3:11 ` Jon Smirl
2007-01-31 3:21 ` Michael Wu
2007-01-31 3:23 ` Pavel Roskin
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=200701302012.23302.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=wireless@lists.tuxdriver.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).