Skip to content

usb: Accept 0x9060 as USB PID for ramdump - #290

Merged
andersson merged 1 commit into
linux-msm:qdl-2.7.yfrom
quic-bjorande:for-linux-msm/pid-9060-for-2.7
Jul 17, 2026
Merged

usb: Accept 0x9060 as USB PID for ramdump#290
andersson merged 1 commit into
linux-msm:qdl-2.7.yfrom
quic-bjorande:for-linux-msm/pid-9060-for-2.7

Conversation

@quic-bjorande

Copy link
Copy Markdown
Contributor

Extend the list of accepted USB PIDs for ramdump with 0x9060.

The proper change is to remove the USB PID list, and this is being done for an upcoming release.

Extend the list of accepted USB PIDs for ramdump with 0x9060.

The proper change is to remove the USB PID list, and this is being done
for an upcoming release.

Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
@igoropaniuk

igoropaniuk commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

@quic-bjorande what about?

qdl/usb.c

Line 279 in f540e59

const char *action = matched_pid == 0x900e ? "Collecting crash dump from" : "Flashing";

@andersson

Copy link
Copy Markdown
Collaborator

@quic-bjorande what about?

You're right, and I believe it would be wrong for some other ramdump targets as well then.

Let's leave it, as the change was validated in its current form and make sure that it's correct in the upcoming v2.8 release.

@andersson
andersson merged commit a248f28 into linux-msm:qdl-2.7.y Jul 17, 2026
14 checks passed
@andersson
andersson deleted the for-linux-msm/pid-9060-for-2.7 branch July 17, 2026 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants