summaryrefslogtreecommitdiff
path: root/meta/recipes-extended/cups
diff options
context:
space:
mode:
authorCalifornia Sullivan <california.l.sullivan@intel.com>2017-04-21 15:18:35 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-05-04 13:49:46 +0100
commit297be6619e3141c32cb1167cb91c4d4f13ff8248 (patch)
tree54ba3d9a82ccb67835d18dd55ca072389026cf0f /meta/recipes-extended/cups
parent4483809d0b99428561dc4a4d95fdfa5cc46100ad (diff)
downloadopenembedded-core-297be6619e3141c32cb1167cb91c4d4f13ff8248.tar.gz
openembedded-core-297be6619e3141c32cb1167cb91c4d4f13ff8248.tar.bz2
openembedded-core-297be6619e3141c32cb1167cb91c4d4f13ff8248.zip
parselogs: whitelist bluetooth firmware load error for intel-corei7-64
The NUC6 has issues bringing up Bluetooth early in the boot sequence. We see: [ 4.091790] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 4.097326] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 4.145317] Bluetooth: hci0: Failed to send firmware data (-38) Followed by this later on: [ 11.509870] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.509988] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 13.090308] Bluetooth: hci0: Waiting for firmware download to complete [ 13.090829] Bluetooth: hci0: Firmware loaded in 1549114 usecs [ 13.090987] Bluetooth: hci0: Waiting for device to boot [ 13.101958] Bluetooth: hci0: Device booted in 10818 usecs Bluetooth does successfully come up and the firmware is loaded. This behavior is consistent across all kernels I've tested. [YOCTO #10628]. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-extended/cups')
0 files changed, 0 insertions, 0 deletions