Skip to content

Update README.md with testing details #201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: development
Choose a base branch
from
Open

Update README.md with testing details #201

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,28 @@ sudo make install

For detailed instructions on testing FastRPC, please refer to the [README.md](test/README.md) in the `test` directory.

**Testing status:**

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

@lumag lumag Jul 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor Author

@ekanshibu ekanshibu Jul 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor

@lumag lumag Jul 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor

@lumag lumag Jul 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor Author

@ekanshibu ekanshibu Aug 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor

@lumag lumag Aug 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • 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

| RB2 | Pending | Linux next | Dev :57f7e64 | Hexagon DSP bin |
| RB3 | Pending | Linux next | Dev :57f7e64 | Hexagon DSP bin |
| RB3Gen2 | Passed | Linux next | Dev :57f7e64 | Hexagon DSP bin |
| QCS9100 | Passed | Linux next | Dev :57f7e64 | Hexagon DSP bin |
| QCS8300 | Passed | Linux next | Dev :57f7e64 | Hexagon DSP bin |
| DB410C | Pending | Linux next | Dev :57f7e64 | Hexagon DSP bin |
| DB820C | Pending | 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 |
| X-Plus | Passed | 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 |
Copy link
Contributor

@lumag lumag Jul 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here. RB5 uses SM8250.

| SM8350 | Passed | Linux next | Dev :57f7e64 | To be upstreamed |
| SM8450 | Passed | Linux next | Dev :57f7e64 | To be upstreamed |
| SM8550 | Passed | Linux next | Dev :57f7e64 | To be upstreamed |
| SM8650 | Passed | Linux next | Dev :57f7e64 | To be upstreamed |

## Logging Control and Verbosity

Both VERIFY and FARF are logging mechanisms used in fastRPC. While VERIFY is a legacy module, FARF is commonly utilized on both DSP (Digital Signal Processor) and HLOS (High-Level Operating System).
Expand Down
Loading