Bug 12903 - [yocto] Kernel config incremental modification not working for yocto-imx
Summary: [yocto] Kernel config incremental modification not working for yocto-imx
Status: RESOLVED OBSOLETE
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: Other arm
: Medium normal
Target Milestone: 2.7
Assignee: Otavio Salvador
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-08-28 06:20 UTC by Sagar
Modified: 2019-05-30 15:20 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sagar 2018-08-28 06:20:15 UTC 
I am working on a project based on the imx7dsabresd board. I've configured and the built the yocto for recipe core-image-minimal-dev. Which works fine. 
Now I needed to add modifications for kernel and configurations for Quectel EC25 module.

I followed instructions from https://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#configuring-the-kernel

My linux-imx_4.1.15.bbappend looks like this

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

SRC_URI += "file://0001-Add-Quectel-EC25-USB-Serial-Driver-Support.patch \
            file://usb_serial.cfg"

Both .path and .cfg are located under meta-quectel-community/recipes-kernel/linux.

When I do bitbake -c cleansstate linux-imx and build the kernel again with bitbake linux-imx only 0001-Add-Quectel-EC25-USB-Serial-Driver-Support.patch patch is getting applied but configuration changes in usb_serial.cfg are getting ignored.

I saw similar issue reported https://lists.yoctoproject.org/pipermail/yocto/2016-December/033475.html but the solutions didn't help me. 

Can you help me with a proper way to change the kernel configurations with linux-imx image?
Comment 1 Randy MacLeod 2019-05-30 15:20:11 UTC 
imx issue need to be reported on the appropriate github page now.