Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bluetooth #11

Closed
danielnilsson9 opened this issue Mar 27, 2016 · 5 comments
Closed

bluetooth #11

danielnilsson9 opened this issue Mar 27, 2016 · 5 comments

Comments

@danielnilsson9
Copy link

Hi

Any ideas for getting bluetooth to work on rpi3? I have tried patching bluez5 according to this issue:
raspberrypi/linux#1314

and putting the image in /lib/firmware/brcm and all but I can't get it to work. I just get get timeouts when running hciattach, sometimes it says flashing firmware but then it times out again.

Anyone who got it working or is working on it that could help?

Thank you,
Daniel
@toolmmy
Copy link
Contributor

toolmmy commented Apr 9, 2016

hi @danielnilsson9
check out the following commit https://github.com/toolmmy/meta-raspberrypi/commit/e6e84cbb8dbee54c484105de8dc6c40169e881bb
Make sure that you dont have a running agetty on ttyAMA0

@danielnilsson9
Copy link
Author

@toolmmy

Looks pretty much identical to what I did, strange I couldn't get i working, definitely gonna try that out. Thank you for letting me know!

@agherzan
Copy link
Owner

@toolmmy I see a set of patches on bluez5 but on trace of them online. Are these sent to bluez5? What is the status of these patches?

@toolmmy
Copy link
Contributor

toolmmy commented Apr 13, 2016 •
edited
Loading

@agherzan These patches regarding bluez5 seem to be very specific for the rpi3. Thats why they are provided by the foundation itself. I couldn't find any discussions in the bluez5 mailing list. Even when the patches are included in the upcoming versions of bluez5 we still rely on the latest versions provided by poky/openEmbedded which might can take time until they have spread out.

@agherzan
Copy link
Owner

I merged a patch similar to what @toolmmy proposed. The only change is that the changes to bluez are rpi3 machine specific in the bbappend.

Cheers!

agherzan pushed a commit that referenced this issue Mar 23, 2018
@hhromic @agherzan
gstreamer1.0-omx: refresh and clean-up patches
415c199 
fixes:

    WARNING: gstreamer1.0-omx-1.12.4-r0 do_patch:
    Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
    The context lines in the patches can be updated with devtool:

        devtool modify <recipe>
        devtool finish --force-patch-refresh <recipe> <layer_path>

    Then the updated patches and the source tree (in devtool's workspace)
    should be reviewed to make sure the patches apply in the correct place
    and don't introduce duplicate lines (which can, and does happen
    when some of the context is ignored). Further information:
    http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
    https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
    Details:
    Applying patch 0001-config-files-path.patch
    patching file config/bellagio/gstomx.conf
    Hunk #1 succeeded at 1 with fuzz 2.
    Hunk #2 succeeded at 9 with fuzz 2.
    patching file config/rpi/gstomx.conf
    Hunk #8 succeeded at 63 with fuzz 2.
    Hunk #10 succeeded at 82 with fuzz 2.
    Hunk #11 succeeded at 92 with fuzz 2.

    Now at patch 0001-config-files-path.patch

deleted obsolete `gstreamer1.0-omx` directory with duplicated patches that are also in `gstreamer1.0-omx-1.12`.
made file naming for `gstreamer1.0-omx_%.bbappend` consistent with the rest of the layer recipes.

Signed-off-by: Hugo Hromic <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@agherzan @danielnilsson9 @toolmmy