ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sven Eckelmann <sven@open-mesh.com>
Cc: simon@open-mesh.com, openwrt-devel@lists.openwrt.org,
	ath10k@lists.infradead.org, Matti Laakso <malaakso@elisanet.fi>
Subject: Re: [PATCH 0/2] Initial 11ac support using ath10k
Date: Sat, 18 Jan 2014 11:14:28 +0200	[thread overview]
Message-ID: <878uudps7f.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87mwitpsmn.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Sat, 18 Jan 2014 11:05:20 +0200")

(resending my mail due to a stupid rule in ath10k-devel, I need to be
subcribed before posting to that list)

Hi Sven,

adding ath10k@lists.infradead.org.

Sven Eckelmann <sven@open-mesh.com> writes:

> Hi,
>
> support for ath10k cards was added a while ago to OpenWrt. Unfortunately, the 
> actual 802.11ac support was never added (patches on the mailing lists were 
> just ignored). This is a rather unpleasant situation when trying to get some 
> 11ac test hardware working.

Yeah, it would be great to get proper ath10k support to OpenWrt. Thanks
for working on this!

> I've picked up the patches and rebased them on top of the current master 
> branch/trunk.

Where did you take the ath10k patches? ath10k is under heavy
development, so I strongly recommend taking patches directly from
ath-next branch of my ath.git. That way you would be using the latest
and greatest.

> Just as general information to the state of ath10k, my current test showed 
> some problems with it:
>
>  * Samsung GT-I9300 only got horrible slow connections to an QCA9880 but
>    an Intel N6205 (using iwlwifi from v3.12) or Samsung S4 worked
>    "fine"

Could you report the I9300 issue to the ath10k list with more details,
please? We can try to investigate it.

>  * Adhoc mode doesn't work at all

That was with 10.1 firmware? AFAIK it doesn't support adhoc at all. I
think we need to add a firmware feature flag to disable adhoc with that
firmware.

>  * TX bitrate information is bogus (iw XXX station dump)

Yeah, this is annoying. But firmware doesn't report this to the host at
all so there is not much ath10k can do right now. But I'll send a query
to the firmware team if they could provide that information to ath10k.

>  * Crashed relative often on reconfiguration:
>    Data bus error, epc 87b7a864, ra 87b7a864

On some QCA988x boards cold reset seems to cause problems on the PCI
bus. We are investigating this.

>  * Sometimes adding of station seems to fail:
>    ath10k: Failed to add peer 5c:0a:5b:4e:6a:c4 for vdev 1 when adding a new
>    sta: -145

This is new to me. Can you report this to the ath10k list, please?

>  * Adhoc interface +  "iw dev wlan0 scan trigger" just crashes the firmware:
>    [ 296.160000] ath10k: firmware crashed!
>    [ 296.170000] ath10k: hardware name qca988x hw2.0 version 0x4100016c
>    [ 296.170000] ath10k: firmware version: 65.467.0.0

What firmware version was this? The version printed here seems to be
corrupted.

-- 
Kalle Valo

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

  reply	other threads:[~2014-01-18  9:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1513091.zjVOOQ7NvD@bentobox>
2014-01-18  9:05 ` [PATCH 0/2] Initial 11ac support using ath10k Kalle Valo
2014-01-18  9:14   ` Kalle Valo [this message]
2014-01-20  9:33     ` Yeoh Chun-Yeow
2014-01-20 10:29     ` Sven Eckelmann
2014-01-27 14:19       ` Kalle Valo

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=878uudps7f.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=malaakso@elisanet.fi \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=simon@open-mesh.com \
    --cc=sven@open-mesh.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