-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
WARNING: bluez5-5.46-r0 do_configure: QA Issue: bluez5: invalid PACKAGECONFIG: experimental [invalid-packageconfig]
We really should not mix multiple rcar-gen3 support layers.
The changes to core infrastructure (e.g. systemd, bluetooth, network) done by these is waaay to big.
BSP layers should only enable the hardware, not configure an image for a particular purpose. Thats what demo/distro layers are for. See the split between -bsp and -example here: https://github.com/siemens/meta-iot2000
So if we'd follow that approach quite a few recipes from the -adas layer would end-up in an -example sup-layer. B/C they're for a particular board setup or demo.
ronan, sdesneux, harunobu.kurokawa ... comments or pointers ?
Any update on the roadmap for KingFisher being in the default bsp release ?