From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ] tools/mesh-cfgclient: Increase app's CRPL size
Date: Wed, 18 Mar 2020 18:17:01 +0000 [thread overview]
Message-ID: <62e46a6ceb7c2913b0a857e0c3d10e327ed6340f.camel@intel.com> (raw)
In-Reply-To: <20200318174859.27387-1-inga.stotland@intel.com>
Applied
On Wed, 2020-03-18 at 10:48 -0700, Inga Stotland wrote:
> This increases the value of the CRPL supplied by the applicaiton
> to 0x7fff: since the tool is intended to be a provisioner and config
> client, it may have to keep track of communications with a significant
> number of unique mesh nodes, each with its corresponding CRPL entry in
> config client node storage. Therefore, a large CRPL size is necessary.
> ---
> tools/mesh-cfgclient.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/mesh-cfgclient.c b/tools/mesh-cfgclient.c
> index e4523e5fc..ae13c4409 100644
> --- a/tools/mesh-cfgclient.c
> +++ b/tools/mesh-cfgclient.c
> @@ -57,6 +57,7 @@
> #define DEFAULT_START_ADDRESS 0x00aa
> #define DEFAULT_MAX_ADDRESS (VIRTUAL_ADDRESS_LOW - 1)
> #define DEFAULT_NET_INDEX 0x0000
> +#define MAX_CRPL_SIZE 0x7fff
>
> #define DEFAULT_CFG_FILE "config_db.json"
>
> @@ -122,7 +123,7 @@ static struct meshcfg_app app = {
> .cid = 0x05f1,
> .pid = 0x0002,
> .vid = 0x0001,
> - .crpl = 10,
> + .crpl = MAX_CRPL_SIZE,
> .ele = {
> .path = "/mesh/cfgclient/ele0",
> .index = 0,
prev parent reply other threads:[~2020-03-18 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 17:48 [PATCH BlueZ] tools/mesh-cfgclient: Increase app's CRPL size Inga Stotland
2020-03-18 18:17 ` Gix, Brian [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=62e46a6ceb7c2913b0a857e0c3d10e327ed6340f.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).