All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221720] Outdated Intel BT firmware ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq (patch 0x27) breaks all HFP/SCO audio — Windows driver ships working patch 0x2b
Date: Sat, 18 Jul 2026 15:00:55 +0000	[thread overview]
Message-ID: <bug-221720-62941-VphKlgwo48@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221720-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=221720

--- Comment #2 from dev@fluid8.de (dev@fluid8.de) ---
Created attachment 310476
  --> https://bugzilla.kernel.org/attachment.cgi?id=310476&action=edit
install Intel Bluetooth legacy RAM-patch firmware

install-ibt-fw.sh — install Intel Bluetooth legacy RAM-patch firmware.

Companion to extract-ibt-fw.py: takes the .bseq blobs that script carved out of
Intel's Windows driver and installs them so the Linux btintel driver picks them
up, on any reasonably current Linux distribution.

#   ./extract-ibt-fw.py --verify BT_21.10.1_64_Win8.1.exe out/
#   sudo ./install-ibt-fw.sh out/
#   # then power the machine fully off once

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2026-07-18 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-04 15:19 [Bug 221720] New: Outdated Intel BT firmware ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq (patch 0x27) breaks all HFP/SCO audio — Windows driver ships working patch 0x2b bugzilla-daemon
2026-07-18 13:21 ` [Bug 221720] " bugzilla-daemon
2026-07-18 15:00 ` bugzilla-daemon [this message]

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-221720-62941-VphKlgwo48@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.