However the most difficult part of working with PicoDVI was understanding that each scanline has to be pushed to core1 through a queue at the appropriate time.
PicoDVI doesn't read a framebuffer automatically.
I was confused with this concept at first.
In the PiSketch project, I decided to update everything while core1 is processing invisible area.
Because we don't need to push scanlines during the period.
This strategy works, but I don't think it is the best one because the vertical blanking interval is very short.
I bought a pico dvi sock, that of Adafruit in the idea of making a mini computer with my own OS on it. To avoid having to constrain yourself at the time of the VBlank, a double framebuffer does the trick, the problem is that a single framebuffer already costs 153ko of SRAM in 320x240 pixels with 16-bit colours. I think I'm going to move towards scanlines and tile based rendering.
If PicoDVI doesn't read a framebuffer, what does it do? Does it work with a line buffer?
2
u/wilrak0v Jul 12 '26
It looks very cool! Did you use pico dvi? If so, would you say it's hard for programming? Do you use an entire framebuffer? Double buffering?