On 29/03/17 11:30, Laurent Pinchart wrote: > The mode setting min/max width and height are used by the core when creating a > framebuffer to validate its size. It's thus only related to planes, not to the > CRTC. It's also set to drm_mode_card_res, and fb's min & max are not necessarily the same as plane's min and max. But yes, I think you're right, it's not related to crtc as such. With legacy the fb min defines the crtc min (I think), but possibly with atomic that's not true. It's a bit messed up, really. We should have separate limits for crtcs, planes and fbs. For now the mode_config is all we have. Tomi
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
