ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Denton Gentry <denton.gentry@gmail.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Firmware crash w/ 10.2 diagnosis?
Date: Wed, 10 Sep 2014 18:26:52 +0300	[thread overview]
Message-ID: <8761gv7ayr.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CABnBrYV6MSw1LgcgbL4O4sgR0K_P-9jCMEhOvMDmPt8yw2UeXQ@mail.gmail.com> (Denton Gentry's message of "Tue, 9 Sep 2014 13:05:21 -0700")

Denton Gentry <denton.gentry@gmail.com> writes:

> I'm using backports, and the kernel version is 3.2.
> hostapd says it is indeed using the cooked monitor:
>
>     monitor mode needed: 1 (poll_cmd=1 data_tx_status=0)
>
> I'll look at updating the kernel, if not to 3.16 then at least to
> something recent enough to stop using the monitor interface from
> hostapd.

Good. But if you use bridging the monitor vdev is created anyway. So
most likely switching to nl80211 management frame interface is not going
to workaround the firmware bug.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      reply	other threads:[~2014-09-10 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 20:56 Firmware crash w/ 10.2 diagnosis? Denton Gentry
2014-09-08  6:28 ` Michal Kazior
2014-09-08 12:42   ` Denton Gentry
2014-09-09 12:08     ` Kalle Valo
2014-09-09 12:48       ` Michal Kazior
2014-09-09 20:05         ` Denton Gentry
2014-09-10 15:26           ` Kalle Valo [this message]

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=8761gv7ayr.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=denton.gentry@gmail.com \
    --cc=michal.kazior@tieto.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