Yeah looks like it, basically normally 2 128byte blocks so file size in most cases would be 256byte
Can use the load command from the first posts here to try and load, it will not tell you if it failed, but can check the dmesg logging I put some “fail” logging in when it cannot pass the checksums etc and fails to load for some reason.
Note: when it fails to load it just reloads the existing without any indication there was an error, so for a while that threw me thinking everything was fine until added the “fail” logging, and worked out the correct format for the EDID files.
Edit: I tried the first one from that list, it loads ok, but looks like not changing the max nits for me in the logging, so not sure.
I do see they contain V2 DV VSVDB, but would think that should be fine, as I guess quite a few displays been tested with CE are V2.
Vendor-Specific Video Data Block (Dolby), OUI 00-D0-46:
Version: 2 (12 bytes)
Supports YUV422 12 bit
DM Version: 3.x
Backlt Min Luma: 100 cd/m^2
Interface: Low-Latency
Supports 10b 12b 444: Not supported
Target Min PQ v2: 0 (0.00000000 cd/m^2)
Target Max PQ v2: 2640 (385 cd/m^2)
Unique Rx, Ry: 0.70703125, 0.28906250
Unique Gx, Gy: 0.16796875, 0.79687500
Unique Bx, By: 0.12890625, 0.04296875
Looking at the code which sets up the min and max luminance, it is only looking at dv version 1, so that explains why I do not see a change from the logging:
if (vinfo->vout_device->dv_info->ver == 1) {
if (vinfo->vout_device->dv_info->tmaxLUM) {
As all the VSVDB info I think is passed down to the dovi.ko this may not matter and possibly it handles v2 differently there, but no source code for that so don’t know what it does - will need empirical testing to check if correct.
Unfortunately though this means no easy way to tell the EDID is in effect from the existing logging on these DV V2 EDID.
, it is not hard - better to teach how to fish 
With the Ezcoo i had to force hdr.
