beagleboard invalid config in 1.3 danny branch
This is mostly informative, unless it's because I'm doing something wrong in which case I'd appreciate a clue.
With this sequence:
git clone -b danny git://git.yoctoproject.org/poky
cd poky
. oe-init-build-env
MACHINE=beagleboard bitbake virtual/kernel
which documents itself as:
Build Configuration:
BB_VERSION = "1.16.0" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "beagleboard" DISTRO = "poky" DISTRO_VERSION = "1.3" TUNE_FEATURES = "armv7a vfp neon cortexa8" TARGET_FPU = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp = "danny:09031ac2fc0f30ec577ee823fc61ff0e5d852e21"
the build produces the following warning (with referenced file contents inserted):
This BSP sets 4 invalid/obsolete kernel options.
These config options are not offered anywhere within this kernel. The full list can be found in your kernel src dir at:
meta/cfg/standard/beagleboard/invalid.
CONFIG_DISPLAY_SUPPORTCONFIG_USB_MUSB_HDRC_HCDCONFIG_USB_MUSB_OTGCONFIG_WL12XX_HT
This BSP sets 4 kernel options that are possibly non-hardware related. The full list can be found in your kernel src dir at:
meta/cfg/standard/beagleboard/specified_non_hdw.cfg
CONFIG_CC_OPTIMIZE_FOR_SIZECONFIG_NETCONFIG_NETDEVICESCONFIG_PANEL_DVI
WARNING: There were 8 hardware options requested that do not
have a corresponding value present in the final ".config" file. This probably means you aren't getting the config you wanted.
The full list can be found in your kernel src dir at:
meta/cfg/standard/beagleboard/mismatch.cfg
Value requested for CONFIG_BACKLIGHT_CLASS_DEVICE not in final ".config" Requested value: "CONFIG_BACKLIGHT_CLASS_DEVICE=y"
Actual value set: ""
Value requested for CONFIG_PANEL_SHARP_LS037V7DW01 not in final ".config" Requested value: "CONFIG_PANEL_SHARP_LS037V7DW01=y"
Actual value set: ""
Value requested for CONFIG_USB_G_NCM not in final ".config" Requested value: "CONFIG_USB_G_NCM=y"
Actual value set: "# CONFIG_USB_G_NCM is not set"
Value requested for CONFIG_USB_MUSB_HDRC_HCD not in final ".config" Requested value: "CONFIG_USB_MUSB_HDRC_HCD=y"
Actual value set: ""
Value requested for CONFIG_USB_MUSB_OTG not in final ".config" Requested value: "CONFIG_USB_MUSB_OTG=y"
Actual value set: ""
Value requested for CONFIG_USB_OMAP not in final ".config" Requested value: "CONFIG_USB_OMAP=y"
Actual value set: "# CONFIG_USB_OMAP is not set"
Value requested for CONFIG_USB_OTG not in final ".config" Requested value: "CONFIG_USB_OTG=y"
Actual value set: ""
Value requested for CONFIG_WL12XX_HT not in final ".config" Requested value: "CONFIG_WL12XX_HT=y"
Actual value set: ""
Since beagleboard is a reference platform I had not expected these warnings. I see in the archives discussion of a similar issue in the pre-release phases of 1.2. I didn't try with "real" 1.3 but subsequent changes in danny don't seem relevant.
There's also the following which is suspicious:
find: warning: -path /prj/oe/poky/build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a5554b81cc8ad23267d-r4.3/linux/ will not match anything because it ends with /.
Peter
Quoted 4 lines · Peter A. Bigot
This is mostly informative, unless it's because I'm doing something wrong in which case I'd appreciate a clue.
Hmm. I was also under the impression that we squashed all these, at least the qemu* boards were clean.
Quoted 78 lines
With this sequence:
git clone -b danny git://git.yoctoproject.org/**poky<http://git.yoctoproject.org/poky>
cd poky
. oe-init-build-env
MACHINE=beagleboard bitbake virtual/kernelwhich documents itself as:
Build Configuration:
BB_VERSION = "1.16.0" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "beagleboard" DISTRO = "poky" DISTRO_VERSION = "1.3" TUNE_FEATURES = "armv7a vfp neon cortexa8" TARGET_FPU = "vfp-neon"meta
meta-yocto
meta-yocto-bsp = "danny:**09031ac2fc0f30ec577ee823fc61ff**0e5d852e21"the build produces the following warning (with referenced file contents inserted):
This BSP sets 4 invalid/obsolete kernel options.
These config options are not offered anywhere within this kernel. The full list can be found in your kernel src dir at:
meta/cfg/standard/beagleboard/**invalid.
CONFIG_DISPLAY_SUPPORTCONFIG_USB_MUSB_HDRC_HCDCONFIG_USB_MUSB_OTGCONFIG_WL12XX_HTThis BSP sets 4 kernel options that are possibly non-hardware related. The full list can be found in your kernel src dir at:
meta/cfg/standard/beagleboard/**specified_non_hdw.cfg
CONFIG_CC_OPTIMIZE_FOR_SIZECONFIG_NETCONFIG_NETDEVICESCONFIG_PANEL_DVIWARNING: There were 8 hardware options requested that do not
have a corresponding value present in the final ".config" file. This probably means you aren't getting the config you wanted.
The full list can be found in your kernel src dir at:
meta/cfg/standard/beagleboard/**mismatch.cfgValue requested for
CONFIG_BACKLIGHT_CLASS_DEVICEnot in final ".config" Requested value: "CONFIG_BACKLIGHT_CLASS_**DEVICE=y"
Actual value set: ""Value requested for
CONFIG_PANEL_SHARP_LS037V7DW01not in final ".config" Requested value: "CONFIG_PANEL_SHARP_**LS037V7DW01=y"
Actual value set: ""Value requested for
CONFIG_USB_G_NCMnot in final ".config" Requested value: "CONFIG_USB_G_NCM=y"
Actual value set: "#CONFIG_USB_G_NCMis not set"Value requested for
CONFIG_USB_MUSB_HDRC_HCDnot in final ".config" Requested value: "CONFIG_USB_MUSB_HDRC_HCD=y"
Actual value set: ""Value requested for
CONFIG_USB_MUSB_OTGnot in final ".config" Requested value: "CONFIG_USB_MUSB_OTG=y"
Actual value set: ""Value requested for
CONFIG_USB_OMAPnot in final ".config" Requested value: "CONFIG_USB_OMAP=y"
Actual value set: "#CONFIG_USB_OMAPis not set"Value requested for
CONFIG_USB_OTGnot in final ".config" Requested value: "CONFIG_USB_OTG=y"
Actual value set: ""
Quoted 10 lines
Value requested for
CONFIG_WL12XX_HTnot in final ".config" Requested value: "CONFIG_WL12XX_HT=y"
Actual value set: ""Since beagleboard is a reference platform I had not expected these warnings. I see in the archives discussion of a similar issue in the pre-release phases of 1.2. I didn't try with "real" 1.3 but subsequent changes in danny don't seem relevant.
None of these should impact the runtime of the board, but they also shouldn't
be present.
We are iterating the configs now in master for the LTSI update, I can have a look
at them then, and any relevant changes can be backported to danny.
Quoted 7 lines
There's also the following which is suspicious:
find: warning: -path /prj/oe/poky/build/tmp/work/**beagleboard-poky-linux- **gnueabi/linux-yocto-3.4.11+**git1+**a201268353c030d9fafe00f2041976** f7437d9386_1+**449f7f520350700858f21a5554b81c**c8ad23267d-r4.3/linux/ will not match anything because it ends with /.
This isn't the cause of the problem, but it is something that was fixed in master.
Bruce
Quoted 8 lines
Peter
______________________________**_________________
poky mailing list
[email protected]
https://lists.yoctoproject.**org/listinfo/poky<https://lists.yoctoproject.org/listinfo/poky>
Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"