ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Performance of ath10k
Date: Fri, 14 Mar 2014 11:18:08 +0200	[thread overview]
Message-ID: <87siql87fz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <EE97821C81277E459BEA5C6384C6F241012D6392146C@srvexch01.SODIELEC.local> (Vu Hai NGUYEN's message of "Fri, 14 Mar 2014 10:05:21 +0100")

Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> writes:

> I'm doing an internship for6 month and my mission is implementation a
> module of 802.11ac in a mini cpu to create an access point of wifi.
> After looking in the internet for a while, I found this potential
> product from Compex:
> http://www.compex.com.sg/productdetailinfo.asp?model=WLE900VX I wonder
> if is there anyone here have tried this with the driver ath10k and
> does it work well or there's still many bugs?

FWIW I'm using ath10k on my main AP at home on 5G (and ath9k on 2.4G)
and I haven't recently had any major problems preventing use. The uptime
right now is:

11:15:46 up 17 days, 16:39,  load average: 0.13, 0.11, 0.13

But as I'm the ath10k maintainer I'm biased :) 

-- 
Kalle Valo

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

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14  9:05 Performance of ath10k Vu Hai NGUYEN
2014-03-14  9:18 ` Kalle Valo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-14  9:54 Trevor Cullen
2014-03-14 10:34 ` Kalle Valo
2014-03-15  1:45   ` Yeoh Chun-Yeow
2014-03-15  7:50     ` Kalle Valo
2014-03-14 21:34 ` Ben Greear

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=87siql87fz.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=vh.nguyen@actiasodielec.fr \
    /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