qcom: Add sdx61 Foxconn vendor firmware image file
PATCH 1/1 qcom: Add sdx61 Foxconn vendor firmware image file
For MHI modems, it defines an edl firmware in kernel drivers/bus/ mhi/host/pci_generic.c file. According to the requirement of MHI driver maintainer, we shall commit this firmware before commiting kernel driver support.
Since different vendor use different firmwares, so we add a vendor sub-folder under qcom/sdx61.
--- WHENCE | 7 +++++++ qcom/sdx61/foxconn/prog_firehose_lite.elf | Bin 0 -> 663552 bytes 2 files changed, 7 insertions(+) create mode 100644 qcom/sdx61/foxconn/prog_firehose_lite.elf
WHENCE +7 -0
@@ -8689,3 +8689,10 @@ File: qcom/qcm6490/qupv3fw.elf File: qcom/qcs8300/qupv3fw.elf License: Redistributable. See LICENSE.qcom and qcom/NOTICE.txt for details +--------------------------------------------------------------------------- + +Driver: sdx61 - Qualcomm SDX61 firmware image file for Foxconn vendor +File: qcom/sdx61/foxconn/prog_firehose_lite.elf + +License: Redistributable. See LICENSE.qcom and qcom/NOTICE.txt for details +
qcom/sdx61/foxconn/prog_firehose_lite.elf new file binary +0 -0
Signature · 1 line
2.25.1
Quoted 7 lines · Slark Xiao
For MHI modems, it defines an edl firmware in kernel
drivers/bus/mhi/host/pci_generic.cfile. According to the requirement of MHI driver maintainer, we shall commit this firmware before commiting kernel driver support.
Since different vendor use different firmwares, so we add a vendor sub-folder under qcom/sdx61.
Quoted 7 lines
Signed-off-by Slark Xiao <[email protected]>--- WHENCE | 7 +++++++ qcom/sdx61/foxconn/prog_firehose_lite.elf | Bin 0 -> 663552 bytes 2 files changed, 7 insertions(+) create mode 100644 qcom/sdx61/foxconn/prog_firehose_lite.elf
Signature · 2 lines
With best wishes Dmitry
Quoted 17 lines · Dmitry Baryshkov
Quoted 7 lines · Slark Xiao
For MHI modems, it defines an edl firmware in kernel
drivers/bus/mhi/host/pci_generic.cfile. According to the requirement of MHI driver maintainer, we shall commit this firmware before commiting kernel driver support.
Since different vendor use different firmwares, so we add a vendor sub-folder under qcom/sdx61.Quoted 7 lines
Signed-off-by Slark Xiao <[email protected]>--- WHENCE | 7 +++++++ qcom/sdx61/foxconn/prog_firehose_lite.elf | Bin 0 -> 663552 bytes 2 files changed, 7 insertions(+) create mode 100644 qcom/sdx61/foxconn/prog_firehose_lite.elf
Quoted 1 line
Acked-by Dmitry Baryshkov <[email protected]>
I'm sorry, but I have no indication the submitter has the authority to submit this firmware. It's from a gmail address. Is your Ack implying Qualcomm is agreeing to submit this firmware?
josh
Quoted 19 lines · Josh Boyer
Quoted 17 lines · Dmitry Baryshkov
Quoted 14 lines · Slark Xiao
For MHI modems, it defines an edl firmware in kernel
drivers/bus/mhi/host/pci_generic.cfile. According to the requirement of MHI driver maintainer, we shall commit this firmware before commiting kernel driver support.
Since different vendor use different firmwares, so we add a vendor sub-folder under qcom/sdx61.Signed-off-by Slark Xiao <[email protected]>--- WHENCE | 7 +++++++ qcom/sdx61/foxconn/prog_firehose_lite.elf | Bin 0 -> 663552 bytes 2 files changed, 7 insertions(+)create mode 100644 qcom/sdx61/foxconn/prog_firehose_lite.elf
Quoted 5 lines
Quoted 1 line
Acked-by Dmitry Baryshkov <[email protected]>I'm sorry, but I have no indication the submitter has the authority to submit this firmware. It's from a gmail address. Is your Ack implying Qualcomm is agreeing to submit this firmware?
No, I can not validate the submitter too. It's more about the filename hierarchy. I'm sorry for the confusion.
Signature · 2 lines
With best wishes Dmitry
Quoted 21 lines · Dmitry Baryshkov
Quoted 19 lines · Josh Boyer
Quoted 17 lines · Dmitry Baryshkov
Quoted 14 lines · Slark Xiao
For MHI modems, it defines an edl firmware in kernel
drivers/bus/mhi/host/pci_generic.cfile. According to the requirement of MHI driver maintainer, we shall commit this firmware before commiting kernel driver support.
Since different vendor use different firmwares, so we add a vendor sub-folder under qcom/sdx61.Signed-off-by Slark Xiao <[email protected]>--- WHENCE | 7 +++++++ qcom/sdx61/foxconn/prog_firehose_lite.elf | Bin 0 -> 663552 bytes 2 files changed, 7 insertions(+)create mode 100644 qcom/sdx61/foxconn/prog_firehose_lite.elf
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
Acked-by Dmitry Baryshkov <[email protected]>I'm sorry, but I have no indication the submitter has the authority to submit this firmware. It's from a gmail address. Is your Ack implying Qualcomm is agreeing to submit this firmware?
No, I can not validate the submitter too. It's more about the filename hierarchy. I'm sorry for the confusion.
Thank you for clarifying.
Slark, given we can't identify this was supposed to be released and licensed under the Qualcomm license from your email address alone, we can't merge this. We have no idea what the provenance of this firmware is.
Can you work with someone in Qualcomm to acknowledge this came from them and it's licensed appropriately by sending the firmware or at least an Ack from a qualcomm email address?
josh
Quoted 34 lines · Josh Boyer
Quoted 21 lines · Dmitry Baryshkov
Quoted 19 lines · Josh Boyer
Quoted 17 lines · Dmitry Baryshkov
Quoted 14 lines · Slark Xiao
For MHI modems, it defines an edl firmware in kernel
drivers/bus/mhi/host/pci_generic.cfile. According to the requirement of MHI driver maintainer, we shall commit this firmware before commiting kernel driver support.
Since different vendor use different firmwares, so we add a vendor sub-folder under qcom/sdx61.Signed-off-by Slark Xiao <[email protected]>--- WHENCE | 7 +++++++ qcom/sdx61/foxconn/prog_firehose_lite.elf | Bin 0 -> 663552 bytes 2 files changed, 7 insertions(+)create mode 100644 qcom/sdx61/foxconn/prog_firehose_lite.elf
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
Acked-by Dmitry Baryshkov <[email protected]>I'm sorry, but I have no indication the submitter has the authority to submit this firmware. It's from a gmail address. Is your Ack implying Qualcomm is agreeing to submit this firmware?
No, I can not validate the submitter too. It's more about the filename hierarchy. I'm sorry for the confusion.
Thank you for clarifying.
Quoted 8 lines
Slark, given we can't identify this was supposed to be released and licensed under the Qualcomm license from your email address alone, we can't merge this. We have no idea what the provenance of this firmware is.
Can you work with someone in Qualcomm to acknowledge this came from them and it's licensed appropriately by sending the firmware or at least an Ack from a qualcomm email address?
I'd say, Qualcomm or Foxconn.
Signature · 2 lines
With best wishes Dmitry
Hi all,
Thanks for this suggestion.
@mani could help confirm this since he is now working in Qualcomm and he is the maintainer of MHI driver as well.
And also, I will forward this email to my company's address [email protected]. That account would confirm this.
Thanks
Quoted 51 lines · Dmitry Baryshkov <[email protected]> 于2025年6月24日周二 06:41写道:
Quoted 23 lines · Josh Boyer
Quoted 21 lines · Dmitry Baryshkov
Quoted 19 lines · Josh Boyer
Quoted 17 lines · Dmitry Baryshkov
Quoted 14 lines · Slark Xiao
For MHI modems, it defines an edl firmware in kernel
drivers/bus/mhi/host/pci_generic.cfile. According to the requirement of MHI driver maintainer, we shall commit this firmware before commiting kernel driver support.
Since different vendor use different firmwares, so we add a vendor sub-folder under qcom/sdx61.Signed-off-by Slark Xiao <[email protected]>--- WHENCE | 7 +++++++ qcom/sdx61/foxconn/prog_firehose_lite.elf | Bin 0 -> 663552 bytes 2 files changed, 7 insertions(+)create mode 100644 qcom/sdx61/foxconn/prog_firehose_lite.elf
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
Acked-by Dmitry Baryshkov <[email protected]>I'm sorry, but I have no indication the submitter has the authority
to
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
submit this firmware. It's from a gmail address. Is your Ack implying Qualcomm is agreeing to submit this firmware?
No, I can not validate the submitter too. It's more about the filename hierarchy. I'm sorry for the confusion.
Thank you for clarifying.
Quoted 8 lines
Slark, given we can't identify this was supposed to be released and licensed under the Qualcomm license from your email address alone, we can't merge this. We have no idea what the provenance of this firmware is.
Can you work with someone in Qualcomm to acknowledge this came from them and it's licensed appropriately by sending the firmware or at least an Ack from a qualcomm email address?
I'd say, Qualcomm or Foxconn.
--
With best wishes
Dmitry
HiDmitry, Josh and Mani,
This is Slark Xiao's company's email.
Both [email protected] and [email protected] belong to me. I can confirm this file comes from Foxconn's product. For license issue, please let Mani do a comment.
Thanks
________________________________
发件人: liyun xiao <[email protected]>
发送时间: 2025年6月24日 14:09
收件人: Dmitry Baryshkov <[email protected]>; [email protected] <[email protected]>; Li-Yun Xiao (肖禮云) <[email protected]>; [email protected] <[email protected]> 抄送: Josh Boyer <[email protected]>
主题: Re: [PATCH] qcom: Add sdx61 Foxconn vendor firmware image file
You don't often get email from [email protected]. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Fii 资安提示:该邮件为外部邮件,请不要点击来历不明的链接或附件
External email: Use caution opening links or attachments
Hi all,
Thanks for this suggestion.
@mani could help confirm this since he is now working in Qualcomm
and he is the maintainer of MHI driver as well.
And also, I will forward this email to my company's address [email protected]<mailto:[email protected]>. That account would confirm this.
Thanks
Dmitry Baryshkov <[email protected]<mailto:[email protected]>> 于2025年6月24日周二 06:41写道:
Quoted 34 lines · Josh Boyer
Quoted 21 lines · On Mon, Jun 23, 2025 at 9:55 AM Dmitry Baryshkov…
Quoted 19 lines · Josh Boyer
Quoted 17 lines · On Mon, Jun 23, 2025 at 9:42 AM Dmitry Baryshkov…
Quoted 14 lines · Slark Xiao
For MHI modems, it defines an edl firmware in kernel
drivers/bus/mhi/host/pci_generic.cfile. According to the requirement of MHI driver maintainer, we shall commit this firmware before commiting kernel driver support.
Since different vendor use different firmwares, so we add a vendor sub-folder under qcom/sdx61.Signed-off-by Slark Xiao <[email protected]<mailto:[email protected]>>--- WHENCE | 7 +++++++ qcom/sdx61/foxconn/prog_firehose_lite.elf | Bin 0 -> 663552 bytes 2 files changed, 7 insertions(+)create mode 100644 qcom/sdx61/foxconn/prog_firehose_lite.elf
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
I'm sorry, but I have no indication the submitter has the authority to submit this firmware. It's from a gmail address. Is your Ack implying Qualcomm is agreeing to submit this firmware?
No, I can not validate the submitter too. It's more about the filename hierarchy. I'm sorry for the confusion.
Thank you for clarifying.
Quoted 8 lines
Slark, given we can't identify this was supposed to be released and licensed under the Qualcomm license from your email address alone, we can't merge this. We have no idea what the provenance of this firmware is.
Can you work with someone in Qualcomm to acknowledge this came from them and it's licensed appropriately by sending the firmware or at least an Ack from a qualcomm email address?
I'd say, Qualcomm or Foxconn.
--
With best wishes
Dmitry
________________________________
此电子邮件及其任何附件可能是机密的,其内容仅供指定收件人使用。上述信息表达的任何观点仅代表个人意见,并不一定代表本公司之立场。若您因为误传而收到本邮件,请立即以邮件通知寄件人,并将本邮件删除。禁止将本邮件或其附件复制、转发、散布或以任何形式泄露向任何人透露此消息的内容。本邮件经由 Internet 传递,无法保证电子邮件的完整性和安全性,邮件有可能遭窜改或病毒入侵。为确保资讯之安全,建议收件人请就本邮件及附件之重要内容,与寄件人进行确认
________________________________
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of FII-Foxconn Industrial Internet. If you have received it by mistake, please inform the sender by an email reply and then delete the message. It is forbidden to copy, forward, or in any way reveal the contents of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet. Therefore, it's advised for the receiver to verify the validity of this message with the sender.
________________________________