On Tue, Sep 24, 2024 at 04:13:08PM GMT, Maxime Ripard wrote:
> On Tue, 27 Aug 2024 11:39:04 -0500, 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_INF
On Tue, 27 Aug 2024 11:39:04 -0500, 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
On Mon, 16 Sep 2024, Derek Foreman wrote:
> Gentle ping - is there anything more I need to do before this can land?
I don't think so. FWIW, I bounced this to intel-gfx and got passing CI
results too.
Cc: drm-misc maintainers. Just wondering where to merge this. It's a fix
to commits in v6.11. Ar
Gentle ping - is there anything more I need to do before this can land?
Thanks,
Derek
On 2024-08-28 03:31, Jani Nikula wrote:
On Tue, 27 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 tot
On Tue, 27 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
On Tue, 27 Aug 2024 11:39:04 -0500, 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
>
> [ ... ]
Acked-by: Max
