All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harshal Vora <harshal@amideeptech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Adhoc mode and chip reset issue with tp link wn721n/ath9k_htc drivers
Date: Mon, 31 Mar 2014 14:40:44 +0530	[thread overview]
Message-ID: <53393114.8080306@amideeptech.com> (raw)
In-Reply-To: <533925BA.6000007@rempel-privat.de>

Hi Oleksij,

I compared the initial few commits from wireless-testing repo with 
3.13.y branch of raspberry linux git repo. Seems like all of those have 
been merged.

I also specifically checked commits only for 
/drivers/net/wireless/ath/ath9k folder and seems like they are also 
present in the raspberry linux repo.

So I assume all the changes should be there.

If issues persist, then I will test with the wireless-testing repo as well.

Thanks,
Regards,

On 03/31/2014 01:52 PM, Oleksij Rempel wrote:
> Am 31.03.2014 10:06, schrieb Harshal Vora:
>> Hi Oleksij,
>>
>> We will test with kernel version 3.13.7 and also the latest firmware.
> I assume we misunderstand each other. FW will work with older kernel
> versions and some bugs are fixed in 3.13. But only wireless-testing.git
> can detect some FW oopses, and has  changes which may affect AdHock mode.
> I recommend you to use wireless-testing.git or at least try to
> cherry-peak this changes.
>

  reply	other threads:[~2014-03-31  9:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29 10:17 [ath9k-devel] Adhoc mode and chip reset issue with tp link wn721n/ath9k_htc drivers Harshal Vora
2014-03-30  7:31 ` Oleksij Rempel
2014-03-31  5:41   ` Harshal Vora
2014-03-31  7:19     ` Oleksij Rempel
2014-03-31  8:06       ` Harshal Vora
2014-03-31  8:22         ` Oleksij Rempel
2014-03-31  9:10           ` Harshal Vora [this message]
2014-04-04 12:37             ` Harshal Vora
2014-04-04 12:59               ` Oleksij Rempel
2014-04-19 11:49                 ` Harshal Vora
2014-04-19 19:42                   ` Oleksij Rempel

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=53393114.8080306@amideeptech.com \
    --to=harshal@amideeptech.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 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.