From: Yang Li <yang.li@amlogic.com>
To: "Christain Stefan Köver-Draxl" <ckoever@outlook.de>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-bluetooth@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] Bluetooth: add a quirk for controllers that cannot enable Secure Connections
Date: Tue, 10 Nov 2026 17:11:23 +0800 [thread overview]
Message-ID: <f05a1d68-4a07-4b79-aaf7-69fa85038248@amlogic.com> (raw)
In-Reply-To: <MMZPR08MB549315933A342E32853DED71E1DF762@MMZPR08MB549315.eurprd08.prod.outlook.com>
Hi,
I updated the w155s2 firmware bin in linux-firmware.
See the link below.
https://lore.kernel.org/all/20261110-upgrade_w155s2_bin-v1-1-4533ba6005cd@amlogic.com/
>
> On 11/5/26 10:19, Yang Li wrote:
>> This appears to be an anomaly with the firmware binary. Could you
>> provide the FW version in use? It is logged during Bluetooth driver
>> initialization.
>
> Hi Yang,
>
> the controller reports
>
> fw_version: date = 09.08, number = 0x15d2
>
> The firmware is not the linux-firmware one: aml_w155s2_bt_uart.bin from
> linux-firmware downloads without errors on this board and then never
> starts (no HCI event after the download). The one that works is the
> firmware embedded in the vendor Android libbt-vendor_aml.so of this box
> (X98Q, S905W2), 0x60000 bytes. I load it as aml_w1_bt_uart.bin.
>
> If there is a newer firmware without this behaviour, I would be glad to
> test it, and if it fixes it I would rather drop the quirk than add it.
> Is the linux-firmware image meant for this chip revision, or should it
> start as well?
>
> Kind regards,
> Christian K.-D.
next prev parent reply other threads:[~2026-11-10 9:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 19:23 [PATCH 0/7] Bluetooth: make the Amlogic W1 (W155S2) usable christian.koever-draxl
2026-10-25 19:23 ` [PATCH 1/7] Bluetooth: add a quirk for controllers that cannot enable Secure Connections christian.koever-draxl
2026-11-05 2:19 ` Yang Li
2026-11-06 9:17 ` Christain Stefan Köver-Draxl
2026-11-10 9:11 ` Yang Li [this message]
2026-10-25 19:23 ` [PATCH 2/7] Bluetooth: add a quirk for controllers that hang on Write Current IAC LAP christian.koever-draxl
2026-11-05 2:24 ` Yang Li
2026-11-06 9:19 ` Christain Stefan Köver-Draxl
2026-11-10 9:13 ` Yang Li
2026-10-25 19:23 ` [PATCH 3/7] Bluetooth: hci_aml: cope with a controller that is already running christian.koever-draxl
2026-11-06 3:28 ` Yang Li
2026-10-25 19:23 ` [PATCH 4/7] dt-bindings: net: bluetooth: amlogic,w155s2-bt: allow local-bd-address christian.koever-draxl
2026-10-30 11:32 ` Krzysztof Kozlowski
2026-10-25 19:23 ` [PATCH 5/7] Bluetooth: hci_aml: take the address from the firmware description christian.koever-draxl
2026-11-06 3:15 ` Yang Li
2026-10-25 19:23 ` [PATCH 6/7] dt-bindings: net: bluetooth: amlogic,w155s2-bt: add amlogic,shared-antenna christian.koever-draxl
2026-10-30 11:40 ` Krzysztof Kozlowski
2026-10-25 19:23 ` [PATCH 7/7] Bluetooth: hci_aml: configure the RF for a shared antenna christian.koever-draxl
2026-11-06 2:57 ` Yang Li
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=f05a1d68-4a07-4b79-aaf7-69fa85038248@amlogic.com \
--to=yang.li@amlogic.com \
--cc=ckoever@outlook.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®