All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath10k@lists.infradead.org, Matti Laakso <malaakso@elisanet.fi>
Subject: Re: fetching calibration data from flash
Date: Tue, 10 Jun 2014 08:56:01 -0700	[thread overview]
Message-ID: <53972A91.1080600@candelatech.com> (raw)
In-Reply-To: <87sindb0gj.fsf@kamboji.qca.qualcomm.com>

On 06/10/2014 02:03 AM, Kalle Valo wrote:
> Matti Laakso <malaakso@elisanet.fi> writes:
> 
>>> But why let the user name provide the file name? Why cannot it be a
>>> fixed name, like "cal.bin"?
> 
> s/user name/user space/
> 
>> If there are multiple WNICs each with its own calibration data?
> 
> Ah, of course.


Another nice feature would be to allow configuring the number of
vdevs, peers, etc per NIC.  That way, you could have one NIC
tuned to be one big AP with lots of peers, and a second could
be several small APs with fewer peers and some stations, etc.

Maybe this could be a separate file, or maybe it would be worth
adding this to a TLV type file with cal.bin being part of the
data?

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-06-10 15:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  7:55 fetching calibration data from flash Sven Schnelle
2014-06-10  8:28 ` Kalle Valo
2014-06-10  8:32   ` Sven Schnelle
2014-06-10  8:36 ` Matti Laakso
2014-06-10  8:54   ` Kalle Valo
2014-06-10  8:59     ` Matti Laakso
2014-06-10  9:03       ` Kalle Valo
2014-06-10 15:56         ` Ben Greear [this message]
2014-06-11  8:38           ` Kalle Valo
2014-06-11 13:40             ` Ben Greear
2014-06-16 12:24               ` Kalle Valo
2014-06-16 14:53                 ` Ben Greear
2014-06-16 15:28                   ` Kalle Valo
2014-06-16 15:58                     ` 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=53972A91.1080600@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    --cc=malaakso@elisanet.fi \
    /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.