Skip to content

RDKCOM-5593: RDKBDEV-3446 IPQ Bug Fixes for QCOM#337

Open
VedhaLoganathan wants to merge 1 commit into
rdkcentral:developfrom
VedhaLoganathan:IPQ3
Open

RDKCOM-5593: RDKBDEV-3446 IPQ Bug Fixes for QCOM#337
VedhaLoganathan wants to merge 1 commit into
rdkcentral:developfrom
VedhaLoganathan:IPQ3

Conversation

@VedhaLoganathan

Copy link
Copy Markdown
Contributor

RDKBDEV-3446: IPQ Bug Fixes for QCOM Platform
Reason for change:

  • Captive portal functionality was not working correctly on IPQ devices.
  • Excessive logging was observed on IPQ devices. Logging has been reduced

Test Procedure: Flash the image with fix and test the captive portal functionality in IPQ
Risks: Low

Copilot AI review requested due to automatic review settings June 7, 2026 08:59
@VedhaLoganathan VedhaLoganathan requested review from a team as code owners June 7, 2026 08:59

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR adjusts platform-specific behavior for command logging and partner/default network configuration application, adding special handling for _COSA_QCA_ARM_.

Changes:

  • Suppress vsystem() command logging on _COSA_QCA_ARM_.
  • Treat _COSA_QCA_ARM_ like _RDK_REF_PLATFORM_ for PartnerID selection.
  • Add syscfg_get()-based gating before applying certain network-related partner defaults.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
source/util/utils/util.c Conditionally disables stderr command logging for _COSA_QCA_ARM_.
source/scripts/init/src/apply_system_defaults/apply_system_defaults.c Adds _COSA_QCA_ARM_ PartnerID handling and gates partner default application based on current syscfg values.
Comments suppressed due to low confidence (3)

source/scripts/init/src/apply_system_defaults/apply_system_defaults.c:2544

  • The new gating condition only calls set_syscfg_partner_values() when the current syscfg value already matches the partner/default value (strcmp(...) == 0). That makes these updates effectively a no-op in the typical case where the intent is to apply partner defaults. If the goal is to apply partner values when they differ, the comparison should be inverted (apply when strcmp(...) != 0). If the goal is instead “only apply when the device is still at factory defaults”, this should compare against the known factory default (or “unset”/missing key state) rather than comparing current value to the partner value being applied.
						defaultAdminIP = paramObjVal->valuestring; 
						syscfg_get( NULL, "lan_ipaddr", buf, sizeof( buf ));
					
						if ((defaultAdminIP != NULL) && (strcmp(buf, defaultAdminIP) == 0))
						{
							set_syscfg_partner_values(defaultAdminIP,"lan_ipaddr");
							defaultAdminIP = NULL;
						}	

source/scripts/init/src/apply_system_defaults/apply_system_defaults.c:2561

  • The new gating condition only calls set_syscfg_partner_values() when the current syscfg value already matches the partner/default value (strcmp(...) == 0). That makes these updates effectively a no-op in the typical case where the intent is to apply partner defaults. If the goal is to apply partner values when they differ, the comparison should be inverted (apply when strcmp(...) != 0). If the goal is instead “only apply when the device is still at factory defaults”, this should compare against the known factory default (or “unset”/missing key state) rather than comparing current value to the partner value being applied.
						subnetRange = paramObjVal->valuestring; 
						syscfg_get( NULL, "lan_netmask", buf, sizeof( buf ));
					
						if ((subnetRange != NULL) && (strcmp(buf, subnetRange) == 0))
						{
							set_syscfg_partner_values(subnetRange,"lan_netmask");
							subnetRange = NULL;
						}	

source/scripts/init/src/apply_system_defaults/apply_system_defaults.c:2577

  • The new gating condition only calls set_syscfg_partner_values() when the current syscfg value already matches the partner/default value (strcmp(...) == 0). That makes these updates effectively a no-op in the typical case where the intent is to apply partner defaults. If the goal is to apply partner values when they differ, the comparison should be inverted (apply when strcmp(...) != 0). If the goal is instead “only apply when the device is still at factory defaults”, this should compare against the known factory default (or “unset”/missing key state) rather than comparing current value to the partner value being applied.
						minAddress = paramObjVal->valuestring;
						syscfg_get( NULL, "dhcp_start", buf, sizeof( buf ));

						if ((minAddress != NULL) && (strcmp(buf, minAddress) ==0))
						{
							set_syscfg_partner_values(minAddress,"dhcp_start");
							minAddress = NULL;
						}

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 2586 to 2591
maxAddress = paramObjVal->valuestring;
syscfg_get( NULL, "dhcp_end", buf, sizeof( buf ));

if (maxAddress != NULL)
if ((maxAddress != NULL) && (strcmp(buf, maxAddress) == 0))
{
set_syscfg_partner_values(maxAddress,"dhcp_end");
cJSON *alwaysParamObjVal = NULL;
char *error_ptr = NULL;
int iterator = 0;
char buf[50] = {0};
Comment thread source/util/utils/util.c
Comment on lines +69 to +71
#ifndef _COSA_QCA_ARM_
fprintf(stderr, "%s: %s\n", __FUNCTION__, cmd);
#endif
@pradeeptakdas pradeeptakdas changed the title IPQ Bug Fixes for QCOM RDKBDEV-3446: RDKCOM-5593 IPQ Bug Fixes for QCOM Jun 8, 2026
@pradeeptakdas pradeeptakdas changed the title RDKBDEV-3446: RDKCOM-5593 IPQ Bug Fixes for QCOM RDKCOM-5593: RDKBDEV-3446 IPQ Bug Fixes for QCOM Jun 8, 2026
@AkhilaReddyK7 AkhilaReddyK7 added the community-contribution Contribution from community label Jun 15, 2026
Signed-off-by: VedhaLoganathan <vedhaval@qti.qualcomm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-contribution Contribution from community

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants