From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 110901] Macbook8,1 12-inch (Early 2015) Bluetooth not working
Date: Sun, 17 Mar 2024 21:23:08 +0000 [thread overview]
Message-ID: <bug-110901-62941-nlJZMMrmgj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-110901-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=110901
Jonas (j@ovvvo.co) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |j@ovvvo.co
--- Comment #49 from Jonas (j@ovvvo.co) ---
(In reply to Leif Liddy from comment #46)
> Cool, thanks for the update.
>
> I managed to get bluetooth working on a 4.14-rc1 kernel after applying
>
> l1k's hci_bcm.c patch
> https://github.com/torvalds/linux/compare/master...l1k:hci_bcm
>
> and roadrunner2's hci_bcm.c and hci_ldisc.c patches
> https://github.com/l1k/linux/pull/1/files/
> 61c59e8b2a7f129a339608610069a26f4181c82a..
> 7dd4a90a92b97b017d9210899afcfbe985b10509
>
> There's a pull request to include roadrunner's patches in l1k's repo. Work
> is also being done to port the patches to 4.14 (I just did it manually)
> So, this all be cleaned up in the near future.
>
> You can read more about the current status on the link Christoph posted:
> https://github.com/Dunedan/mbp-2016-linux/issues/29
Are these patches still required or have they eventually been merged into the
kernel eventually?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-03-17 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-110901-62941@https.bugzilla.kernel.org/>
2017-09-06 8:39 ` [Bug 110901] Macbook8,1 12-inch (Early 2015) Bluetooth not working bugzilla-daemon
2017-09-24 22:41 ` bugzilla-daemon
2017-09-24 22:43 ` bugzilla-daemon
2017-09-25 7:08 ` bugzilla-daemon
2024-03-17 21:23 ` bugzilla-daemon [this message]
2026-05-13 16:08 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-110901-62941-nlJZMMrmgj@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.