Maxim Devaev

I could probably add a fifo level for 1080p@50hz/RGB, but I don't quite understand what the more general condition for switching to this level is. Apparently, some other video modes...

Hm, I've tried 511 and it broke both 60 and 50 Hz modes. Something wrong: ``` [root@pikvm ~]# i2ctransfer -f -y 10 r2@0x0f 0x00 0x06 r2@0x0f Error: Invalid direction Error:...

Unchanged 374 value: ``` [root@pikvm ~]# i2ctransfer -f -y 10 w2@0x0f 0x00 0x06 r2@0x0f 0x76 0x01 ``` But is it a right order?..

Ok, the order is right. I found that minimal value you calculated makes 50Hz working, and also fixing 720p@30Hz. ``` i2ctransfer -f -y 10 w4@0x0f 0x00 0x06 0x78 0x00 ```

> The spreadsheet implies that any setting up to the max of 511 is permissible. Well, I tried, it's not working. Very weird. > If `tc358743_num_csi_lanes_needed` used the full line...

> with (typos excepted) I see. I'll test it and come back, thank you. > Sorry I won't accept that hack. Any fix needs to be justifiable, and ideally upstreamed....

``` u32 bps = (bt->width + bt->hfrontporch + bt->hsync + bt->hbackporch) * (bt->height + bt->vfrontporch + bt->vsync + bt->vbackporch) * fps(bt) * bits_pr_pixel; ``` It's not working at all for...

Here is a list of modes for which my hack helps: ``` if ( (bt->width == 1920 && bt->height == 1080 && f == 50) || (bt->width == 1280 &&...

> You don't say what that mode is. Sorry, 1280x1024@60Hz with RGB24, for example. > I'm afraid that as this isn't a Raspberry Pi product the support level provided for...

Thanks for the tips. My HW engineer and I will carefully read the datasheet and maybe find the right way to use blanking and other things. > Our project is...