On Fri, Feb 20, 2026 at 03:02:48PM +0100, Konrad Dybcio wrote: > On 2/20/26 2:53 PM, George Moussalem wrote: > > > > > > On 2/20/26 14:36, Konrad Dybcio wrote: > >> On 2/19/26 8:42 PM, Jeff Johnson wrote: > >>> On 1/13/2026 1:20 AM, Varadarajan Narayanan wrote: > >>>> From: George Moussalem <[email protected]> > >>>> > >>>> Enable nodes required for q6 remoteproc bring up. > >>> > >>> I just recently became aware of this series, and have some questions... > >>> > >>>> + q6v5_wcss: remoteproc@cd00000 { > >>>> + compatible = "qcom,ipq5018-wcss-sec-pil"; > >>>> + reg = <0x0cd00000 0x10000>; > >>>> + firmware-name = > >>>> "ath11k/IPQ5018/hw1.0/q6_fw.mbn"; > >>> > >>> This file does not currently exist in linux-firmware. > >>> Instead there is q6_fw.mdt with associated .b* files. > >>> > >>> How do we transition from .mdt to .mbn given that distros update their > >>> version > >>> of linux-firmware independently from kernel updates? Will we need to have > >>> both > >>> the .mdt and .mbn files present for some period of time? Are there > >>> associated > >>> changes which no longer attempt to load the .mdt files? > >> > >> Since there are no in-kernel users for this one (the ipq8074 WCSS driver > >> requests that but no DT is wired up), I would say we should promptly move > >> to > >> MBN.. > >> > >>> I ask because I've been told the ath11k/ath12k drivers will also need to > >>> transition their firmware loading from m3_fw.mdt to m3_fw.mbn, and I'm not > >>> sure how to make that transition. > >> > >> I can't see any m3_fw.mdt in the tree or l-f, unless the m3.bin qualifies > > > > I think you checked for QCN9074 which uses amss.bin and m3.bin. For > > IPQ5018, IPQ6018, and IPQ8074, m3_fw.mdt is there, see: > > https://git.kernel.org/pub/scm/linux/kernel/git/ath/linux-firmware.git/tree/ath11k/IPQ5018/hw1.0 > > https://git.kernel.org/pub/scm/linux/kernel/git/ath/linux-firmware.git/tree/ath11k/IPQ6018/hw1.0 > > https://git.kernel.org/pub/scm/linux/kernel/git/ath/linux-firmware.git/tree/ath11k/IPQ8074/hw2.0 > > Snap, you're right. > > I think a simple ln -s file.mbn file.mdt should work though? mdt_loader > seems not to care about the file extension at a glance.
You are correct here. A symlink is a correct way to upgrade from .mdt to .mbn. Inside linux-firmware the easiest way to handle it is to add Link: to the WHENCE file. -- With best wishes Dmitry
