Re: [PULL]: Revert QDU100 firmware binaries

Kishore Batta <[email protected]>
Newsgroups org.kernel.lore.linux-firmware
Message-ID <[email protected]>
On 12/18/2025 10:01 PM, Dmitry Baryshkov wrote:
> On Thu, Dec 18, 2025 at 08:48:16PM +0530, Kishore Batta wrote:
>> The following changes since commit e66d9269e773a553a99f7771982a4bef06c562ec:
>>
>>    Merge branch 'robot/pr-0-1766039412' into 'main' (2025-12-18 13:28:40
>> +0000)
>>
>> are available in the Git repository at:
>>
>>    https://github.com/kishorebatta-ossqcom/remove_qdu_firmware.git
>>
>> for you to fetch changes up to 1b13c94137c81ae21d81065ac94c27e71c51bc96:
>>
>>    [PULL] : Revert QDU100 firmware binaries. (2025-12-18 20:36:55 +0530)
>>
>> ----------------------------------------------------------------
>> Kishore Batta (1):
>>        [PULL] : Revert QDU100 firmware binaries.
> Why is [PULL] being a part of the commit message?
I will remove PULL and use a descriptive subject line in the next revert 
patch.
>
> Also, more than a month ago, when it was submitted previously, I asked
> for a list of the affected software. Are you saying that you are unable
> to compile it?
The affected component is the kernel_boot.elf image used in QDU100 
firmware. No other modules are impacted.
> Also, why are you mentioning some random NOTICE files? This is a licence
> breach, it should be described and treated as such. Write a sensible
> commit message.
I will remove unnecessary references to NOTICE files. The commit message 
will cleanly state that the revert is due to license compliance issue 
and will describe the commit message properly.
>
>>   WHENCE                          |     22 -
>>   qcom/NOTICE.txt                 | 268885 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> What is this? Why are you touching a file which supposedly applies to
> other firmware files?
I will ensure that the next patch only reverts the kernel_boot.elf image 
and does not touch qcom/NOTICE.txt or any unrelated files.
>
>>   qcom/qdu100/abl_userdebug.elf   |    Bin 212792 -> 0 bytes
>>   qcom/qdu100/aop.mbn             |    Bin 510944 -> 0 bytes
>>   qcom/qdu100/aop_devcfg.mbn      |    Bin 12136 -> 0 bytes
>>   qcom/qdu100/cpucp.elf           |    Bin 68576 -> 0 bytes
>>   qcom/qdu100/efs1.bin            |    Bin 512 -> 0 bytes
>>   qcom/qdu100/efs2.bin            |    Bin 512 -> 0 bytes
>>   qcom/qdu100/efs3.bin            |    Bin 512 -> 0 bytes
>>   qcom/qdu100/fw_csm_gsi_3.0.elf  |    Bin 20328 -> 0 bytes
>>   qcom/qdu100/hypvm.mbn           |    Bin 1358672 -> 0 bytes
>>   qcom/qdu100/kernel_boot.elf     |    Bin 49004344 -> 0 bytes
>>   qcom/qdu100/mdmddr.mbn          |    Bin 81960 -> 0 bytes
>>   qcom/qdu100/multi_image.mbn     |    Bin 12088 -> 0 bytes
>>   qcom/qdu100/multi_image_qti.mbn |    Bin 12088 -> 0 bytes
>>   qcom/qdu100/qdsp6sw.mbn.xz      |    Bin 5589248 -> 0 bytes
>>   qcom/qdu100/qdsp6sw_dtbs.elf    |    Bin 7992 -> 0 bytes
>>   qcom/qdu100/qupv3fw.elf         |    Bin 56432 -> 0 bytes
>>   qcom/qdu100/shrm.elf            |    Bin 82428 -> 0 bytes
>>   qcom/qdu100/tz.mbn              |    Bin 3186640 -> 0 bytes
>>   qcom/qdu100/uefi.elf            |    Bin 2666296 -> 0 bytes
>>   qcom/qdu100/xbl_config.elf      |    Bin 225368 -> 0 bytes
>>   qcom/qdu100/xbl_ramdump.elf     |    Bin 749464 -> 0 bytes
>>   qcom/qdu100/zeros_1sector.bin   |    Bin 512 -> 0 bytes
> Are all the files in the list affected by the Open Source Software
> licence breach?
The license compliance issue applies only to kernel_boot.elf image The 
previous patch inadvertently included other QDU100 firmware binaries 
because it was based on a full revert of the original commit. I will 
correct this in the next patch so that only kernel_boot.elf is reverted 
and no other files are touched.
>
>>   24 files changed, 268426 insertions(+), 481 deletions(-)
>>   delete mode 100644 qcom/qdu100/abl_userdebug.elf
>>   delete mode 100644 qcom/qdu100/aop.mbn
>>   delete mode 100644 qcom/qdu100/aop_devcfg.mbn
>>   delete mode 100644 qcom/qdu100/cpucp.elf
>>   delete mode 100644 qcom/qdu100/efs1.bin
>>   delete mode 100644 qcom/qdu100/efs2.bin
>>   delete mode 100644 qcom/qdu100/efs3.bin
>>   delete mode 100644 qcom/qdu100/fw_csm_gsi_3.0.elf
>>   delete mode 100644 qcom/qdu100/hypvm.mbn
>>   delete mode 100644 qcom/qdu100/kernel_boot.elf
>>   delete mode 100644 qcom/qdu100/mdmddr.mbn
>>   delete mode 100644 qcom/qdu100/multi_image.mbn
>>   delete mode 100644 qcom/qdu100/multi_image_qti.mbn
>>   delete mode 100644 qcom/qdu100/qdsp6sw.mbn.xz
>>   delete mode 100644 qcom/qdu100/qdsp6sw_dtbs.elf
>>   delete mode 100644 qcom/qdu100/qupv3fw.elf
>>   delete mode 100644 qcom/qdu100/shrm.elf
>>   delete mode 100644 qcom/qdu100/tz.mbn
>>   delete mode 100644 qcom/qdu100/uefi.elf
>>   delete mode 100644 qcom/qdu100/xbl_config.elf
>>   delete mode 100644 qcom/qdu100/xbl_ramdump.elf
>>   delete mode 100644 qcom/qdu100/zeros_1sector.bin
>>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.