On 2024-08-27 05:19, Jani Nikula wrote:
On Tue, 27 Aug 2024, Maxime Ripard wrote:
Hi,
On Mon, Aug 26, 2024 at 07:10:11AM GMT, Derek Foreman wrote:
The largest infoframe we create is the DRM (Dynamic Range Mastering)
infoframe which is 26 bytes + a 4 byte header, for a total of 30
bytes.
With
On Tue, 27 Aug 2024, Maxime Ripard wrote:
> Hi,
>
> On Mon, Aug 26, 2024 at 07:10:11AM GMT, Derek Foreman wrote:
>> The largest infoframe we create is the DRM (Dynamic Range Mastering)
>> infoframe which is 26 bytes + a 4 byte header, for a total of 30
>> bytes.
>>
>> With HDMI_MAX_INFOFRAME_SIZE
Hi,
On Mon, Aug 26, 2024 at 07:10:11AM GMT, Derek Foreman wrote:
> The largest infoframe we create is the DRM (Dynamic Range Mastering)
> infoframe which is 26 bytes + a 4 byte header, for a total of 30
> bytes.
>
> With HDMI_MAX_INFOFRAME_SIZE set to 29 bytes, as it is now, we
> allocate too lit
On Mon, 26 Aug 2024, Derek Foreman wrote:
> The largest infoframe we create is the DRM (Dynamic Range Mastering)
> infoframe which is 26 bytes + a 4 byte header, for a total of 30
> bytes.
>
> With HDMI_MAX_INFOFRAME_SIZE set to 29 bytes, as it is now, we
> allocate too little space to pack a DRM
The largest infoframe we create is the DRM (Dynamic Range Mastering)
infoframe which is 26 bytes + a 4 byte header, for a total of 30
bytes.
With HDMI_MAX_INFOFRAME_SIZE set to 29 bytes, as it is now, we
allocate too little space to pack a DRM infoframe in
write_device_infoframe(), leading to an E
