From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k@lists.infradead.org, Matti Laakso <malaakso@elisanet.fi>
Subject: Re: fetching calibration data from flash
Date: Mon, 16 Jun 2014 18:28:33 +0300 [thread overview]
Message-ID: <87a99c27ry.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <539F04E2.9090807@candelatech.com> (Ben Greear's message of "Mon, 16 Jun 2014 07:53:22 -0700")
Ben Greear <greearb@candelatech.com> writes:
> I also think that we will want to be able to configure firmware on
> a per-nic basis instead of per-machine. If we did that, we could poke
> any special config into the firmware images using the existing meta-data
> api. Should be easy enough to write a small program that prepended
> the config to a generic firmware..then those that care can create their
> own customized firmware images quickly and easily.
That's still essentially an ini file, just using a binary format hidden
inside the firmware image. The firmware meta data is for advertising
capabilities of the firmware binary so that ath10k choose correct
settings to run the binary, not for delivering configuration settings
from user space.
If we would start providing driver settings from firmware binaries that
would just confuse anyone.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-06-16 15:29 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
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 [this message]
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=87a99c27ry.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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.