1.0.5: qcom,fastrpc-cb 26300000.remoteproc:glink-edge:fastrpc:compute-cb@2: flag not supported 0x0

[lool]

Hi

This is on a Monaco EVK (RB4) running a linux-next kernel + Debian trixie rootfs from qcom-deb-images.

When I install the fastrpc-support package from:

URIs: https://deb.debusine.debian.net/debian/r-rbasak-qcom-hexagon-stack-2
Suites: sid

I see this in dmesg:

[  211.403260] qcom,fastrpc-cb 26300000.remoteproc:glink-edge:fastrpc:compute-cb@2: flag not supported 0x0
[  211.407715] qcom,fastrpc-cb 3000000.remoteproc:glink-edge:fastrpc:compute-cb@4: flag not supported 0x0

I'm filing this here but please redirect me – I don't know if these messages are due to config files for DSP debug flags being missing in the package, or some issue with the DSP binaries / boot firmware (in which case I'd pass that to hexagon-dsp-binaries, or to the Qcom team releasing boot binaries).

[ekanshibu]

These are non-fatal errors which is seen because '0' flag is not supported by fastrpc mmap ioctl call. We are working on fixing this from our userspace project(qualcomm/fastrpc). I'll update here once we have a PR for this.

[lool]

These are non-fatal errors which is seen because '0' flag is not supported by fastrpc mmap ioctl call. We are working on fixing this from our userspace project(qualcomm/fastrpc). I'll update here once we have a PR for this.

Ah thanks; I guess this belongs in the fastrpc project then, not this packaging one; I don't think I have the permissions to transfer issues, would you like me to file a new one and close this one?

[github-actions]

This issue has been marked as stale due to 60 days of inactivity. To prevent automatic closure in 10 days, remove the stale label or add a comment. You can reopen a closed issue at any time.

[lool]

Removing Stale label

[lool]

Ekansh Gupta (@ekanshibu) should we move this issue to the fastrpc project? Perhaps it's been addressed already?

[ekanshibu]

This is addressed already, qualcomm/fastrpc@f68b30a

[lool]

Thanks! I can't transfer issues to the fastrpc project, so I've just made a note that this is fixed in 1.0.5

[github-actions]

This issue has been marked as stale due to 60 days of inactivity. To prevent automatic closure in 10 days, remove the stale label or add a comment. You can reopen a closed issue at any time.

[ekanshibu]

This should be fixed with 1.0.6 upgrade.