Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Bluetooth BCM20702A1
@ 2016-04-30 17:57 Marco Trapanese
  2016-04-30 20:07 ` Peter Korsgaard
  0 siblings, 1 reply; 3+ messages in thread
From: Marco Trapanese @ 2016-04-30 17:57 UTC (permalink / raw)
  To: buildroot

Hi!
Does buildroot provide the firmware for this common USB/BT dongle?
I'm running the latest version on an RPi3.
Here the output of dmesg:

> [    3.126672] usb 1-1.2: Product: BCM20702A0
> [    4.435485] Bluetooth: hci0: BCM20702A
> [    4.442507] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
> [    4.442572] bluetooth hci0: Direct firmware load for 
> brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2
> [    4.442579] Bluetooth: hci0: BCM: Patch 
> brcm/BCM20702A1-0a5c-21e8.hcd not found

and here lsmod:

> # lsmod | grep bt
> btusb                  27112  0
> btrtl                   3573  1 btusb
> btintel                 6072  1 btusb
> btbcm                   5627  1 btusb
> bluetooth             315678  7 btusb,btrtl,btintel,btbcm

The dongle works fine with Raspbian Jessie.
If you need other information, please feel free to ask!

Thanks in advance
Marco

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Buildroot] Bluetooth BCM20702A1
  2016-04-30 17:57 [Buildroot] Bluetooth BCM20702A1 Marco Trapanese
@ 2016-04-30 20:07 ` Peter Korsgaard
  2016-05-01 15:00   ` [Buildroot] Qt5 and display Marco Trapanese
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Korsgaard @ 2016-04-30 20:07 UTC (permalink / raw)
  To: buildroot

>>>>> "Marco" == Marco Trapanese <marcotrapanese@gmail.com> writes:

 > Hi!
 > Does buildroot provide the firmware for this common USB/BT dongle?
 > I'm running the latest version on an RPi3.
 > Here the output of dmesg:

 >> [    3.126672] usb 1-1.2: Product: BCM20702A0
 >> [    4.435485] Bluetooth: hci0: BCM20702A
 >> [    4.442507] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
 >> [    4.442572] bluetooth hci0: Direct firmware load for
 >> brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2
 >> [    4.442579] Bluetooth: hci0: BCM: Patch
 >> brcm/BCM20702A1-0a5c-21e8.hcd not found

It seems it is not available in linux-firmware:

find build/linux-firmware-b0668886def608d352cd0263a7ef04e64e25574a \
     -name BCM20702A1-0a5c-21e8.hcd

According to this bugreport:

https://bugzilla.redhat.com/show_bug.cgi?id=1275122

It is indeed not available in linux-firmware. The bugreport does refer
to places where you can download the firmware, but it is not clear what
license it is available under and if we are allowed to redistribute it.

Judging from the kernel commits to this driver it sounds like it should
be usable without firmware though:

commit ad750fa142747f3f42b66ae051a0f275bd2035df
Author: Petri Gynther <pgynther@google.com>
Date:   Wed Feb 10 12:00:46 2016 -0800

    Bluetooth: btbcm: Fix handling of firmware not found

    If the call to request_firmware() fails in btbcm_setup_patchram(),
    the BCM chip will be operating with its default firmware.

    In this case, btbcm_setup_patchram() should not return immediately
    but instead should skip to btbcm_check_bdaddr() and quirk setup.

    Signed-off-by: Petri Gynther <pgynther@google.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

But that commit is probably not present in the rpi kernel yet.


 > The dongle works fine with Raspbian Jessie.
 > If you need other information, please feel free to ask!

It would be interesting to know where they get the firmware from. Can
you check what package provides the file?

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Buildroot] Qt5 and display
  2016-04-30 20:07 ` Peter Korsgaard
@ 2016-05-01 15:00   ` Marco Trapanese
  0 siblings, 0 replies; 3+ messages in thread
From: Marco Trapanese @ 2016-05-01 15:00 UTC (permalink / raw)
  To: buildroot

Hi,
I compiled Qt5 in Buildroot 2016.05-git-01124-g70fc85f-dirty with both 
X11 and eglfs support, because I would like to try both.
Console application runs fine, but when I launch a visual application 
(i.e. qml) I get:


> Could not open display

Currently I have no X server running so I'm launching my application 
with -platform eglfs

exporting QT_DEBUG_PLUGINS=1 leads to this output:

> QML debugging is enabled. Only use this in a safe environment.
> QFactoryLoader::QFactoryLoader() checking directory path 
> "/usr/lib/qt/plugins/platforms" ...
> QFactoryLoader::QFactoryLoader() looking at 
> "/usr/lib/qt/plugins/platforms/libqeglfs.so"
> Found metadata in lib /usr/lib/qt/plugins/platforms/libqeglfs.so, 
> metadata=
> {
>     "IID": 
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
>     "MetaData": {
>         "Keys": [
>             "eglfs"
>         ]
>     },
>     "className": "QEglFSIntegrationPlugin",
>     "debug": false,
>     "version": 329216
> }
>
>
> Got keys from plugin meta data ("eglfs")
> QFactoryLoader::QFactoryLoader() looking at 
> "/usr/lib/qt/plugins/platforms/libqminimal.so"
> Found metadata in lib /usr/lib/qt/plugins/platforms/libqminimal.so, 
> metadata=
> {
>     "IID": 
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
>     "MetaData": {
>         "Keys": [
>             "minimal"
>         ]
>     },
>     "className": "QMinimalIntegrationPlugin",
>     "debug": false,
>     "version": 329216
> }
>
>
> Got keys from plugin meta data ("minimal")
> QFactoryLoader::QFactoryLoader() looking at 
> "/usr/lib/qt/plugins/platforms/libqminimalegl.so"
> Found metadata in lib /usr/lib/qt/plugins/platforms/libqminimalegl.so, 
> metadata=
> {
>     "IID": 
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
>     "MetaData": {
>         "Keys": [
>             "minimalegl"
>         ]
>     },
>     "className": "QMinimalEglIntegrationPlugin",
>     "debug": false,
>     "version": 329216
> }
>
>
> Got keys from plugin meta data ("minimalegl")
> QFactoryLoader::QFactoryLoader() looking at 
> "/usr/lib/qt/plugins/platforms/libqoffscreen.so"
> Found metadata in lib /usr/lib/qt/plugins/platforms/libqoffscreen.so, 
> metadata=
> {
>     "IID": 
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
>     "MetaData": {
>         "Keys": [
>             "offscreen"
>         ]
>     },
>     "className": "QOffscreenIntegrationPlugin",
>     "debug": false,
>     "version": 329216
> }
>
>
> Got keys from plugin meta data ("offscreen")
> QFactoryLoader::QFactoryLoader() looking at 
> "/usr/lib/qt/plugins/platforms/libqxcb.so"
> Found metadata in lib /usr/lib/qt/plugins/platforms/libqxcb.so, metadata=
> {
>     "IID": 
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
>     "MetaData": {
>         "Keys": [
>             "xcb"
>         ]
>     },
>     "className": "QXcbIntegrationPlugin",
>     "debug": false,
>     "version": 329216
> }
>
>
> Got keys from plugin meta data ("xcb")
> QFactoryLoader::QFactoryLoader() checking directory path 
> "/opt/QmlTest/bin/platforms" ...
> loaded library "/usr/lib/qt/plugins/platforms/libqeglfs.so"
> QFactoryLoader::QFactoryLoader() checking directory path 
> "/usr/lib/qt/plugins/egldeviceintegrations" ...
> QFactoryLoader::QFactoryLoader() looking at 
> "/usr/lib/qt/plugins/egldeviceintegrations/libqeglfs-x11-integration.so"
> Found metadata in lib 
> /usr/lib/qt/plugins/egldeviceintegrations/libqeglfs-x11-integration.so, metadata=
> {
>     "IID": 
> "org.qt-project.qt.qpa.egl.QEGLDeviceIntegrationFactoryInterface.5.5",
>     "MetaData": {
>         "Keys": [
>             "eglfs_x11"
>         ]
>     },
>     "className": "QEglFSX11IntegrationPlugin",
>     "debug": false,
>     "version": 329216
> }
>
>
> Got keys from plugin meta data ("eglfs_x11")
> QFactoryLoader::QFactoryLoader() checking directory path 
> "/opt/QmlTest/bin/egldeviceintegrations" ...
> loaded library 
> "/usr/lib/qt/plugins/egldeviceintegrations/libqeglfs-x11-integration.so"
> Could not open display
> Aborted
> Application finished with exit code 134.

I never had this kind of problem with all previous Buildroot 
environments I compiled.
This is due to my configuration? I attach the .config file.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/xml
Size: 84242 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160501/07ad3c71/attachment-0001.wsdl>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-05-01 15:00 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-30 17:57 [Buildroot] Bluetooth BCM20702A1 Marco Trapanese
2016-04-30 20:07 ` Peter Korsgaard
2016-05-01 15:00   ` [Buildroot] Qt5 and display Marco Trapanese

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox