From: Hui Yang <busydog0104@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] virtual interface with multiple channels in ath9k
Date: Thu, 15 Sep 2016 00:58:19 +0800 [thread overview]
Message-ID: <CAMQ0-Ems0RUf9tYxsZET62x-kGee_-fywr-nrE5L-XEzHCX7=w@mail.gmail.com> (raw)
Hi.
I want to do an experiment using virtual interfaces to connect multiple
wireless channel. But I can only connect to the same channel.
I find the ath9k driver supported multiple channel in the past from this
http://osdir.com/ml/linux-wireless/2009-03/msg00090.html.
But I can not get the past source code of ath9k.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20160915/7cb69e1b/attachment.htm
next reply other threads:[~2016-09-14 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 16:58 Hui Yang [this message]
2016-09-14 17:16 ` [ath9k-devel] virtual interface with multiple channels in ath9k Ben Greear
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='CAMQ0-Ems0RUf9tYxsZET62x-kGee_-fywr-nrE5L-XEzHCX7=w@mail.gmail.com' \
--to=busydog0104@gmail.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).