All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: CT firmware available with management-over-HTT (tested)
Date: Tue, 28 Jul 2015 10:18:38 -0700	[thread overview]
Message-ID: <55B7B96E.5020804@candelatech.com> (raw)

For those interested, I have uploaded a new beta build (version 15)
that enables management frames over the normal HTT transport.  This
has now been tested, and some bugs in the original attempt have been
fixed.

One user reports that the 'wmi timeout' issues have been resolved
by this patch.

Basic AP, Station, and IBSS testing has been completed
successfully.

This requires a driver patch...see the release notes for a link to
the patch.  Our 4.0 kernel has been patched.  3.17 has not.  And, for
4.2 and similar kernels, you need a somewhat different patch than what
we have in 4.0.  In general, HTT-MGT frames on CT firmware should
take the exact same path as data frames (native-wifi type, use-fragments).
HTT version is '2.2' for HTT-MGT CT firmware, so you can use that to check
to enable CT HTT-MGT path or not.

# Release notes
http://www.candelatech.com/downloads/ath10k-fw-beta/release_notes.txt

# Firmware binary
http://www.candelatech.com/downloads/ath10k-fw-beta/firmware-2-ct-full-htt-mgt-community.bin

I'd be curious to know the results if anyone gives this a try.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


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

                 reply	other threads:[~2015-07-28 17:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=55B7B96E.5020804@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.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.