| Summary: | Kernel config warnings while building linux-yocto-4.8 for intel-corei7-64 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Maxin B. John <maxin.john> |
| Component: | bsps-meta-intel | Assignee: | California Sullivan <california.l.sullivan> |
| Status: | RESOLVED FIXED | QA Contact: | David Lopez Barriba <davidx.lopez.barriba> |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | jose.perez.carranza, sgw |
| Version: | 2.2 | ||
| Target Milestone: | 2.3 M1 | ||
| Hardware: | NUC | ||
| OS: | x86_64 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | 10408 | ||
| Bug Blocks: | |||
|
Description
Maxin B. John
2016-10-13 12:57:06 UTC
Patch is pending with the yocto-kernel-cache and this will be fixed for the meta-intel release. I sent a patch to meta-intel updating the yocto-kernel-cache SRCREVs to include my changes, which fixes these errors and a few others in different configurations. Still remaining are the following: With intel-quark builds we get: Config: CONFIG_INV_MPU6050_I2C Requested value: CONFIG_INV_MPU6050_I2C=m Actual value: This occurs due to a missing I2C_MUX dependency on a driver enabled in iio.cfg. In other BSPs this dependency is satisfied automatically through a select, and I just haven't decided the appropriate place to add the I2C_MUX configuration yet. Config: CONFIG_BMP280 Requested value: # CONFIG_BMP280 is not set Actual value: CONFIG_BMP280 depends on !BMP085. BMP085 is used by the galileo (target device for intel-quark), so the option for BMP280 is not available, but its requested in iio.cfg. I added "# CONFIG_BMP280 is not set" because requesting is not set and getting no configuration is preferable to requesting the driver and getting no configuration. Might reiterate back on this one. With intel-core2-32 or intel-corei7-64 preempt-rt builds we get: Config: CONFIG_LEDS_TRIGGER_CPU Requested value: CONFIG_LEDS_TRIGGER_CPU=y Actual value: This one occurs because the leds feature is in intel-common-drivers, leds.cfg includes CONFIG_LEDS_TRIGGER_CPU=y, and LEDS_TRIGGER_CPU depends on !PREEMPT_RT_BASE, which makes the option unavailable to set. It will be difficult to fix this one without a fairly hefty reorganization. Patches submitted addressing the remaining issues. |