From: Daniel Drake <dsd@gentoo.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: wireless@lists.tuxdriver.org
Subject: Re: SIOCGIWRANGE and dscape
Date: Tue, 30 Jan 2007 19:54:09 -0500 [thread overview]
Message-ID: <45BFE8B1.2070104@gentoo.org> (raw)
In-Reply-To: <9e4733910701301636i18a21f31q421cc7d5c61f6c99@mail.gmail.com>
Jon Smirl wrote:
> 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?
This isn't a small project and is one of the remaining significant
things that some people would like to see before devicescape gets merged.
As you note, drivers do need to inform the stack of basic capabilities,
regulatory domain, supported reg domains, etc. And yes, channel
'databases' and frequency mappings should be stack level or higher.
I don't think there is an answer to your questions at the moment - this
is stuff that needs both designing and implementing. Good luck :)
Daniel
_______________________________________________
wireless mailing list
wireless@lists.tuxdriver.org
http://lists.tuxdriver.org/mailman/listinfo/wireless
next prev parent reply other threads:[~2007-01-31 0:53 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 [this message]
2007-01-31 1:12 ` Michael Wu
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=45BFE8B1.2070104@gentoo.org \
--to=dsd@gentoo.org \
--cc=jonsmirl@gmail.com \
--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).