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
I'm wondering about the possibility to have Cedrus working on v3s.
Although Allwinner market v3s as a video encoder/decoder soc, I'm not sure if it would be practically useful since it only has 64 MB, maybe in a very specific use case.
Would be at least fun to have it 😄
I added this code to arch/arm/boot/dts/sun8i-v3s.dtsi that I copied from a33 dts.
and the module doesn't load.
How could I track the source of this problem?
Looking in the memory mapping of the v3s, it seems that the video engine (VE) should be in the same address as the other SOC, bur SRAM C seems to be in a different place, and much smaller. Also, it is not clear that this space can be used by the video engine.
V3S:
A10:
The text was updated successfully, but these errors were encountered:
Hello,
I'm wondering about the possibility to have Cedrus working on v3s.
Although Allwinner market v3s as a video encoder/decoder soc, I'm not sure if it would be practically useful since it only has 64 MB, maybe in a very specific use case.
Would be at least fun to have it 😄
I added this code to
arch/arm/boot/dts/sun8i-v3s.dtsi
that I copied from a33 dts.and loaded the module, but I'm having the following kernel crash:
and the module doesn't load.
How could I track the source of this problem?
Looking in the memory mapping of the v3s, it seems that the video engine (
VE
) should be in the same address as the other SOC, bur SRAM C seems to be in a different place, and much smaller. Also, it is not clear that this space can be used by the video engine.V3S:
A10:
The text was updated successfully, but these errors were encountered: