On 6/30/26 2:09 PM, George Moussalem wrote: > On 6/30/26 15:40, Konrad Dybcio wrote: >> On 6/29/26 3:01 PM, George Moussalem via B4 Relay wrote: >>> From: George Moussalem <[email protected]> >>> >>> Add nodes for the reserved memory carveout and Bluetooth. >>> >>> Signed-off-by: George Moussalem <[email protected]> >>> --- >>> arch/arm64/boot/dts/qcom/ipq5018.dtsi | 25 ++++++++++++++++++++++++- >>> 1 file changed, 24 insertions(+), 1 deletion(-) >>> >>> diff --git a/arch/arm64/boot/dts/qcom/ipq5018.dtsi >>> b/arch/arm64/boot/dts/qcom/ipq5018.dtsi >>> index 6f8004a22a1f..65a47ba7d3a3 100644 >>> --- a/arch/arm64/boot/dts/qcom/ipq5018.dtsi >>> +++ b/arch/arm64/boot/dts/qcom/ipq5018.dtsi >>> @@ -17,6 +17,23 @@ / { >>> #address-cells = <2>; >>> #size-cells = <2>; >>> >>> + bluetooth: bluetooth { >>> + compatible = "qcom,ipq5018-bt"; >>> + >>> + firmware-name = "qca/bt_fw_patch.mbn"; >> >> Is this fw vendor-signed? > > I've just analyzed the mbn file (and the mdt + b0x files): it only > contains hashes for the mdt and b02 segments, no signature/certs at all. > I've used your pil squasher to create the mbn file. Here are the FW files: > https://github.com/georgemoussalem/openwrt/tree/ipq50xx-bluetooth/package/firmware/qca-bt-firmware/files > > Perhaps you can double check?
Using the not very sophisticated but very quick method of running strings on it, there's no certificate identifiers indeed Konrad
