From: Rodolphe Marques <rodolphe.marques@ua.pt>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k-deve: add / delete virtual wiphys through iw (nl80211)
Date: Wed, 05 May 2010 15:27:34 +0100 [thread overview]
Message-ID: <4BE18056.6010809@ua.pt> (raw)
In-Reply-To: <1273069270.27891.16.camel@jm-laptop>
Hi Jouni,
That means that from the OS perspective we would see only one interface
and that the mac80211 would that care of multiple associations in order
to improve overall throughput?
Best Regards,
Rodolphe Marques
On 05/05/2010 03:21 PM, Jouni Malinen wrote:
> On Wed, 2010-05-05 at 02:28 -0700, "Lorna Gonz?lez" wrote:
>
>> according to the nl80211_commands it is possible to add, get, set and delete wiphy using iw command like using debugfs ath9k/phy#/wiphy am I right? But I can?t use and don?t have this options in my supported commands (iw phy<name> info).
>> Does any one knows what could be the reason?
>>
> There is currently no support for managing virtual wiphys in nl80211 (or
> iw for that matter). The current design in ath9k is experimental and at
> this point, it does not look likely that it would be standardized via
> nl80211 in this way. In other words, it is more likely that the vif
> concept in mac80211 would get extended to support multi-channel
> operations which would eventually remove need for the virtual wiphy
> concept.
>
> - Jouni
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
next prev parent reply other threads:[~2010-05-05 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 9:28 [ath9k-devel] ath9k-deve: add / delete virtual wiphys through iw (nl80211) "Lorna González"
2010-05-05 14:21 ` Jouni Malinen
2010-05-05 14:27 ` Rodolphe Marques [this message]
2010-05-05 14:39 ` Jouni Malinen
2010-05-21 11:45 ` [ath9k-devel] ath9k-deve: about the scheduler in virtual radios "Lorna González"
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=4BE18056.6010809@ua.pt \
--to=rodolphe.marques@ua.pt \
--cc=ath9k-devel@lists.ath9k.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.