Update README.md with testing details #201

ekanshibu · 2025-07-18T08:24:34Z

Add details about the testing status on multiple boards with open source software

lumag · 2025-07-18T08:51:20Z

README.md

+| RB1        | Pending        | Linux next    | Dev :57f7e64   | Linaro Rescue    |
+| RB2        | Passed         | Linux next    | Dev :57f7e64   | Linaro Rescue    |
+| RB3        | Passed         | Linux next    | Dev :57f7e64   | Linaro Rescue    |
+| RB5        | Pending        | Linux next    | Dev :57f7e64   | Linaro Rescue    |


Why are you using 'Linaro Rescue' here? You should be testing with the same hexagon-dsp-binaries package

I was facing problems in booting up RB boards with upstream kernel so used linaro rescue image, I'll try using hexagon-dsp-bins for this.

Huh? What does column list then? Rootfs? The source for dspso.bin? 'Linaro Rescue' doesn't contain a bootable system, it's only bootloaders + firmware.

lumag · 2025-07-18T08:52:05Z

README.md

+| RB3        | Passed         | Linux next    | Dev :57f7e64   | Linaro Rescue    |
+| RB5        | Pending        | Linux next    | Dev :57f7e64   | Linaro Rescue    |
+| RB3Gen2    | Passed         | Linux next    | Dev :57f7e64   | Hexagon DSP bin  |
+| RB5Gen2    | Passed         | Linux next    | Dev :57f7e64   | Hexagon DSP bin  |


No, RB5 Gen2 isn't supported in hexagon-dsp-binaries.

This is actually for QCS9100

RB5 Gen2 was QCS8550

my bad, RB8 is using QCS9100 base, I'll fix this, thanks for pointing this out

lumag · 2025-07-18T08:52:24Z

README.md

+| RB5        | Pending        | Linux next    | Dev :57f7e64   | Linaro Rescue    |
+| RB3Gen2    | Passed         | Linux next    | Dev :57f7e64   | Hexagon DSP bin  |
+| RB5Gen2    | Passed         | Linux next    | Dev :57f7e64   | Hexagon DSP bin  |
+| RB4        | Passed         | Linux next    | Dev :57f7e64   | Hexagon DSP bin  |


Also not supported

QCS8300, will update this one here

Please list both SoC and device on the same line

lumag · 2025-07-18T08:53:00Z

README.md

+| RB4        | Passed         | Linux next    | Dev :57f7e64   | Hexagon DSP bin  |
+| SC8280xp   | Pending        | Linux next    | Dev :57f7e64   | To be upstreamed |
+| X-Elite    | Passed         | Linux next    | Dev :57f7e64   | To be upstreamed |
+| SDM845     | Pending        | Linux next    | Dev :57f7e64   | To be upstreamed |


Are you listing platforms or SoCs here? RB3 uses SDM845.

platform, yes RB3 and RB5 uses SDM845 and SM8250 respectively, was thinking of adding SDM845, SM8250 separately for mobile platform

Which device did you use?

Tried on RB3 and SM8250(in progress). Don't have access to RB5 and SDM845

RB5 is SM8250 (QRB5165). Again, what is being listed here? Please list actual devices.

lumag · 2025-07-18T08:53:18Z

README.md

+| X-Elite    | Passed         | Linux next    | Dev :57f7e64   | To be upstreamed |
+| SDM845     | Pending        | Linux next    | Dev :57f7e64   | To be upstreamed |
+| SM8150     | In Progress    | Linux next    | Dev :57f7e64   | To be upstreamed |
+| SM8250     | In Progress    | Linux next    | Dev :57f7e64   | To be upstreamed |


Same here. RB5 uses SM8250.

lumag · 2025-07-18T08:53:51Z

Missing db410c and db820c

Add details about the testing status on multiple boards with open source software Signed-off-by: Ekansh Gupta <[email protected]>

lumag · 2025-07-30T11:25:55Z

README.md

+
+| Platform   | Testing Status | Kernel Used   | Library Used   | DSP Used         |
+|------------|----------------|---------------|----------------|------------------|
+| RB1        | Pending        | Linux next    | Dev :57f7e64   | Hexagon DSP bin  |


What does 'Linux next' mean? Is it a snapshot from a particular day?
Also, you still have a mixture of device names and SoC names here. Could you please make it more logical? E.g. list both the SoC and the particular device name.

I've tried on both linux-next and 6.16.rc1. Will keep 6.16.rc1 for better understanding.

For SoC & device name, I'll update the details. (Note: I'm majorly using internal reference boards for testing and not the commercial ones)

Can you please comment if you see any discrepancy here (adding @Chennak-quic @quic-bkumar also to comment):
RB1 -> QCS405
RB2 -> QRB4210
RB3 -> DB845C
RB3Gen2 -> QCM6490
RB4 -> QCS8300
RB5 -> QRB5165
RB8 -> QCS9100
DB410c -> MSM8916
DB820c -> MSM8998
Snapdragon 8cx Gen 3 -> SC8280xp
Snapdragon X Elite -> x1e80100
Snapdragon X Plus -> x1p42100
Snapdragon 855 -> SM8150
Snapdragon 865 -> SM8250
Snapdragon 888 -> SM8350
Snapdragon 8 Gen 1 -> SM8450
Snapdragon 8 Gen 2 -> SM8550
Snapdragon 8 Gen 3 -> SM8650

I've tried on both linux-next and 6.16.rc1. Will keep 6.16.rc1 for better understanding.

Which linux-next? It's fine, but please provide the date of the snapshot, so that if there is a question, we can reproduce it later.

For SoC & device name, I'll update the details. (Note: I'm majorly using internal reference boards for testing and not the commercial ones)

I'd really prefer if you use the SoC and the board name. It's fine to use commercial board names or internal board names such as EVK, IDP, MTP, etc.

Can you please comment if you see any discrepancy here (adding @Chennak-quic @quic-bkumar also to comment):

RB1 -> QCS405

wrong

RB2 -> QRB4210

ok

RB3 -> DB845C

wrong

RB3Gen2 -> QCM6490

wrong

RB4 -> QCS8300 RB5 -> QRB5165 RB8 -> QCS9100

ok, please group SM8250 and QRB5165 together.

DB410c -> MSM8916

wrong

DB820c -> MSM8998

wrong

Snapdragon 8cx Gen 3 -> SC8280xp Snapdragon X Elite -> x1e80100 Snapdragon X Plus -> x1p42100 Snapdragon 855 -> SM8150 Snapdragon 865 -> SM8250 Snapdragon 888 -> SM8350 Snapdragon 8 Gen 1 -> SM8450 Snapdragon 8 Gen 2 -> SM8550 Snapdragon 8 Gen 3 -> SM8650

okay

Please also include linux-firmware version that has been used for the test.

I've tried on both linux-next and 6.16.rc1. Will keep 6.16.rc1 for better understanding.

Which linux-next? It's fine, but please provide the date of the snapshot, so that if there is a question, we can reproduce it later.

For SoC & device name, I'll update the details. (Note: I'm majorly using internal reference boards for testing and not the commercial ones)

I'd really prefer if you use the SoC and the board name. It's fine to use commercial board names or internal board names such as EVK, IDP, MTP, etc.

Can you please comment if you see any discrepancy here (adding @Chennak-quic @quic-bkumar also to comment):

RB1 -> QCS405

wrong

RB2 -> QRB4210

ok

RB3 -> DB845C

wrong

Can you please help with the details for RB1, RB2, DB410c and DB820c. I checked internally and found these documented. Some are also there in hexagon-dsp-binaries project.

RB3Gen2 -> QCM6490

wrong

This is what we have been generally using:
https://github.com/linux-msm/hexagon-dsp-binaries/tree/trunk/qcm6490/Thundercomm/RB3gen2

RB4 -> QCS8300 RB5 -> QRB5165 RB8 -> QCS9100

ok, please group SM8250 and QRB5165 together.

DB410c -> MSM8916

wrong

DB820c -> MSM8998

wrong

Snapdragon 8cx Gen 3 -> SC8280xp Snapdragon X Elite -> x1e80100 Snapdragon X Plus -> x1p42100 Snapdragon 855 -> SM8150 Snapdragon 865 -> SM8250 Snapdragon 888 -> SM8350 Snapdragon 8 Gen 1 -> SM8450 Snapdragon 8 Gen 2 -> SM8550 Snapdragon 8 Gen 3 -> SM8650

okay

RB1 uses QRB2210

DB410 uses APQ8016, should be grouped with MSM8916

DB820C uses APQ8096, should be grouped with MSM8996 (not 98)

RB3 uses SDA845. DB845C is another name for RB3

RB3 Gen2 uses QCS6490

github-actions · 2025-10-01T02:12:18Z

This pull request has been marked as stale due to 60 days of inactivity.

quic-bkumar previously approved these changes Jul 18, 2025

View reviewed changes

lumag suggested changes Jul 18, 2025

View reviewed changes

ekanshibu force-pushed the test_doc branch from 21a3a8a to 71fcbb9 Compare July 30, 2025 11:00

Update README.md with testing details

4a3bc1a

Add details about the testing status on multiple boards with open source software Signed-off-by: Ekansh Gupta <[email protected]>

ekanshibu force-pushed the test_doc branch from 71fcbb9 to 4a3bc1a Compare July 30, 2025 11:02

lumag reviewed Jul 30, 2025

View reviewed changes

ekanshibu dismissed quic-bkumar’s stale review via 4a3bc1a August 1, 2025 08:59

github-actions bot added the Stale label Oct 1, 2025

Update README.md with testing details #201

Are you sure you want to change the base?

Update README.md with testing details #201

Uh oh!

Conversation

ekanshibu commented Jul 18, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lumag commented Jul 18, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Oct 1, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants