ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Ben Greear <greearb@candelatech.com>, ath10k@lists.infradead.org
Subject: Re: request: ACK timing setting required
Date: Mon, 25 May 2015 22:31:34 +0200	[thread overview]
Message-ID: <556386A6.4050908@dd-wrt.com> (raw)
In-Reply-To: <556378E3.7050707@candelatech.com>

Am 25.05.2015 um 21:32 schrieb Ben Greear:
>
>
> On 05/25/2015 12:21 PM, Sebastian Gottschall wrote:
>> Am 25.05.2015 um 19:53 schrieb Ben Greear:
>>>
>>>
>>> On 05/25/2015 10:48 AM, Sebastian Gottschall wrote:
>>>> Am 25.05.2015 um 19:13 schrieb Ben Greear:
>>>>>
>>>>>
>>>>> On 05/25/2015 10:10 AM, Sebastian Gottschall wrote:
>>>>>> Hello
>>>>>>
>>>>>> could it be possible to add a ACK timing feature to the ath10k 
>>>>>> firmware (QCA9880 internal register 0x8014, mask 0x3FFF)
>>>>>
>>>>> You just need ability to set this register to some value?
>>>>>
>>>>> If so, probably something I could add to CT firmware, at least.
>>>>>
>>>> not alone. this register is rewritten on each reset (channel change 
>>>> etc.) so it needs to be correct handled.
>>>> yes. just writing and handling the ack value would be enough. the 
>>>> math behind is no problem.
>>>> otherwise its impossible todo long range links with ath10k. (LSDK 
>>>> based firmware from compex do support this feature unlike ath10k)
>>>
>>> I'll see if I can add this to my firmware, probably will be a few 
>>> days before I can get
>>> time to work on it.  Will post to list when I have a FW build ready 
>>> for testing.
>> do you plan to bring up your codebase to 10.2.4 with api 5 one time?
>> or is the code already up to date, just using the old api?
>
> I'm having a slow time getting updated source from QCA, but I plan to
> move to a newer code base when I can get access.
>
> For now, my firmware is based on 10.1.467, but it has quite a bit of 
> improvements
> and changes.  It does not support some of the newer chipsets that 
> newer QCA
> firmware supports.
as soon as i have seen each new chipset has a own firmware. the standard 
firmware will only support AR9880 v2.
since i'm only working on embedded devices which are only running on 
AR9880 v2 based chipsets, this isnt a big issue

Sebastian
>
> Thanks,
> Ben
>
>


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

  reply	other threads:[~2015-05-25 20:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 12:45 [PATCH] amth10k: fix promisc handling Michal Kazior
2015-05-21  5:40 ` Michal Kazior
2015-05-21  7:40   ` Kalle Valo
2015-05-25 12:25     ` Kalle Valo
2015-05-25 17:10       ` request: ACK timing setting required Sebastian Gottschall
2015-05-25 17:13         ` Ben Greear
2015-05-25 17:48           ` Sebastian Gottschall
2015-05-25 17:53             ` Ben Greear
2015-05-25 19:21               ` Sebastian Gottschall
2015-05-25 19:32                 ` Ben Greear
2015-05-25 20:31                   ` Sebastian Gottschall [this message]
2015-05-25 21:26                   ` possible memory leak or memory waste Sebastian Gottschall
2015-05-25 22:39                     ` Ben Greear
2015-05-25 23:00                       ` Sebastian Gottschall
2015-05-25 23:42                         ` Ben Greear
2015-05-26  0:07                           ` Sebastian Gottschall
2015-05-26  5:42                             ` Michal Kazior
2015-05-26  6:20                               ` Rajkumar Manoharan
2015-05-26  7:26                                 ` Sebastian Gottschall
2015-05-26  7:23                               ` Sebastian Gottschall
2015-05-26  8:26                                 ` Michal Kazior
2015-05-26  8:37                                   ` Sebastian Gottschall
2015-05-26  9:21                                     ` Michal Kazior
2015-05-26 11:19                                       ` Sebastian Gottschall
2015-05-27 10:25       ` [PATCH] amth10k: fix promisc handling 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=556386A6.4050908@dd-wrt.com \
    --to=s.gottschall@dd-wrt.com \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.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