From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Ravi Sharma <sharmaravi.lx@gmail.com>
Cc: Sunil Mehta <sunil2@telenetsystems.com>,
"John W. Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>, <Mohammed@venema.h4ckr.net>,
Rodriguez Luis <rodrigue@qca.qualcomm.com>,
<ath9k-devel@lists.ath9k.org>,
Felix Bitterli <felixb@qca.qualcomm.com>
Subject: Re: [ath9k-devel] :
Date: Mon, 24 Sep 2012 10:45:50 +0530 [thread overview]
Message-ID: <505FEC86.7020201@qca.qualcomm.com> (raw)
In-Reply-To: <CAEZZmbG78oO5_D3zncanXStYpuf_faoqq6rp3usPpd3_5+tBQA@mail.gmail.com>
Hi Ravi,
I was on leave, will soon share the complete data that might help you..
p2p concurrency (having P2P go has some issues).
regards,
shafi
On Thursday 20 September 2012 04:07 PM, Ravi Sharma wrote:
> Hi,
>
> I am trying to setup concurrent mode for TL-WL722N (TP-LINK) (ath9k)
> and upgraded& used the driver with the latest compat release. I am
> trying to run STA & P2P concurrently with two supplicant. Is this
> configuration possible?
>
>
>
> I am using Ubuntu with kernel 3.2
>
> Can you please share the setup you are using to validate the ath9k
> mac80211 for concurrent mode?
>
> Regards,
> Ravi
>
> On Tue, Aug 21, 2012 at 10:43 AM, Mohammed Shafi Shajakhan
> <mohammed@qca.qualcomm.com> wrote:
>> Hi,
>>
>>
>> On Friday 17 August 2012 12:42 PM, Sunil Mehta wrote:
>>>>
>>>>
>>>> Hi
>>>
>>>
>>> We are using AR9331 and are currently using the device in - AP mode, and
>>> Station mode.
>>>
>>> We would like to use the device for a P2P application. Can you suggest
>>> what we need to do.
>>
>>
>> sorry for the delayed reply, i was on leave(did not check any mails!) for
>> the past 6 days.
>>
>> please read this and check this out, if it helps and works for you
>> http://linuxwireless.org/en/developers/p2p/howto.
>>
>> please let me know if there any basic configuration issues.
>>
>> technical issues related to p2p are discussed in hostap mailing lists
>> http://lists.shmoo.com/mailman/listinfo/hostap
>>
>>
>>
>>>
>>> Regards,
>>> Sunil.
>>>
>>>
>>
>>
>> --
>> thanks,
>> shafi
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
thanks,
shafi
next prev parent reply other threads:[~2012-09-24 5:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 6:28 [PATCH] ath9k: Add PID/VID support for AR1111 Mohammed Shafi Shajakhan
2012-08-02 17:43 ` Luis R. Rodriguez
[not found] ` <CAAT9HshKC9+YiP2YzVGO_nuRsyvbgBeUvj2+r2Wzj1wU-QV7-A@mail.gmail.com>
2012-08-02 18:13 ` John W. Linville
[not found] ` <CAAT9HsjQ9abXWEy4Jp86HH9HUEOhSbQG_jn2Hnwk8_QX=oqfag@mail.gmail.com>
2012-08-06 5:50 ` Mohammed Shafi Shajakhan
2012-08-17 7:12 ` [ath9k-devel] : Sunil Mehta
2012-08-21 5:13 ` Mohammed Shafi Shajakhan
2012-09-20 10:37 ` Ravi Sharma
2012-09-24 5:15 ` Mohammed Shafi Shajakhan [this message]
2012-09-24 14:40 ` Mohammed Shafi
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=505FEC86.7020201@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=Mohammed@venema.h4ckr.net \
--cc=ath9k-devel@lists.ath9k.org \
--cc=felixb@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=sharmaravi.lx@gmail.com \
--cc=sunil2@telenetsystems.com \
/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).