| Summary: | Kernel Config for NUC machine is incomplete in regard to Bluetooth support | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Cristian Iorga <cristian.iorga> | ||||
| Component: | bsps-meta-intel | Assignee: | Cristian Iorga <cristian.iorga> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Cristina Agurida <cristina-danielax.agurida> | ||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | bogdanx.a.voiculescu, cristian.iorga, dvhart, sgw, tom.zanussi | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 1.9 M1 | ||||||
| Hardware: | NUC | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Cristian Iorga
2014-11-13 10:00:12 UTC
Any sort of generic protocol/etc type support is appropriate for: meta/cfg/kernel-cache/features/bluetooth/bluetooth.cfg I would suggest breaking these up into BT Subsystem and BT Drivers. For example: bluetooth.cfg CONFIG_NET CONFIG_BT CONFIG_BT_RFCOMM* CONFIG_BT_BNEP* CONFIG_BT_CMTP CONFIG_BT_HIDP The drivers however should be separate, especially if they pull in entire subsystems like USB. We have other hierarchical driver configs like this, Nitin did the media abstraction for this reason. You don't want bluetooth to force the inclusion of USB, for example. So those should be separated out, perhaps: bluetooth-drivers-all bluetooth-usb bluetooth-sdio bluetooth-uart the top one can also include all the specific drivers, but people can select: bluetooth-usb and get everything they need for the NUC, as it would depend on bluetooth, but not pull in SDIO nor UART - for example. Using the scc files for the dependency chain. Investigation started. Design started, based on Darren Hart notes. Partial implementation sent in for review. Partial implementation via commit: http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.19/commit/?h=meta&id=be02def40293bdfbaa9f230e0adba715ec906516 for linux-yocto-3.19 Partial implementation via commit: http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.14/commit/?h=meta&id=8c705b03452f8db4f251c6cef067cc94d5c19f9f for linux-yocto-3.14 Final patchset submitted for review. Testing: Relevant info: [ 1.827694] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated root@intel-corei7-64:~# hciconfig hci0 up Can't init device hci0: Operation not possible due to RF-kill (132) root@intel-corei7-64:~# rfkill unblock bluetooth root@intel-corei7-64:~# hciconfig hci0 up root@intel-corei7-64:~# hcitool dev Devices: hci0 AC:7B:A1:93:C4:3D root@intel-corei7-64:~# hcitool scan Scanning ... 00:27:13:9B:B9:E0 ***URIDX-**BL (obfuscated) 7C:7A:91:85:8F:03 ***NFIR-**BL1 (obfuscated) root@intel-corei7-64:~# uname -a Linux intel-corei7-64 3.19.2-yocto-standard #1 SMP PREEMPT Mon Apr 20 10:54:41 EEST 2015 x86_64 GNU/Linux root@intel-corei7-64:~# Created attachment 2483 [details]
Full non-exhaustive test log
Integrated into linux-yocto with commit: http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.19/commit/?h=meta&id=205aca0c1241563d57eda8b8ba0896a7f6570962 Fixed for intel-core* machines with commit: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=34ddfb6559c5fb0c7e194cbe9440c619efcc6907 |