search

rockchip-linux / mpp

Media Process Platform (MPP) module
465 stars 155 forks source link

4G limit on an 8G board #560

Open great9 opened 3 months ago

great9 commented 3 months ago

There seems to be a memory limit of 4G even though my board is 8G. I've described it on nyanmisaka's ffmpeg-rockchip repo: https://github.com/nyanmisaka/ffmpeg-rockchip/issues/51

HermanChen commented 2 months ago

The 32bit iova space is hardware limit. But we still can use some tick in driver to workaround this problem. We are trying.

great9 commented 2 months ago

The 32bit iova space is hardware limit. But we still can use some tick in driver to workaround this problem. We are trying.

Thank you!

Lots of people have this issue. At one point I was considering of getting a secondary board with 16GB but then I found out more people had this problem.

great9 commented 2 months ago

The 32bit iova space is hardware limit. But we still can use some tick in driver to workaround this problem. We are trying.

any updates?

great9 commented 1 month ago

@HermanChen

HermanChen commented 1 month ago

It is not fixed yet.

great9 commented 1 month ago

It is not fixed yet.

just pinging in the hopes of getting a message back from you saying that 4 devs are working on a fix. :)

from design perspective, why was this ever limited to 32 bit? Vendors marketed the board as a multi-realtime-stream encoder/decoder. It's very easy to hit that limit.

great9 commented 2 weeks ago

any updates @HermanChen ?

chencl9410 commented 2 weeks ago

0001-DEBUG-video-rockchip-mpp-disable-CONFIG_DMABUF_CACHE.patch To disable DMABUF_CACHE so that iova will be instantly unmaped after every encoder/decoder task finished. Please apply this patch on kernel6.1 or kernel5.10 and recompile kernel boot and retry. @great9

great9 commented 3 days ago

0001-DEBUG-video-rockchip-mpp-disable-CONFIG_DMABUF_CACHE.patch To disable DMABUF_CACHE so that iova will be instantly unmaped after every encoder/decoder task finished. Please apply this patch on kernel6.1 or kernel5.10 and recompile kernel boot and retry. @great9

this patch doesn't apply with 5.10 rkr3.4 (aka the latest 5.10 from radxa)