All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Re: New CT firmware release is uploaded.
Date: Thu, 31 Jul 2014 14:29:43 -0700	[thread overview]
Message-ID: <53DAB547.3030700@candelatech.com> (raw)
In-Reply-To: <53CD9C08.9090908@candelatech.com>

I've put up a new version (010) that fixes a crash bug in the 009
release.  64 stations (vdevs) have been fairly well tested at
this point (using my 3.14.14+ kernel).

http://www.candelatech.com/ath10k.php

Thanks,
Ben


On 07/21/2014 04:02 PM, Ben Greear wrote:
> Release notes:
> 
>       Improve RAM usage:  Re-organized, trimmed, and otherwise made better use
>       of RAM.  Allow compiling out swbmiss, beacon filtering, roaming code.
>       Images with 'full' in their name do NOT have the previously mentioned features
>       compiled out.
> 
>       Over-all, freed up about 80k of extra RAM, which can be used for more vdevs,
>       peers, buffers, etc.
> 
>       Supports 64 vdevs (one should be reserved for monitor interface, so
>       effectively 63 vdevs for current kernels.)
> 
> I have only lightly tested this on my 3.14 kernel so far.
> 
> A lot of these changes could potentially introduce run-time
> crashes due to extensive use of a different type of RAM for
> storing many structures.  Should be a quick fix should problems
> arise.
> 
> As always, let me know if you find any problems.
> 
> 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:[~2014-07-31 21:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 23:02 New CT firmware release is uploaded Ben Greear
2014-07-31 21:29 ` Ben Greear [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=53DAB547.3030700@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.