You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we used 4MB udmabuf to read and write from firmware to host(linux) memory successfully on hardware configuration1 for a while.
Also we are able to read and write to udmabuf with linux test programs in the host. So both the firmware writes and host writes work.
Now we have new piece of hardware configuration and we are seeing strange/different behavior.
In the new hardware we are still able to read and write completely to udmabuf with linux test programs in the host.
HOWEVER, the firmware/PCI writes are not working properly with the new hardware. We see that even if we are writing 10000 bytes from firmware, only the last 80 bytes are written to the udmabuf space when we read it on linux host. What happened to the remaining bytes being written from firmware to udmabuf?
Does anyone know what could be going wrong here or any debugging tips?
thanks
The text was updated successfully, but these errors were encountered:
we used 4MB udmabuf to read and write from firmware to host(linux) memory successfully on hardware configuration1 for a while.
Also we are able to read and write to udmabuf with linux test programs in the host. So both the firmware writes and host writes work.
Now we have new piece of hardware configuration and we are seeing strange/different behavior.
In the new hardware we are still able to read and write completely to udmabuf with linux test programs in the host.
HOWEVER, the firmware/PCI writes are not working properly with the new hardware. We see that even if we are writing 10000 bytes from firmware, only the last 80 bytes are written to the udmabuf space when we read it on linux host. What happened to the remaining bytes being written from firmware to udmabuf?
Does anyone know what could be going wrong here or any debugging tips?
thanks
The text was updated successfully, but these errors were encountered: