From: Johannes Berg <johannes@sipsolutions.net>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: Oleksij Rempel <linux@rempel-privat.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [BUG] P2P setup timeout
Date: Mon, 16 Dec 2013 16:15:12 +0100 [thread overview]
Message-ID: <1387206912.2057.25.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CANq1E4S+u6UZf15fU9aO6JvY4OTE+RnOKGL0K16T9A_4vr+C6A@mail.gmail.com> (sfid-20131216_160940_365143_3C2C01EE)
On Mon, 2013-12-16 at 16:09 +0100, David Herrmann wrote:
> Thanks, I tracked down the ENETDOWN. I'm not entirely sure but I think it's:
Obviously :)
> @Oleksij, I actually have three ath9k-htc devices so I'd like to get
> this working, and the devices are really nice apart from this bug. I
> will keep you up to date, but if you have any hints where to continue
> digging, lemme know. Until it's fixed, I'll just work on
> wired-displays via ethernet instead of wifi-displays..
Based on what Oleksij said, these issues are likely not even related -
maybe ath9k_htc can't even set the rates to exclude CCK, so even if that
call were to succeed it wouldn't work?
The issue here doesn't seem to be that call anyway, since that call was
for the data frames on the p2p-wlan1-0 interface, but rather seems to be
that ath9k_htc ignores the no-CCK parameter for the NL80211_CMD_FRAME
command (in mac80211, this would be IEEE80211_TX_CTL_NO_CCK_RATE)
johannes
next prev parent reply other threads:[~2013-12-16 15:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 10:18 [BUG] P2P setup timeout David Herrmann
2013-12-09 14:03 ` Oleksij Rempel
2013-12-09 14:30 ` David Herrmann
2013-12-16 12:00 ` David Herrmann
2013-12-16 12:36 ` Johannes Berg
2013-12-16 13:39 ` David Herrmann
2013-12-16 13:45 ` Johannes Berg
2013-12-16 13:51 ` David Herrmann
2013-12-16 14:57 ` Oleksij Rempel
2013-12-16 15:09 ` David Herrmann
2013-12-16 15:15 ` Johannes Berg [this message]
2013-12-16 15:26 ` Oleksij Rempel
2013-12-16 15:29 ` Johannes Berg
2013-12-16 15:37 ` Oleksij Rempel
2013-12-16 15:53 ` David Herrmann
2013-12-17 5:50 ` Ujjal Roy
2013-12-17 7:19 ` Johannes Berg
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=1387206912.2057.25.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.org \
--cc=dh.herrmann@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
/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).