From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-firmware@kernel.org, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org, ath11k@lists.infradead.org
Subject: Re: [PULL linux-firmware] ath10k & ath11k firmware 20230215
Date: Wed, 22 Mar 2023 07:54:19 +0200 [thread overview]
Message-ID: <87v8ite3g4.fsf@kernel.org> (raw)
In-Reply-To: <f08d7310-8c33-ab0b-c9f1-317f737ba37c@linaro.org> (Dmitry Baryshkov's message of "Wed, 22 Mar 2023 01:39:17 +0200")
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
>> ath11k/IPQ5018/hw1.0/Notice.txt | 4094 ++++++++++++++++++++++++++++++
>> ath11k/IPQ5018/hw1.0/board-2.bin | Bin 0 -> 524564 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.b00 | Bin 0 -> 148 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.b01 | Bin 0 -> 136 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.b02 | Bin 0 -> 262144 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.flist | 3 +
>> ath11k/IPQ5018/hw1.0/m3_fw.mdt | Bin 0 -> 284 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b00 | Bin 0 -> 532 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b01 | Bin 0 -> 520 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b02 | Bin 0 -> 7552 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b03 | Bin 0 -> 545008 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b04 | Bin 0 -> 86788 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b05 | Bin 0 -> 17776 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b07 | Bin 0 -> 1488 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b08 | Bin 0 -> 4096 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b09 | Bin 0 -> 2330624 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b10 | Bin 0 -> 269028 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b11 | Bin 0 -> 99436 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b13 | Bin 0 -> 7024 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b14 | Bin 0 -> 1668 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.flist | 13 +
>> ath11k/IPQ5018/hw1.0/q6_fw.mdt | Bin 0 -> 1052 bytes
>
> For the past several years, the Qualcomm community has been shifting
> from the pack of .mdt+.bNN files to a single .mbn file as a main
> firmware file format. It reduces the back-and-forth between the kernel
> and userspace and also simplifies handling of these files.
>
> In-kernel mdt loader provides backwards compatibility, detecting the
> file type and using .mbn instead of .mdt one, retaining the name (or
> using symlink).
>
> Do you have any plans to also shift from .mdt to .mbn?
I have not heard any such plans but I'll ask around. Would you mind
filing this to bugzilla as a feature request?
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
That way it's easier for me to track it.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-firmware@kernel.org, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org, ath11k@lists.infradead.org
Subject: Re: [PULL linux-firmware] ath10k & ath11k firmware 20230215
Date: Wed, 22 Mar 2023 07:54:19 +0200 [thread overview]
Message-ID: <87v8ite3g4.fsf@kernel.org> (raw)
In-Reply-To: <f08d7310-8c33-ab0b-c9f1-317f737ba37c@linaro.org> (Dmitry Baryshkov's message of "Wed, 22 Mar 2023 01:39:17 +0200")
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
>> ath11k/IPQ5018/hw1.0/Notice.txt | 4094 ++++++++++++++++++++++++++++++
>> ath11k/IPQ5018/hw1.0/board-2.bin | Bin 0 -> 524564 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.b00 | Bin 0 -> 148 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.b01 | Bin 0 -> 136 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.b02 | Bin 0 -> 262144 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.flist | 3 +
>> ath11k/IPQ5018/hw1.0/m3_fw.mdt | Bin 0 -> 284 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b00 | Bin 0 -> 532 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b01 | Bin 0 -> 520 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b02 | Bin 0 -> 7552 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b03 | Bin 0 -> 545008 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b04 | Bin 0 -> 86788 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b05 | Bin 0 -> 17776 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b07 | Bin 0 -> 1488 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b08 | Bin 0 -> 4096 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b09 | Bin 0 -> 2330624 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b10 | Bin 0 -> 269028 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b11 | Bin 0 -> 99436 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b13 | Bin 0 -> 7024 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b14 | Bin 0 -> 1668 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.flist | 13 +
>> ath11k/IPQ5018/hw1.0/q6_fw.mdt | Bin 0 -> 1052 bytes
>
> For the past several years, the Qualcomm community has been shifting
> from the pack of .mdt+.bNN files to a single .mbn file as a main
> firmware file format. It reduces the back-and-forth between the kernel
> and userspace and also simplifies handling of these files.
>
> In-kernel mdt loader provides backwards compatibility, detecting the
> file type and using .mbn instead of .mdt one, retaining the name (or
> using symlink).
>
> Do you have any plans to also shift from .mdt to .mbn?
I have not heard any such plans but I'll ask around. Would you mind
filing this to bugzilla as a feature request?
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
That way it's easier for me to track it.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-firmware@kernel.org, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org, ath11k@lists.infradead.org
Subject: Re: [PULL linux-firmware] ath10k & ath11k firmware 20230215
Date: Wed, 22 Mar 2023 07:54:19 +0200 [thread overview]
Message-ID: <87v8ite3g4.fsf@kernel.org> (raw)
In-Reply-To: <f08d7310-8c33-ab0b-c9f1-317f737ba37c@linaro.org> (Dmitry Baryshkov's message of "Wed, 22 Mar 2023 01:39:17 +0200")
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
>> ath11k/IPQ5018/hw1.0/Notice.txt | 4094 ++++++++++++++++++++++++++++++
>> ath11k/IPQ5018/hw1.0/board-2.bin | Bin 0 -> 524564 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.b00 | Bin 0 -> 148 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.b01 | Bin 0 -> 136 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.b02 | Bin 0 -> 262144 bytes
>> ath11k/IPQ5018/hw1.0/m3_fw.flist | 3 +
>> ath11k/IPQ5018/hw1.0/m3_fw.mdt | Bin 0 -> 284 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b00 | Bin 0 -> 532 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b01 | Bin 0 -> 520 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b02 | Bin 0 -> 7552 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b03 | Bin 0 -> 545008 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b04 | Bin 0 -> 86788 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b05 | Bin 0 -> 17776 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b07 | Bin 0 -> 1488 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b08 | Bin 0 -> 4096 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b09 | Bin 0 -> 2330624 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b10 | Bin 0 -> 269028 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b11 | Bin 0 -> 99436 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b13 | Bin 0 -> 7024 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.b14 | Bin 0 -> 1668 bytes
>> ath11k/IPQ5018/hw1.0/q6_fw.flist | 13 +
>> ath11k/IPQ5018/hw1.0/q6_fw.mdt | Bin 0 -> 1052 bytes
>
> For the past several years, the Qualcomm community has been shifting
> from the pack of .mdt+.bNN files to a single .mbn file as a main
> firmware file format. It reduces the back-and-forth between the kernel
> and userspace and also simplifies handling of these files.
>
> In-kernel mdt loader provides backwards compatibility, detecting the
> file type and using .mbn instead of .mdt one, retaining the name (or
> using symlink).
>
> Do you have any plans to also shift from .mdt to .mbn?
I have not heard any such plans but I'll ask around. Would you mind
filing this to bugzilla as a feature request?
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
That way it's easier for me to track it.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-03-22 5:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 9:17 [PULL linux-firmware] ath10k & ath11k firmware 20230215 Kalle Valo
2023-02-15 9:17 ` Kalle Valo
2023-02-15 9:17 ` Kalle Valo
2023-02-15 19:27 ` Josh Boyer
2023-02-15 19:27 ` Josh Boyer
2023-02-15 19:27 ` Josh Boyer
2023-02-17 18:57 ` Christian Lamparter
2023-02-17 18:57 ` Christian Lamparter
2023-02-17 18:57 ` Christian Lamparter
2023-02-20 5:56 ` Kalle Valo
2023-02-20 5:56 ` Kalle Valo
2023-02-20 5:56 ` Kalle Valo
2023-03-14 12:59 ` Christian Lamparter
2023-03-14 12:59 ` Christian Lamparter
2023-03-15 6:28 ` Kalle Valo
2023-03-15 6:28 ` Kalle Valo
2023-03-17 22:25 ` Christian Lamparter
2023-03-17 22:25 ` Christian Lamparter
2023-03-21 23:39 ` Dmitry Baryshkov
2023-03-21 23:39 ` Dmitry Baryshkov
2023-03-21 23:39 ` Dmitry Baryshkov
2023-03-22 5:54 ` Kalle Valo [this message]
2023-03-22 5:54 ` Kalle Valo
2023-03-22 5:54 ` Kalle Valo
2023-03-23 9:35 ` Dmitry Baryshkov
2023-03-23 9:35 ` Dmitry Baryshkov
2023-03-23 9:35 ` Dmitry Baryshkov
2023-03-23 10:19 ` Kalle Valo
2023-03-23 10:19 ` Kalle Valo
2023-03-23 10:19 ` Kalle Valo
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=87v8ite3g4.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@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.